to, 2005-12-15 kello 11:43 +0100, Volker Christian Behr kirjoitti: > On Thu, 2005-12-15 at 04:41, Alex Satrapa wrote: > > On 14 Dec 2005, at 20:23, Volker Christian Behr wrote: > > > > > 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 > > > > Test page works perfectly. > > > > > 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 > > > > I created a text file ("blah.txt") containing the characters "Blah", > > then used a2ps to create a PostScript file ("blah.ps"), a2ps blah.txt > > -o blah.ps. > > > > The PostScript file looks fine, and cups-pdf converts it to PDF just > > fine. > > Ok, so we seem to only run into a problem if the PostScript is generated > by CUPS (with the PPD). > > > > 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 ... > > > > Finished this - the postscript in the CUPS spool (/var/spool/cups) and > > the cups-pdf backend spool (/var/spool/cups-pdf/SPOOL) are identical > > (which seems reasonable enough), and both render fine in kghostview > > (I'm using KDE3 on my Linux workstations, Mac OS X 10.3 on my desktop). > > > > When trying to open one of the PostScript files in Preview (the Mac OS > > X equivalent of Kghostview) I get the error, "Can't create CMap > > Adobe-Identity-UCS2." Does this provide any hints as to the nature of > > the problem? > > > > I guess the next step is to go through the process that is automated by > > cups-pdf to figure out at what point the "damage" is being done. > > I do not know this error but it might be related to the problem. First I > would like to try to generate a PDF on the command line from the > spoolfile with options identicl to the ones CUPS-PDF uses. To do this, > execute the following command for <spoolfile>: > > gs -q -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -dSAFER > -sDEVICE=pdfwrite -sOutputFile=/tmp/testpage.pdf > -dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false > -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/prepress -c save pop -f > <spoolfile> > > Now gs should generate a PDF the same way as if invoked by cups-pdf. If > we still get garbled text we can debug without cups-pdf being involved > which will make things easier.
Alex: have you tried the above test? Could you please provide me and Volker with your results, so that we can resolve this issue? Thanks! -- Martin-Éric Racine http://q-funk.iki.fi
signature.asc
Description: Digitaalisesti allekirjoitettu viestin osa