I am specialized in enhancing marketing and branding efforts through innovative design. I will provide you with top-notch Solution that covers many aspectsīy having a strong experience, I will emphasize customers' expectations with the utmost care. If your name table isn't generating the correct unicode values, make sure that the internal name you've given to your name table isn't conflicting with something else.īTW: From a *user's* standpoint, I strongly prefer fonts that are built this way - the reason for this is that while many all-caps fonts use the same characters for upper- and lowercase characters, many others include variants forms for some or all letters in the lowercase positions.Īs an example, consider Gudrun Hesse's Ariadne font, in which upper- and lowercase characters are identical *except* for four or five characters - if double encoding had been used it would be much easier to tell from the glyph palette which characters actually include alternate forms.Īlthough I understand the reasons why some avoid double-encoding, I find that fonts which include lots of duplication of identical glyphs (e.g A.sc a.sc A.alt.sc a.alt.sc etc) end up with extremely cluttered glyph palettes.I am a Brand Consultant having 7+ years of experience in this field provide a complete range of marketing materials and branding solutions to any industry as well as corporate clients maintaining their reputation and increasing brand awareness online marketing activities. I use this trick all the time and have never had issues, though I would strongly recommend changing the second line above to (I haven’t experimented yet to test by-passing the GOADB and findĪnother other option would be to post-process the OTF with TTX and re-overwrite the cmap table.Īnyone know a trick to get automatically double encode in FontLab Studio 5? I have a custom name table with double encodes but I doesn't work when I try generate Unicode the values get blanked out. My allcaps.nam is formatted like this: I think this Adobe “enforcement” is a side-effect of the GOADB approach, which has other benefits, and the default behaviors.īelieve it may be possible to work around this limitation if youĪddress makeotf directly from the command line and add appropriateįlags.
So, yes, it is overwriting the cmap table. Generates, and the GOADB format does not permit of multiple encoding. Will use the GlyphOrderAndAliasDB to set the unicodes in the OTF it Have subclassed the OutlineOTFCompiler and changed the Save FDK Parts Next To UFO in preferences).
But, for whatever reason, the same baseįont from RoboFont calling ufo2fdk does not (which is inspectable if you The base font that ufo2fdk compiles to hand off to makeotf does respect
0 kommentar(er)
