Created attachment 8012 [details] Source PCL file Hi, I am trying to convert the attached file to a PDF with this command: pcl6.exe -J"@PJL SET PAPER=A4" -sDEVICE=pdfwrite -dTextAlphaBits=4 -dNOPA USE -sOutputFile="output.pdf" "Auftrag1_PCL-Quelldatei.prn" ... with this result: glyph index c0000000 out of range glyph index c0000000 out of range glyph index c0000000 out of range glyph index c0000000 out of range It seems that some of the text is not properly printed/mapped like the top-left-most headline. If this is not a bug - can you give me some hints how to track down the problem? Thanks!
(In reply to comment #0) > pcl6.exe -J"@PJL SET PAPER=A4" -sDEVICE=pdfwrite -dTextAlphaBits=4 -dNOPA > USE -sOutputFile="output.pdf" "Auftrag1_PCL-Quelldatei.prn" > It seems that some of the text is not properly printed/mapped like the > top-left-most headline. > > If this is not a bug - can you give me some hints how to track down the > problem? Try using a current version of the software, 9.04 was released 2 months ago and is the current release. TextAlphaBits only affects rendering, don't us it with pdfwrite.
Thank you. 9.04 produces the same output and message. What I don't understand - how to use for example the "-dPDFWRDEBUG" switch? Where can I see/find the log? Thanks.
(In reply to comment #2) > Thank you. 9.04 produces the same output and message. Well the current master code works for me, the output is the same as the rendered output. > What I don't understand - how to use for example the "-dPDFWRDEBUG" switch? I'm not aware of such a switch, where did you find it documented ? > Where can I see/find the log? The PostScript back channel.
Hm, what does it mean, it works for you? It works for me too basically, but the mentioned string ("Autohaus Diehl..") is pixelated (see when zoomed) and can't be selected within a PDF viewer. -- I just assumed that there might be the same switched as for Ghostscript, like mentioned here: http://www.ghostscript.com/doc/current/Use.htm#Debugging
(In reply to comment #4) > Hm, what does it mean, it works for you? It works for me too basically, but the > mentioned string ("Autohaus Diehl..") is pixelated (see when zoomed) and can't > be selected within a PDF viewer. That simply means that the text isn't 'text'. You said: "It seems that some of the text is not properly printed/mapped like the top-left-most headline." For met the appearance is the same as the rendered page, so I don't see a problem. There is absolutely no guarantee that what you see as text is actually text, it could easily be an image. pdfwrite is no capable of turning an image in the source into text in the destination. Is there some reason to think that the 'text' in that location is text ? It will take some considerable time for me to reduce a 3 page PCL file, mostly text, to the basic offending area to determine whether there is in fact any actual text in the input file.
There is text representing 'Autohaus Diehl..' from the upper-left of page 1, however the characters are embedded, uses symbol set 16A, and the PCL driver generated code points which were not a precise match to ASCII, so Autohaus in the PCL became 'Dxwrkdxv#Glhko...' starting at hex offset 72677.
Meant decimal offset 72677 (from within a hex editor).
(In reply to comment #6) > There is text representing 'Autohaus Diehl..' from the upper-left of page 1, > however the characters are embedded, uses symbol set 16A, and the PCL driver > generated code points which were not a precise match to ASCII, so Autohaus in > the PCL became 'Dxwrkdxv#Glhko...' starting at hex offset 72677. This is why the text is not searchable. The reason that it is bitmapped is because the original font in the PCL is a bitmap font. As to why Acrobat cannot highlight the text, that is a question for Adobe....