246 useful characters you could put in there, FC leaves the old codes on those extra characters (246-233=13 extra). So when one of these old fonts has the approx. Not sure why, but old symbol fonts were limited to 233 characters. And FC appears to only process the first 233 characters when the Windows encoding is set to Microsoft Symbol - as is in most of these old badly converted fonts. So the names need to be correct (which is often not the case, this font has some errors). In FontCreator (FC) the "Convert to Unicode Font" is looking at the glyph names and assigning Unicode code points based on those names. And you cannot search them in the doc as they are not correctly coded. So you can see the glyphs and enter them from the glyph browser, but you cannot type them. All the glyphs in the original TTF have code points assigned up in the Private Use Area (which no keyboard is going to type). The characters cannot be typed from the keyboard because the keyboard is entering specific Unicode code points and the original TTF is missing those code points. Glyph browsers just display whatever glyphs are there - regardless of the Unicode code points assigned to those glyphs (if any). (and also seems to be listed correctly in the Glyphs browsers of Affinity apps and Photoshop CC 2023 even if they cannot be typed from the keyboard in these apps Considering subscription based software like Photoshop, a user might lose support of certain font technology overnight, if an old version of the app is removed from the computer (I think that Adobe does that eventually) and it would be well grounded to make these kinds of updates to fonts even just temporarily to rescue a job. I can no longer check if the support for these kinds of fonts was lost in Photoshop in context of losing support for PostScript Type 1 (so that this would also affect these kinds of TrueType fonts initially probably converted from PostScript fonts), or if this is more general issue related to missing Unicode support in a font, but the font works perfectly well still in Photoshop CS6. in latest versions of CorelDRAW, VectorStyler and Xara Designer, but not e.g. These kinds of non-Unicode based glyphs are still supported e.g. On the other hand, probably even this kind of meta data update would in many cases be considered illegal use of fonts (even if not distributing them). That kind of utility would not of course work fool proof but in tasks like these where a font does not actually need to be converted but just its meta data "modernized", it would probably mostly make the font useable again. I wonder if there is a simple low-cost utility that allows users to update fonts like these in a batch (or even just one by one e.g., is this feature included in the Home Edition license of FontCreator). In an earlier thread generation of Unicode name table was discussed, and with this font, just running the "Generate Unicode" would make the font compatible with Affinity apps. With this kind of font simulating handwritten text, a limited character set and missing kerning (the glyphs being bound) are not necessarily a problem (if they were not in the original font). Even if you do "fix" it, you end up with a font which is missing characters, no OpenType features, and no kerning.
0 Comments
Leave a Reply. |