I'm working with Unibook to print code charts and ... hoping someone might have similar experience with the (teeth-gnashing) issue I'm facing:
Glyphs in my font come out blank when the code chart is printed to PDF.
The glyphs appear AOK on screen. They print fine to my HP printer. Blank squares with PDF.
I'm printing just a single block (working with Cherokee currently). My font is large (6MB ttf), so I tried subsetting it with pyftsubset to just the Cherokee block (21K ttf), but the results are the same.
Unibook 6.1.1 Build 260.4, Win10x64,
Might there be a Unibook discussion group anywhere??
Much appreciation for any advice, pointers, as I'm at wits end ... (Hmmm ... good font name "Wits End" ...)
0
Comments
I am currently playing with alternate PDF "printer" drivers - it could be a problem particular to Adobe's print-to-PDF facility, but I'm working through how to replace / upgrade that component ...
Some of the documentation and guidance reflects this. E.g., the download page makes reference to Windows XP and Windows Vista. That gives an idea of how long it's been since documentation was updated. That HKLM\...\LanguagePack registry entry is incredibly old and has been obsolete since (IIRC) Windows Vista. (IIRC, it was at one time a way to enable use of the Uniscribe component in GDI / User text display, but since Vista Uniscribe was always enabled in every system.)
I'd still encourage you to provide feedback: more feedback just possibly might drive a bit more prioritization toward maintenance of the public version. (But not guaranteed.) In the meantime, I applaud your effort at figuring out how to make it work, and sharing your insights,
It fontproof known to work on Wintel (Win10x64 specifically?) I could not immediately tell from the fontproof info ...
In any case, I am quite far down the rabbit hole at this point ... a 200+ page user guide and a flock of Specimen Book documents for my array of fonts. In any case, my target audience is academic users authoring with Microsoft Word, so I feel I have to use MS Word to author as much documentation as possible. Unibook is the exception, since it is exactly what is needed in terms of familiarity (so many folks use the Unicode code charts), and the ease of decompositions and annotations ...