At Sun, 28 Aug 2005 08:42:30 -0400, Kirill wrote: > > 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? > > Not with Times New Roman. But if after editing gsfonts.hints (file > attached) I select NimbusRoman, it displays and prints just fine. > > I edited msttcorefonts.hints as well (file attached), which helped > solve some of the substitution problems, but not the spacing problem > with Times New Roman in KWord.
Hrm. I wonder why Kword has a different set of metrics for Times. Is this the (postscript standard) "Times-Roman" or microsoft's "Times-New-Roman" font you were testing against here? (Your original report had Times being correctly replaced by Nimbus Roman but produced with the wrong metrics. Here you mention Times New Roman - a different font in the eyes of Defoma/postscript/fontconfig) > > Hrm. ghostscript (via Defoma and gsfonts.hints) only knows this font > > as "NimbusRomNo9L-ReguItal". Where did kword get the name > > "NimbusRomanNo9L-Italic" from? > > It seems these names are somehow related to fontconfig font names. > Output of fc-list also attached. The GUI drop down widget-thing you select the fonts from almost certainly comes from fontconfig. I hope the KDE printing stuff is doing something better than just removing whitespace from the fontconfig names and hoping that makes a valid postscript FontName. > Looks like at least the KDE printing component thinks that what it > outputs are valid aliases for the existing fonts. I have no idea > how it comes up with them. But no embedding should take place here. So how do you print to a remote CUPS printer spooler for example, where Arial (or whatever) simply may not be available? The KDE printing component really should be embedding the font data in the generated postscript. > You won't be able to blame the substitution problem on KWord alone, > since other programs give the same results (Konqueror and so on). I expect Kword's print output is generated via some common KDE component, so all KDE print output would suffer the same problem. Try comparing against another fontconfig-using-but-not-KDE app like mozilla or some gnome program. -- - Gus
pgprscKmli3C4.pgp
Description: PGP signature
