> 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?
It's msttcorefonts stuff, via fontconfig. > (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) What I actually tried to use was Times New Roman, however it somehow got substituted with Times in the resulting postscript file. No clue why. > > 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. Again I really have no idea how KDEPrint (I think that's what it's called), CUPS and fontconfig are supposed to work together. > 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. I may do that when I get time, but like I said the real question is whether other people see this problem. If anyone else is using a similar setup, they can test both KDE and non-KDE fontconfig programs and see what they get. Also I really wish there was any kind of document describing how defoma, fontconfig, ghostscript, CUPS, KDEPrint, and so on are meant to work together. Or are they?.. -- Kirill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
