At Sat, 11 Jun 2005 12:14:17 -0400, Kirill wrote: > I am trying to set up an HPLJ 1012 to print from KDE apps (KWord, Konqueror) > using CUPS. I am getting most fonts messed up by ghostscript (gs-esp). I've > been struggling with it for a whole week now with very little progress so far.
> When I print to a PostScript file and then try to view it with ghostscript, > almost all fonts are totally messed up, both the typeface and letter spacing > is bad. Same with print preview and on paper. > > Printing with Times New Roman in regular, italic, bold and bold italic and > then > looking in the .ps file I see: > > %%DocumentFonts: Times-Bold Times-Italic Times-Roman Times-BoldItalic > > Then I run gs on it, and it says: > > ESP Ghostscript 7.07 (2003-07-12) > Copyright 2003 artofcode LLC and Easy Software Products, all rights reserved. > This software comes with NO WARRANTY: see the file PUBLIC for details. > Loading NimbusRomNo9L-MediItal font from > /var/lib/defoma/gs.d/dirs/fonts/n021024l.pfb... 2149928 764523 1763096 439747 > 0 done. > Loading NimbusRomNo9L-ReguItal font from > /var/lib/defoma/gs.d/dirs/fonts/n021023l.pfb... 2307264 878740 1763096 385118 > 0 done. > Loading NimbusRomNo9L-Medi font from > /var/lib/defoma/gs.d/dirs/fonts/n021004l.pfb... 2444504 1012113 1783192 > 401765 0 done. > Loading NimbusRomNo9L-Regu font from > /var/lib/defoma/gs.d/dirs/fonts/n021003l.pfb... 2581744 1137566 1783192 > 387726 0 done. > >>showpage, press <return> to continue<< > > Result: it shows the page with Nimbus Roman instead of Times New Roman, and > all letter spacing is fubared. URW Nimbus Roman is supposed to be metric-compatible with Adobe's Times New Roman, so this substitution is exactly what is supposed to happen. (I'm assuming here that you haven't gone out and bought the real Adobe fonts) Having the letter spacing wrong probably means the original kword app somehow didn't get the font metric information correct, however. Has this ever worked for you in the past? My only experience with kword was many years ago and I too was appalled at the print quality although I never investigated it. > When I format all text with Nimbus Roman, I get: > > %%DocumentFonts: NimbusRomanNo9L-Bold NimbusRomanNo9L-Italic NimbusRomanNo9L > NimbusRomanNo9L-BoldItalic > > in the .ps file, and then > > ESP Ghostscript 7.07 (2003-07-12) > Copyright 2003 artofcode LLC and Easy Software Products, all rights reserved. > This software comes with NO WARRANTY: see the file PUBLIC for details. > Can't find (or can't open) font file > /usr/share/ghostscript/fonts/NimbusRomanNo9L-Italic. > Can't find (or can't open) font file NimbusRomanNo9L-Italic. > Substituting font Times-Italic for NimbusRomanNo9L-Italic. > Loading NimbusRomNo9L-ReguItal font from > /var/lib/defoma/gs.d/dirs/fonts/n021023l.pfb... 2170024 782484 1763096 440505 > 0 done. > Loading NimbusSanL-ReguItal font from > /var/lib/defoma/gs.d/dirs/fonts/n019023l.pfb... 2267072 876716 1763096 445071 > 0 done. [...] > > and everything shows up in Nimbus Sans. Hrm. ghostscript (via Defoma and gsfonts.hints) only knows this font as "NimbusRomNo9L-ReguItal". Where did kword get the name "NimbusRomanNo9L-Italic" from? Since Nimbus Roman isn't one of the base postcript fonts, Kword (or whatever KDE component created the postscript) should have embedded the font in the produced postscript file and ghostscript would not have had to look for the font data itself. Have you by any chance turned some font embedding option off? (I'd be extremely surprised if it was off by default) > Bold, italic and bold italic are shown fine, but normal Georgia it > can't find because in defoma aliases it's known as Georgia-Regular > rather than Georgia. [similar with other font families] It seems that kword is working off a totally different list of font names than ghostscript. This would be just fine if kword embedded the font data in the postscript output, but it isn't and its expecting ghostscript to be able to find the font data under the same font names its using. Since I don't have kword installed anywhere (and don't really want to lug in all of KDE just to have a look), I'm CCing this to the kword maintainer. Ben, how does kword find font information when producing postscript? At the moment, it looks like Defoma (and ghostscript) are doing the right thing and I'm thinking of reassigning this bug to kword. Kirill, As a temporary workaround, you could manually edit /etc/defoma/hints/gsfonts.hints, etc and add the aliases that Kword is assuming exist. Just run "defoma-font reregister-all $hintfile" after editing a hintfile for defoma to act on your changes. -- - Gus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
