> - can this report be closed as 'Fix Released' (Milestone 0.47), > I was able to import the PDF generated by OO3 PDF Export > Subject: Re: PDF import changes font case randomly I have no issues with viewing and editing my OO3 sample PDF using the current stable version, Inkscape 0.48.0 r9654Īs far as I am concerned, the bug is fixed so please close the report, thanks! According to Ken Sharp's reply to my bug, it seems to be a non-standard encoding problem with the font, see changed: I thought this might be a bug in Ghostscript, which generated the above PDF ( ) so I filed the problem as a bug with Ghostscript. I don't see a bug here, possibly (given that the PDF file was created by GSĨ.63) there is a bug in pdfwrite which caused the encoding oddness, btu thatĬan't be determined without seeing the PostScript file. Re-encoded the font like this, so that the PDF file had to be made the same way. Would have to guess that the file was created from a PostScript file which had Its impossible to tell from the PDF file why the file was created this way, one aacute /t and so on, which matches what you get when you copy and paste. To the glyph names we see that we get /Y /bar /Udieresis /aacute /agrave /space Using the Encoding to map from the character codes In thisĬase Acrobat falls back to translating the glyph names into their ASCIIĮquivalents (when possible). So there is no Unicode information, and the encoding is non standard.
In addition the glyph names in the encoding are not what one wouldĮxpect, I would expect to see /F, /i /r, /s, /t and so on.
The font in question is a TrueType font embedded as a subset without a ToUnicodeĬMap, and using a custom encoding. bugs.ghostscrip t.com/show_ bug.cgi? id=690440 According to Ken Sharp's reply to my bug, it seems to be a non-standard encoding problem with the font, see below: I thought this might be a bug in Ghostscript, which generated the above PDF ( launchpadlibrar ian.net/ 25800877/ test3.pdf ) so I filed the problem as a bug with Ghostscript.
0 kommentar(er)
