On Sat, 2006-09-16 at 17:15, Martin-Éric Racine wrote: > la, 2006-09-16 kello 20:21 +0800, Dan Jacobson kirjoitti: > > Package: cups-pdf > > Version: 2.4.1-1 > > Severity: normal > > > > Support UTF-8, so one can do > > $ date|lp > > and not have characters missing. > > Good point. > > However, I am not convinced that CUPS-PDF is to blame, since printing > UTF-8 text works fine from GNOME. Here, I regularly mix Cyrillic and > Latin characters, a combination that clearly requires UTF-8 support. > > I suspect that how CUPS clients and Ghostscript select fonts affect the > absence or presence of certain characters, thus why I'm copying this to > the CUPS and Ghostscript maintainers for comment. > > The CUPS-PDF author is already subscribed to this package's PTS and can > probably also contribute answers to this bug report.
Hi, I agree that this is most likely not the fault of CUPS-PDF itself but one of the other programs it uses. You might want to try a different postscript PPD file that is known to work with your charset (CUPS-PDF will accept any PPD file that creates postscript code). In order to track down the issue it would be helpful to know where the error occurs: $ date|enscript -o date.ps creates a PS-file with the date-sting (you can also use e.g. a2ps instead of enscript). Printing this file to CUPS-PDF set up without a PPD file (i.e. raw queue) will result in a PDF: if there the characters are mangled it is a issue with the setup of ghostscript, if there everything is fine it is probably due to the PPD file. Volker -- 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)
