Yourself if you depend on someone else’s C code, and it would clutterĭo you include a glyph or not, if it might take the place of anĪnother even simpler condition that can occur, and which the Googleįont subset script fails, is when a glyph is multiply-encoded. I have used scripts to generate my fontsįor a long time. Matter that I long ago quit using the Generate dialog for anything but Generating fonts with serious options is such a complicated I know, but this is a sort of thing for which extension languagesĮxist. Well, suppose you have a Type 1 or other font with more than oneĮncoding. Leave out its substitution rules as well, to save yet more space? Otherwise would be left out, but that glyph might take the place ofĪnother after substitution, do I include it, or do I leave it out, and If I have a glyph, either unencoded or with an encoding value that I would take the time to get accustomed with the writing of such There will be different scripts for different purposes. It is going to be too much for any one script to handle allĬases. These are all factors that a script has to take into account, and A glyph name mayĬorrespond to the encoding according to some convention, or it may May happen to correspond to Unicode codepoints. The encoding or encodings are stored in the font. In FF the concept of an encoding means a well-known platformĮncoding, which is kind of obsolete today because of Unicode. Values and their ascii names and are easily user definable whereas Means is really handled by 'NameLists,' which have both unicode I'm not 100% clear on how FF handled encodings I believe what Vern I think what Vern wants is widgets in the Generate dialog. These are all decisions to be made by the person tailoring her own script. Right, which won't be part of any pre-defined encoding, but can be part of a namelist. I thought a font in FF can only have one encoding, but FF can re-encode easily.Īre there some glyphs you want to include ‘just because’, such as a foundry logo? If there is more than one encoding in the font, which one do you use? Plenty of characters may have no encoding at allĭo you include a glyph or not, if it might take the place of an encoded I think this ought to better surfaced to users and namelists ought to be stored in /usr/local/share/fontforge/namelists/ and then ~/.FontForge/namelists/ I'm not 100% clear on how FF handled encodings I believe what Vern means is really handled by 'NameLists,' which have both unicode values and their ascii names and are easily user definable whereas in FF the concept of an encoding means a well-known platform encoding, which is kind of obsolete today because of Unicode. Made by the person tailoring her own script.įor instance, how should the subset be determined, since encoding is not a fundamental characteristic of a glyph? ‘just because’, such as a foundry logo? These are all decisions to be Glyph after substitution? If there is more than one encoding in theįont, which one do you use? Are there some glyphs you want to include You include a glyph or not, if it might take the place of an encoded Have no encoding at all, or they may have more than one encoding. Not a fundamental characteristic of a glyph? Plenty of characters may Scripting is far better for this than building in a feature.įor instance, how should the subset be determined, since encoding is
#FONTFORGE MAC SUBSET CHAR ISO#
So, for example, a font that contains characters from ISO 8859-1 Latin, ISO 8859-5 Cyrillic, and ISO-8859-2 Latin, should be able to generate 3 subset fonts named for example 'Latin', 'Latin-2', and 'Cyrillic'. This could be set up enabled at 'Generate Fonts.' and / or from the 'Font Info' tables. it would be a helpful feature to be able to generate the font in subsets, based on fontforge's unicode encoding sets.
Feature request - When generating a font from File->Generate Fonts.
0 kommentar(er)
