Alex Satrapa said: > On 13 Dec 2005, at 17:51, Martin-Éric Racine wrote: > >> 1) Ghostscript versions that you use? >> dpkg -l gs-esp > > 11:19 [0|16]% dpkg -l gs-esp > [snip] > ii gs-esp 7.07.1-9 The Ghostscript PostScript > interpreter - ESP ver > >> 2) DPI setting of your cups-pdf printer in CUPS preferences? > > DPI is set to 1200 default in the PPD. > >> Note that CUPS-PDF is completely dependant [on] >> Ghostscript for the printing quality. > > This might be a ghostscript problem then, since the text is being > garbled - as in encrypted, not drawn badly. For example, your message > to me started with the text: > > severity 343145 important > thanks > > while on the PDF version printed via CUPS-PDF, the starting text was: > > > > &2013! > > So by "garbled" I don't mean "printed unclearly", I mean "replaced with > meaningless rubbish" or perhaps even "encrypted". > > The layout is great - almost pixel for pixel, but the actual glyphs > that make up the "text" are replaced with other symbols. In fact, > having a closer look at the text, it looks almost like a > transliteration error: > >> Note that CUPS-PDF is completely dependant upon the DPI resolution >> configured in CUPS via the printer management interface and upon >> Ghostscript for the printing quality. > > is replaced with: > >> W/&"(&20&(UV@>[EMAIL PROTECTED](%!(A/-.8"&"8'(D"."1D01&(C./1(&2"([EMAIL >> PROTECTED]($"!/8C&%/1 >> A/1E%BC$"D(%1(UV@>(#%0(&2"(.$%1&"$(-010B"-"1&(%1&"$E0A"(01D(C./1 >> R2/!&!A$%.&(E/$(&2"(.$%1&%1B(XC08%&'G( > > If - as you already suggested - this is something I should take up with > the gs-esp maintainer, please let me know. Otherwise I can try to > capture the PostScript being sent from my computer to CUPS, in order to > further test the CUPS-PDF printer - would it be enough to "Stop" the > printer and simply snarf the files from the CUPS spool? >
This might also be due to some settings for character encoding. I suggest the following tests: 1st: print the CUPS printer test page to CUPS-PDF and check whether there the text appears properly 2nd: create a postscript from a simple text file (e.g. by a2ps or encode), check it with ghostview and print this postscript to CUPS-PDF 3rd: if 1st and 2nd work, to get to the PostScript file that is used by CUPS-PDF you will have to edit the source code of cups-pdf: close to the end of the code there are the lines: if (unlink(spoolfile)) log_event(CPERROR, "failed to unlink spoolfile (non fatal)", spoolfile); else log_event(CPDEBUG, "spoolfile unlinked", spoolfile); Just remove or comment out this block, re-compile cups-pdf and the spoolfile will stay after the printout. -- Volker Christian Behr Experimentelle Physik V (Biophysik), Physikalisches Institut Universitaet Wuerzburg, Am Hubland, 97074 Wuerzburg, Germany Office: Room F-069a +49-931-888-5766 (phone) +49-931-888-5851 (fax)
