Hi Jeremias, Jeremias Maerki wrote: > False alarm. JPedal and kpdf, for example, have no problems > reconstructing the correct text based on the embedded Encoding. PDFBox,
Are non-default encodings supposed to work after your latest commit? Because I would like to test evince but I didn’t manage to produce a PDF with a non-default encoding. When putting cyrillic characters in my FO file I get the following kind of errors: WARNING: Glyph 1033 (0x409, afii10058) not available in font NimbusSanL-Regu And I still see “/Encoding /WinAnsiEncoding” in the PDF when I open it by hand. Have I missed anything? Thanks, Vincent > too, but that one had problems extracting from text written using a > TrueType font. But Adobe Acrobat Reader does have a problem: text > written in a Cyrillic Type 1 font is extracted incorrectly. Not even > adding a ToUnicode CMap helped here. Probably a bug. I have no other > idea who I could help Acrobat extract the text correctly. So, if you > care about copy/paste from Acrobat, switch to TrueType fonts instead of > using fonts with encodings other than AdobeStandardEncoding or > WinAnsiEncoding. > > On 13.02.2008 12:12:59 Jeremias Maerki wrote: > <snip/> >> BTW, I just found out that I have to generate a ToUnicode CMap if a >> Type1 font doesn't use one of the encodings that are predefined in the >> PDF spec. So a little more work for me there. > <snip/> > > > > Jeremias Maerki -- Vincent Hennebert Anyware Technologies http://people.apache.org/~vhennebert http://www.anyware-tech.com Apache FOP Committer FOP Development/Consulting
