An option to store several versions of a glyph (variations) in the same project file ?
I guess this could help sorting out different ideas. If one could always exchange the "to be exported" version of a glyph easily, one could assemble all the ideas perhaps in a single file.
(I am only beginning to use FC and have already to many files - perhaps I am doing something wrong but I am hesitant to dump some ideas ).
This would likely require a file format for FontCreator projects.
Variations - inside a FC project file?
-
Bhikkhu Pesala
- Top Typographer
- Posts: 9878
- Joined: Tue Oct 29, 2002 5:28 am
- Location: Seven Kings, London UK
- Contact:
There's nothing to stop you doing that now.
Just insert a few empty glyphs after the mapped glyph and store the (unmapped) glyph variants there.
You can easily strip out all the unwanted glyph variants later by Font, Sort Glyphs. All of the unmapped glyphs will be moved to the end of the font.
Take a look at any commercial font with OpenType features such as Palatino Linotype and you will find a whole load of unmapped glyph variants in it. These variants are accessed by using an OpenType feature called Glyph Substitution (GSUB).
For example, the ligature Th is not mapped to anything, but if the user types Th in an OpenType aware application, it will substitute the ligature for T+h.
Just insert a few empty glyphs after the mapped glyph and store the (unmapped) glyph variants there.
You can easily strip out all the unwanted glyph variants later by Font, Sort Glyphs. All of the unmapped glyphs will be moved to the end of the font.
Take a look at any commercial font with OpenType features such as Palatino Linotype and you will find a whole load of unmapped glyph variants in it. These variants are accessed by using an OpenType feature called Glyph Substitution (GSUB).
For example, the ligature Th is not mapped to anything, but if the user types Th in an OpenType aware application, it will substitute the ligature for T+h.