![]() ![]() Thank you for your attention to this issue. I also find it interesting that with >5.6.3, Word displays a secondary box next to the glyphs (as well as at the end of each table row & paragraph.) These are NOT the hidden text characters that Word uses they still appear if hidden text is displayed.Īnother observation is that the Windows 10 font view/installation window shows the "th" ligature in the font-view for 5.6.3 but does not for subsequent (and "broken") versions. Maybe some of the differences in the character matching might help? The char code column is the character code value Word displays in its Insert Symbol dialog window when selecting the said character. I made a composite image from this document with both 5.6.3 & 5.10.0. The characters were copied to the standard clipboard from MS Word & pasted into the XML edit-stream of the XDF file. ![]() The truly bizarre thing is that my XDF file is still able to access icons that are no longer rendering if I am inserting the character into a field via JavaScript. I was able to continue my work in InDesign ES4 for another 2 days beyond that before that too stopped rendering glyphs. I was able to use Desktop Pro 5.10.0-11 (or whatever that versioning is supposed to be) for 1 day in MS Word before glyphs started to no longer render. It almost seems as if only Unicode prefixed with 'f0' is working as expected while others are unpredictable. Wouldn't you know it, every single glyph is rendered exactly as intended, just as they appear in MS Word. Instead of the native "Export PDF" option, I just tried saving it through Adobe Acrobat DC instead since I have that installed as part of Adobe CC. However, upon saving the document with MS Word's built-in "Export PDF" option, the aforementioned Diploma icon is rendered as white space, despite appearing correctly within Word itself! Curiously, the same is true for the Graduation-cap glyph ( f19d) but not for Briefcase ( f0b1), which is rendered just fine in MS Word and as a PDF. ![]() In my case, when I copy-pasted the unicode glyph for Diploma ( f5ea), it would actually display Paste ( f0ea) instead.įollowing on from message, I replaced the Desktop OTFs with Web TTFs instead and that appears to resolve the issue immediately. Just to add on to this, I experience the same issue of missing/incorrect glyphs when using the Desktop OTFs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |