The archive contains updated glyphname-to-Unicode mapping tables to be used in FontLab Studio 5 and TypeTool 3. Currently, these tables are BETA VERSIONS.
DOWNLOADthe glyphname-to-Unicode mapping tables now!
Please use
this board topic to submit comments, bug reports and opinions on those new tables.
== INSTALLATION ==* To install these files on Microsoft Windows:
1. Unzip the archive.
2. In FontLab Studio 5 or TypeTool 3, go to Tools / Options.
3. Go to the General options / Folders and paths section.
4. If the "Use custom locations for user data files" option is ENABLED, open Windows Explorer and navigate to the folder specified as "User data files for all FontLab products".
5. If the "Use custom locations for user data files" option is DISABLED, open Windows Explorer and navigate to the "My Documents\FontLab\Shared" folder.
6. If there is no "Mapping" subfolder there, create one.
7. Go to the "Mapping" subfolder and place all five extracted .nam files there.
8. Restart FontLab Studio or TypeTool.
9. Go to Tools / Options, General options / Unicode and OpenType.
10. In the "Default Unicode-Name mapping table" dropdown list, choose "2009 Recommended (no afiiXXXXX, no double-encoding)".
* To install these files on Mac OS X:
1. Unzip the archive.
2. In FontLab Studio 5 or TypeTool 3, go to application menu / Preferences.
3. Go to the General options / Folders and paths section.
4. If the "Use custom locations for user data files" option is ENABLED, open Finder and navigate to the folder specified as "User data files for all FontLab products".
5. If the "Use custom locations for user data files" option is DISABLED, open Finder and navigate to the "YourUsername/Library/Application Support/FontLab" folder.
6. If there is no "Mapping" subfolder there, create one.
7. Go to the "Mapping" subfolder and place all five extracted .nam files there.
8. Restart FontLab Studio or TypeTool.
9. Go to application menu / Preferences, General options / Unicode and OpenType.
10. In the "Default Unicode-Name mapping table" dropdown list, choose "2009 Recommended (no afiiXXXXX, no double-encoding)".
== DESCRIPTION ==There are five new glyphname-to-Unicode mapping tables included in this package. Most users should use the "2009 Recommended (no afiiXXXXX, no double-encoding)" table. A brief explanation of the tables is included below. A more detailed explanation of each table, along with a changelog, can be found in each of the tables (you can open them in any plain text editor such as Notepad or TextEdit).
* 2009 Recommended (no afiiXXXXX, no double-encoding)
Mostly compatible on Adobe Glyph List for New Fonts (AGLFN) v1.7, with new-style uniXXXX instead of old-style afiiXXXXX names and without double-mapping for Delta, Omega and mu. This table should be used to develop new fonts.
* 2009 Simplified (no afiiXXXXX, with double-encoding)
Mostly compatible on Adobe Glyph List for New Fonts (AGLFN) v1.7, with new-style uniXXXX instead of old-style afiiXXXXX names, and with double-mapping for Delta, Omega and mu. In this table, all the afiiXXXXX names found in the older AGLFN are considered legacy glyphname-to-Unicode, i.e. if "Generate Glyph Names" is used, the uniXXXX names will be generated instead.
* 2009 Compatible (with afiiXXXXX, with double-encoding)
Mostly compatible on Adobe Glyph List for New Fonts (AGLFN) v1.7, with old-style afiiXXXXX names, and with double-mapping for Delta, Omega and mu. This table provides best compatibility with very old applications but is not recommended for new fonts.
* 2009 Alternative (with afiiXXXXX, no double-encoding)
Mostly compatible on Adobe Glyph List for New Fonts (AGLFN) v1.7, with old-style afiiXXXXX names and without double-mapping for Delta, Omega and mu. This table provides good compatibility with very old applications but is not recommended for new fonts.
* 2009 Private (with PUA codepoints)
Mostly compatible on Adobe Glyph List for New Fonts (AGLFN) v1.7, with new-style uniXXXX instead of old-style afiiXXXXX names and without double-mapping for Delta, Omega and mu. In addition, this table provides a large set of semi-standardized mappings in the Private Use Area (PUA) Unicode block. Adobe currently does not recommend using PUA codepoints but some font developers may prefer to use them for increased compatibility with some applications that support Unicode but do not support user-controllable OpenType Layout features (e.g. Microsoft Word 97-2007).
== DISCLAIMER ==
These tables are considered "beta software" and are provided "as is". Fontlab Ltd. does not provide any warranty for the accuracy or correctness of the data included.
