##Adobe File Version: 1.000
#=======================================================================
# FTP file name: README.TXT
#
# Contents: Background information on Unicode mapping tables
# for Mac OS text encodings
#
# Copyright: (c) 1995-1999 by Apple Computer, Inc., all rights
# reserved.
#
# Contact: charsets@apple.com
#
# Changes:
#
# b02 1999-Sep-22 Update information on Cyrillic. Update
# contact e-mail address.
# n07 1998-Feb-05 Rewrite to provide additional information
# relevant to using the accompanying mapping
# tables, and to delete some extraneous
# information. Delete Bulgarian (no special
# encoding, uses standard Cyrillic), add
# Farsi, Devanagari, Gurmukhi, Gujarati,
# Celtic, Gaelic, Inuit, Tibetan.
# n04 1995-Nov-15 Update info for Hebrew and Thai
# n03 1995-Apr-15 First version (after fixing some typos).
#
##################
0. Preliminaries
----------------
For maximum interchangeability, this file and the accompanying Mac OS
mapping tables use only ASCII characters. They are intended to be
displayed in a monospaced font.
Apple, the Apple logo, Mac, and Macintosh are trademarks of Apple
Computer, Inc., registered in the United States and other countries.
QuickDraw and TrueType are trademarks of Apple Computer, Inc. Unicode is
a trademark of Unicode Inc. PostScript is a trademark of Adobe Systems
Inc., which may be registered in certain jurisdictions. IBM is a
registered trademark of International Business Machines Corporation. ITC
Zapf Dingbats is a registered trademark of the International Typeface
Corporation. For the sake of brevity, throughout this document and the
accompanying tables, "Macintosh" can be used to refer to Macintosh
computers and "Unicode" can be used to refer to the Unicode standard.
Apple Computer, Inc. ("Apple") makes no warranty or representation,
either express or implied, with respect to this document and the
accompanying tables, their quality, accuracy, or fitness for a
particular purpose. In no event will Apple be liable for direct,
indirect, special, incidental, or consequential damages resulting from
any defect or inaccuracy in this document or the accompanying tables.
1. Introduction
---------------
This document summarizes some Unicode mapping considerations that are
relevant for the accompanying mapping tables. It also provides an
overview of Mac OS encodings.
These mapping tables and character lists are subject to change.
The latest tables should be available from the following:
<ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/APPLE/>
<ftp://dev.apple.com/devworld/Technical_Documentation/Misc._Standards/>
2. Round-trip fidelity and overview of mapping techniques
---------------------------------------------------------
For a particular set of national and international standards, Unicode
provides round-trip fidelity: Text in one of those encodings can be
mapped to Unicode and back again, yielding the original characters.
Characters which are distinct in one of these source standards have
a distinct counterpart in Unicode. Note that this counterpart might not
be a single Unicode character; as is pointed out in "The Unicode
Standard, Version 2.0" (page 2-10), "sometimes a single code value in
another standard corresponds to a sequence of code values in the Unicode
Standard, or vice versa."
However, Unicode does not attempt to provide round-trip fidelity for
most vendor standards. Nevertheless, Apple and other platform vendors
may need to provide such round-trip fidelity for their current encodings
(this can be important in file systems, for example). In order to do
this, Apple makes use of some Unicode characters in the corporate-use
zone (the upper end of the private use area).
Corporate-zone characters must be used with care. Indiscriminate use of
such characters can result in text which is not easily interchanged with
other systems, since these characters have no standard meaning outside a
particular platform. The mappings provided here are intended to minimize
the use of private use characters, or to use them in such a way that
basic text content will not be lost if the corporate zone characters are
dropped when text is transferred to another system.
The tables provided here have three goals, in the following order of
importance:
1. Provide 100% round-trip mapping from a Mac OS encoding to Unicode
and back (even if the mappings here are converted to maximal
decompositions, see below).
2. Map characters in a Mac OS encoding into the Unicode characters
that best represent the interpretation and usage of the Mac OS
characters.
3. When mapping text in a Mac OS encoding to Unicode using the tables,
the resulting Unicode text should be as interchangeable as possible.
To satisfy these goals, the mappings use a variety of techniques. First
we attempt to achieve round-trip mappings using any standard Unicode
feature at our disposal, without resorting to corporate-zone characters.
This can includes the following techniques:
- Use of all Unicode characters defined in Unicode 2.1, including
compatibility characters.
- Mapping a single character in a Mac OS encoding to a sequence of
standard Unicode characters, or vice versa. This requires grouping
characters into appropriate chunks for lookup before mapping them
(this mainly applies to sequences of Unicode characters).
- Using Unicode direction overrides to force direction attributes when
mapping to Unicode. This requires resolution of Unicode character
direction, and use of this information, when mapping from Unicode back
to certain Mac OS encodings.
The requirements imposed on Unicode handling are necessary for other,
non-transcoding operations in a full Unicode implementation anyway, so
requiring them for transcoding should not impose much of a burden.
Next, if round-trip fidelity cannot be achieved using the above
techniques, we attempt to use corporate-zone characters only as
"transcoding hints" (more on this below). These are combined with one or
more standard Unicode characters to mark them as special for
transcoding, but have no other function and can be deleted with no loss
of basic text content (only of round-trip fidelity).
Finally, if a character in a Mac OS encoding is unrelated to any Unicode
or Unicode sequence, we may map it to a single corporate-zone Unicode
code point.
These techniques are described in more detail in the following sections.
Some clients of these tables may have a different set of goals. For
example, some clients may prefer to avoid compatibility characters,
perhaps sacrificing round-trip fidelity if necessary. In most cases it
is fairly easy to construct other types of mappings from the mappings
given here. In particular, the mappings here have been designed so that
if they are converted to maximal decomposition mappings (by recursive
application of the canonical decompositions in the Unicode database),
the resulting mappings will still provide 100% roundtrip fidelity.
There is one more round-trip issue that should be mentioned. If a
Unicode character or sequence can be mapped at all into a particular
Mac encoding, then the reverse mapping back to Unicode should yield
the original Unicode character or sequence (except for possible
differences in direction overrides or other Unicode characters in the
"Other, Format" category). The tables here also provide this. For a
related issue, see the next section.
3. Mapping tolerance: Strict and loose
--------------------------------------
In many character sets, a single character may have
没有合适的资源?快使用搜索试试~ 我知道了~
温馨提示
本补丁为PhotoShop CS5 或PhotoShop CS6 版本的文字引擎补丁,完美解决因为字体问题而导致的出错,原则上适用于所有版本,但如果真不适用,请百度搜索下载相应版本的补丁(TypeSupport),替换Adobe目录下面的TypeSupport。
资源推荐
资源详情
资源评论
收起资源包目录
PhotoShop CS5 或PhotoShop CS6 版本的文字引擎补丁 (231个子文件)
78-EUC-H 15KB
78-EUC-V 3KB
78-H 15KB
78-RKSJ-H 15KB
78-RKSJ-V 3KB
78-V 3KB
78ms-RKSJ-H 17KB
78ms-RKSJ-V 4KB
83pv-RKSJ-H 7KB
90ms-RKSJ-H 6KB
90ms-RKSJ-V 4KB
90msp-RKSJ-H 6KB
90msp-RKSJ-V 4KB
90pv-RKSJ-H 8KB
90pv-RKSJ-V 4KB
Add-H 15KB
Add-RKSJ-H 15KB
Add-RKSJ-V 4KB
Add-V 4KB
Adobe-CNS1-0 4KB
Adobe-CNS1-1 4KB
Adobe-CNS1-2 4KB
Adobe-CNS1-3 4KB
Adobe-CNS1-4 4KB
Adobe-CNS1-5 4KB
Adobe-CNS1-6 4KB
Adobe-GB1-0 3KB
Adobe-GB1-1 4KB
Adobe-GB1-2 5KB
Adobe-GB1-3 5KB
Adobe-GB1-4 5KB
Adobe-GB1-5 5KB
Adobe-Japan1-0 3KB
Adobe-Japan1-1 3KB
Adobe-Japan1-2 3KB
Adobe-Japan1-3 3KB
Adobe-Japan1-4 4KB
Adobe-Japan1-5 4KB
Adobe-Japan1-6 5KB
Adobe-Japan2-0 3KB
Adobe-Korea1-0 4KB
Adobe-Korea1-1 4KB
Adobe-Korea1-2 4KB
B5-H 8KB
B5-V 3KB
B5pc-H 8KB
B5pc-V 3KB
CNS-EUC-H 13KB
CNS-EUC-V 14KB
CNS1-H 6KB
CNS1-V 3KB
CNS2-H 4KB
CNS2-V 3KB
ctl_gb18030.cnv 223KB
icudt26l.dat 209KB
ETen-B5-H 8KB
ETen-B5-V 3KB
ETenms-B5-H 3KB
ETenms-B5-V 3KB
ETHK-B5-H 24KB
ETHK-B5-V 3KB
EUC-H 5KB
EUC-V 3KB
Ext-H 16KB
Ext-RKSJ-H 16KB
Ext-RKSJ-V 4KB
Ext-V 4KB
GB-EUC-H 5KB
GB-EUC-V 3KB
GB-H 4KB
GB-V 3KB
GBK-EUC-H 85KB
GBK-EUC-V 3KB
GBK2K-H 94KB
GBK2K-V 4KB
GBKp-EUC-H 85KB
GBKp-EUC-V 3KB
GBpc-EUC-H 5KB
GBpc-EUC-V 3KB
GBT-EUC-H 48KB
GBT-EUC-V 3KB
GBT-H 48KB
GBT-V 3KB
GBTpc-EUC-H 48KB
GBTpc-EUC-V 3KB
H 5KB
Hankaku 3KB
Hiragana 3KB
HKdla-B5-H 24KB
HKdla-B5-V 3KB
HKdlb-B5-H 21KB
HKdlb-B5-V 3KB
HKgccs-B5-H 14KB
HKgccs-B5-V 3KB
HKm314-B5-H 14KB
HKm314-B5-V 3KB
HKm471-B5-H 17KB
HKm471-B5-V 3KB
HKscs-B5-H 24KB
HKscs-B5-V 3KB
共 231 条
- 1
- 2
- 3
master_yao
- 粉丝: 126
- 资源: 11
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 基于python实现的基于PyQt5和爬虫的小说阅读系统.zip
- 机械设计整经机上纱自动化sw20非常好的设计图纸100%好用.zip
- Screenshot_20240427_031602.jpg
- 网页PDF_2024年04月26日 23-46-14_QQ浏览器网页保存_QQ浏览器转格式(6).docx
- 直接插入排序,冒泡排序,直接选择排序.zip
- 在排序2的基础上,再次对快排进行优化,其次增加快排非递归,归并排序,归并排序非递归版.zip
- 实现了7种排序算法.三种复杂度排序.三种nlogn复杂度排序(堆排序,归并排序,快速排序)一种线性复杂度的排序.zip
- 冒泡排序 直接选择排序 直接插入排序 随机快速排序 归并排序 堆排序.zip
- 课设-内部排序算法比较 包括冒泡排序、直接插入排序、简单选择排序、快速排序、希尔排序、归并排序和堆排序.zip
- Python排序算法.zip
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
- 1
- 2
前往页