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.
Grep "Armenian" -R * from the base directory to find the various caches.you will note that they might not be 100% right for 9.0, so this is also a good point to correct these manually.Feature request - When generating a font from File->Generate Fonts. To get down to the core, for least programmer interaction, I would have to point towards Unicode/makeutype.c for extracting the unicode ranges (seems plural, when looking at some extended ranges like Arabic), and Unicode/makebuilds.c (needs a rework, and partially handled by Unicode/charset/generate.sh).Īt the moment, since the unicode blocks *.c files aren't quite automated yet, you may want to put something together as a pull request to see what this looks like as a result.
FONTFORGE MAC SUBSET CHAR PLUS
Just my opinion on noting a couple of Unicode blocks that I'm not 100% sure are up-to 9.0 since I've found more than one copy, plus having looked at combiners which were at 5.3, and I'm not quite satisfied with the results. If the feature changes current behavior, reasons why your solution is betterĬreating these by hand, the first time sounds okay, but maintaining these as time passes, will become a bit of a bear (to maintain by hand).A description of the problem you're trying to solve, including why you think this is a problem.When you open an issue for a change/improvement/feature request: (optional) Possible solution/fix/workaround.The behavior you expect to see, and the actual behavior.The FontForge version and the operating system you're using.Reported on Ubuntu 16.10 for FontForge 20161005 When reporting a bug/issue:
FONTFORGE MAC SUBSET CHAR CODE
Optionally, when someone can supply me with the source of this information, I could add the same for the MS Code Pages. To get these details not, now has to look them up at Unicode's website. Which files need to be extended with this information at the end of the name of the Unicode range? fontforge/unicoderange.c and/or fontforgeexe/fontinfo.c ? I am willing to create a pull request on GtiHub when maintainers support this idea. Please, add from/to Unicode character ranges to Charsets as indicated in the screenshot.
0 kommentar(er)
