Printing in firefox (Debian/1.5.dfsg+1.5.0.1-2) is 'hosed' with lprng too, so this is not CUPS-specific.
It is interesting to see how exactly it is hosed. The following results explain some of the conflicting reports: Test A. ======= 1. Remove prefs.js from the firefox default directory. 2. Start firefox. 3. print page to file using PostScript/Default (i.e. CUPS, if you have that). Succeeds. 4. print same page to file using xprint (lp@:64). Fails. 'Paper size is not supported by printer'. 5. Stop firefox. Test B. ======= 1. Remove prefs.js from the firefox default directory. 2. Start firefox. 3. print page to file using xprint (lp@:64). Succeeds. 4. print same page to file using PostScript/Default. Fails. 'Paper size is not supported by printer'. 5. Stop firefox. So it is whatever you used first, from a 'virgin' situation, that works (and will keep working afterwards). I noticed that in the new firefox the 'Postscript/Default' has been changed; it now uses Freetype printing by default, and thus can print international pages. So we are closer to being able to get rid of xprint (/etc/init.d/xprint stop or update-rc.d -f xprint remove); then X must be restarted, otherwise there will be long delays while firefox keeps looking for the missing xprint. Now only PostScript/Default will be offered. Unfortunately, the print results with PostScript/Default, although better than they used to be, are still not quite up to the standard of (properly tuned) xprint. For instance I noticed some problems with printing left and right (UTF-8) single quotes, and with Korean. But this may also be a matter of tuning. Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
