|
|
#1
07-31-2019, 06:16 AM
|
|||
|
|||
how to track down unicode 0x2010
I'm copy/pasting content from a .docx file to a pure .xml environment, and while everything looks OK there is a warning when I compile:
[FOP WARNING] Glyph "‐" (0x2010, hyphentwo) not available in font "ArialMT". What's the easiest way to track down these occurrences of hyphentwo in the original .docx before migrating the content? 
|
| Tags |
| 0x2010, hyphentwo, unicode |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Using Unicode for Document Properties | ziggle314 | Word | 7 | 03-03-2019 10:05 PM |
 Creating PDF in track changes - simple track changes only
|
sophiah81 | Word | 8 | 07-19-2018 12:51 AM |
|
Track Changes doesn't track Change Case changes
|
wardw | Word | 3 | 10-28-2012 05:31 PM |
| ANSI-ost to unicode-ost | jeff13 | Outlook | 0 | 01-07-2010 11:48 AM |
| Unicode Big endian support | Rose44 | Excel | 0 | 09-04-2009 11:59 PM |
Windows 7 32bit 
Office 2010 64bit
Threaded Mode