|File Format||XML Property List|
contents.plist contains a dictionary that maps glyph names to GLIF file names. Those file names must be plain file names, not absolute or relative paths in the file system. Care must be taken when choosing file names: glyph names are case sensitive, yet many file systems are not. There is no one standard glyph name to file name conversion. However, the most common implementation is described below.
Common glyph name to file name algorithm
This algorithm has limited support for case insensitive file systems: it assumes glyph names are not case sensitive apart from the first character.
- If a glyph name starts with a “.
- Replace the “.” with an “_”. Some file systems regard file names that start with “.” as invisible.
- Break the glyph name into parts delimited by “.”.
- If the first part contains one or more underscores, it is a compound name.
- Split the compound name by underscore into its member names.
- To each member starting with a capital letter, add a “_” at the end.
- Rejoin the member names with underscore.
- If the first part contains no underscore:
- If it starts with a capital letter, add a “_” to the end.
- Rejoin the parts with “.”.
- Tag the name with “.glif”.
|glyph name||file name|
- Some file systems impose file name length restrictions. This can cause file name clashes.
- The assumption that glyph names are not case sensitive apart from the first character causes problems with glyph names like A.alt and A.Alt.
The property list data consists of a dictionary at the top level. The keys are glyph names and the values are file names.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>A</key> <string>A_.glif</string> <key>B</key> <string>B_.glif</string> </dict> </plist>