Howdy, Stranger!
Categories
- All Categories
- 39 Introductions
- 3.6K Typeface Design
- 764 Font Technology
- 1K Technique and Theory
- 590 Type Business
- 435 Type Design Critiques
- 527 Type Design Software
- 30 Punchcutting
- 132 Lettering and Calligraphy
- 79 Technique and Theory
- 53 Lettering Critiques
- 462 Typography
- 289 History of Typography
- 111 Education
- 62 Resources
- 480 Announcements
- 74 Events
- 104 Job Postings
- 147 Type Releases
- 154 Miscellaneous News
- 259 About TypeDrawers
- 52 TypeDrawers Announcements
- 109 Suggestions and Bug Reports
Options
.FEA glyph ranges
Adam Jagosz
Posts: 689
The AFDKO spec defines glyph range as
[<firstGlyph> - <lastGlyph>]
where
1. By a single letter from A-Z, either uppercase or lowercase.
2. By up to 3 decimal digits in a contiguous run.
<firstGlyph> and <lastGlyph> must be the same length and can differ:1. By a single letter from A-Z, either uppercase or lowercase.
2. By up to 3 decimal digits in a contiguous run.
Now FontForge (which doesn't use the FDK, but its own implementation) gets it right and allows ranges like uni2074-uni2079 (though not uni2074-uni207B, because that would be to much to ask of the standard... which is a failure of the standard IMHO).
But FontLab (which does use the FDK) doesn't allow such ranges, which makes me think that the FDK itself is not congruent with its own spec. Or maybe the devs were misled by the example in the spec,
[ampersand.01 - ampersand.58]and thought that the digits needed to be a suffix separated by period? Because such glyph ranges indeed are supported in FontLab.
Tagged:
0