![]() ![]() Therefore I didn't use that character, but instead just used the glyph from Wingdings. Strangely, Character Map shows Zilla Slab to include a glyph for U+2714 (Heavy Check Mark), but when I tried to include it in my document, Word refused to let me set the font to Zilla Slab, but instead rendered it in Segoe UI Symbol. Manually hunt through the text in my document, looking for 'exotic' characters specified as Zilla Slab but actually rendered with glyphs from another font (because the glyphs are missing in Zilla Slab).If so, then it would allow another possible workaround: It's possible that the issue may be that I've inadvertently used one of the codepoints with a missing glyph, and Word has silently rendered it with a 'similar' font, which is OK for viewing in Word and printing, but - perhaps - not OK for making a PDF with the font embedded. ![]() automatically remove codepoints with missing glyphs? Can Editor be tweaked to handle this (provide an automatic fix)? E.g. Does the PDF specification prevent fonts with "missing" glyphs from being embedded?ģ. Go back to 'square one' and find another font family to format my document with.Ģ.This seems like a nightmare to do manually, and I don't even know if it would solve the problem. Manually edit all fonts in the family to remove the troublesome codepoints.Let Word rasterise the unembedded Zilla Slab fonts, which then get output as rasterised images of entire paragraphs, which looks OK from a distance (but not close up), but is not searchable, text cannot be highlighted, and so on.Accept the PDF without the font embedded, which means that recipients won't see what I intended.The only options I seem to have at the moment are all bad.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |