© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The attached patch works for me. It scans through the wide chars as they come in from the EMF/WMF, if any are in the range F020-F0FF then subtract F000. Once the patch was applied all of the problem WMF examples imported correctly.
AFAIK MS only used this range for the Symbols and Wingdings* fonts, so it might speed things up slightly on EMF/WMF import to only call the new msdepua function for text when it is in one of those fonts. But I suspect it would only matter if the imported metafile was about a book's worth of text.
Does Inkscape have a philosophy/design document concerning Private Use Areas? If so, this patch may not be acceptable.
In any case, the odds are that if characters are found in this range during an EMF,WMF import, then they probably came from MS software or from software that used the same conventions. Mostly because it was too dangerous for anybody else to step into Microsoft's PUA, as doing that would have been a good recipe for incompatibility with this de facto "standard".