On Thu, 2005-10-06 at 10:49 +0100, Toby Blake wrote: > [kant]toby: diff WORKING-firefox.output.ps BROKEN-firefox.output.ps|head -24 > 90c90 > < /FontName /Utopia-Regular_iso8859-1 def > --- > > /FontName /Utopia-Regular_iso10646-1 def >
Interesting. This could be important: it looks from this that the heart of the problem is in the font encoding. For some reason a unicode (UTF-8, or iso10646-1) environment is causing the problems. Postscript is older than unicode, there may be some problem adapting. I'm no Postscript expert either so I can't speak knowledgably. You could try printing a chart or two from http://www.unicode.org/charts/ and check it's OK. Although those charts are PDF not Postscript, not quite the same thing. It would be helpful to get a sample postscript file containing unicode glyphs from somewhere. If this is the right line of reasoning, then I think the options are: 1) Postscript has not been arranged to handle iso10646-1 adequately. Seems unlikely but. I've had 2) The font /Utopia-Regular_iso10646-1 itself is broken. Not likely, you're only using the latin1 section of it anyway. 3) Printers are old and can't handle postscript containing iso10646-1. Probably not the case since you'll be able to print to file and see the same problem using gv, correct? 4) Xprint is screwing up the way it handles font encoding. Curious, because the whole attraction of Xprint for me is that it can handle multiple foreign languages at once (the same problem that unicode solves at the encoding level). Xprint's doing something right, but as you've noticed there's still more work to do. > > Starting with a completely vanilla firefox profile (having moved the > ~/.mozilla directory out of the way), everything printed fine. > However, if I then go to Edit->Preferences, General, Fonts and Colors > and change one of the font settings here - this leads to the faulty > postcript being produced, which makes absolutely no sense to me. For > instance, if I make an extremely trivial change, such as changing the > monospace font size from the default (12) to 14, this is enough to > make Firefox/Xprint produce the faulty postscript. Note that if I > change the setting back to 12 again, it *still* produces dodgy > postscript, but if I quit firefox, edit prefs.js to remove the lines > it added when I changed the font size from 12 to 14 (which are... Ah yes, we noticed this on Debian too. I'm "glad" it's not just us... you're seeing the same problem on Redhat. One would think from this behaviour that the bug is in Firefox, not Xprint. It's a complex problem *sigh* I don't think you described what exactly your printing problem was. What appeared on paper when the bad postscript went through? Drew _______________________________________________ Xprint mailing list [email protected] http://mozdev.org/mailman/listinfo/xprint
