On Fri, 2006-09-22 at 11:15 +0200, Jan Willem Stumpel wrote: > Xorg 7.1 has appeared in unstable, and now xprint works again, in the sense > that it no longer crashes Mozilla and Firefox. > > But the font selection is still just as bad as before;
Thanks for the testing. Now at least we've restored Xprint in X11R7 to the same level of "working" order we had in X11R6. It's a progress of sorts, at least. > i.e. you need > both the removal of Xprint's own fonts, and some tweaking of > userContent.css, otherwise you do not get acceptable prints. OK, this is where the interesting work starts. Ultimately it's going to come down to me (if not someone else) rolling my sleeves up and getting my arms grubby deep within the bowels of the Xprint internals. We'll have to mark out exactly what it's doing, font by font, glyph by glyph, postscript directive by postscript directive. Unfortunately it's a long term project since I'm no expert in font or postscript internals. For reference, while I have been able to verify the problems, especially with the spacing problem, most of the way along, that problem has now disappeared from my system with the full installation of X11R7.1. Print quality (measured by print to paper and print to PDF) is now comfortably acceptable for me. The spacing problem on www.debian.org, for instance, just disappeared the other week after we finished the 7.1 transition. That's without any of the font or css tweaking you mentioned. The only odd behaviour I'm seeing at the moment is that font types sometimes get switched around. For instance at the moment firefox displays the cyrillic links at the bottom (Bulgarian, Russian) in serif, but Xprint prints them using a Typewriter (courier) font for some reason. Other pages print similarly for me, printing fine apart from sometimes switching serif for sans-serif. I suspect solving this glitch will also solve the other problems we've been seeing. What is curious to me is that the glitch is acceptably "small" in this way for me, while its manifestation on your system is much larger. > And whatever I do, Mozilla and Firefox still cannot print MathML on Linux > correctly. Strange, because MathML printing is supposed to be one of > the 'selling points' of xprint. This problem is subtle. I tested some MathML on the new "working" Xprint, e.g. http://www.mozilla.org/projects/mathml/demo/texvsmml.xhtml . Now firefox itself renders mathml defectively, even after manually installing Mathematica fonts as directed on the mozilla.org pages, the pages are not rendered satisfactorily on screen, with some symbols missing, and superscripts misaligned. Printing the same page with Xprint however, some symbols are still missing but others are rendered, and the alignment of superscripts is more or less correct. That is, in this case Xprint does a better job of rendering MathML than firefox itself does on screen! It's hard for more to evaluate Xprint's MathML handling further when the browser can't do it on screen anyway. So firefox's MathML support is completely and utterly stuffed. Mozilla (1.7.13) does a much better job on screen. Here Xprint from mozilla is near perfect until #12 after which it fails (goes blank on the remaining samples). At the same time mozilla printing with "default printing" (not Xprint) misprints from sample #3, although it makes an attempt at all samples. Xprint from firefox rendered all samples, but with some misprinting, e.g. vertical brackets are only one character high instead of surrounding the full height of the matrices in #23. I think we can still sustain the claim that Xprint deals with MathML better than "default printing". Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
