JS> Even with this weakness, Xprint is by far the best printing
JS> solution available at the moment for Mozilla under Unix/X11
JS> because postscript printing module of Mozilla does not work very
JS> well yet
Xprint might work for CJK fonts, although I'm a little bit suprised at
your enthusiasm for the thing. There is no way, though, how Xprint
could work for complex scripts without standardising on glyph
mappings. There is also no way[1] how Xprint could implement
dynamically generated fonts, as required for example by CSS2.
The right approach is obviously to do incrememtal uploading of fonts
to the printer at the PS level, as the Mozilla folks are trying to do.
I'm a little bit suspicious about their choice to use Type 42 CIDFonts
for that, though, as it will require many users to rasterise every-
thing with ghostscript on the host, with all the ensuing performance
and printing quality issues.
Juliusz
[1] Without a major protocol extension. Way, way more complex than
what Xft does -- basically you'd have to duplicate the most complex
part of PS, the font interfaces, at the X11 protocol level.
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
