Edmund GRIMLEY EVANS wrote on 2000-08-12 17:01 UTC:
> Markus's UCS fonts seem to confuse Mozilla even if I rename the
> fonts.alias file. With ucs-fonts/ on the font path, Mozilla displays
> apparently double-width boxes instead of us-ascii chars in various
> places.
First guess:
Could this be the ancient GTK+ 1.2 bug, namely that they load the
default fonts with an encoding of *-*, and if they get a font that
contains a single character > 0x255, they treat everything like a JIS
font with EUC decoding? The fix in this case is to explicitly specify
that you want to have *-iso8859-1 fonts, otherwise the *-iso10646-1
fonts come earlier in the alphabetic list of fonts, get therefore
selected and activate the brain-dead JIS font machinery in GTK+ 1.2.
Many X11 applications are full of font bugs around the naive assumption
that every 16-bit font looks like a JIS X0208 font. Xfontsel had another
of these, and I wonder how many more there are.
The font
-Adobe-Helvetica-Medium-R-Normal--12-120-75-75-P-67-ISO10646-1
is not installed any more with the ucs-fonts package, which could be the
reason why an old ucs-fonts package might be the problem. However,
upgrading to a newer ucs-fonts package is *NOT* the solution, because we
will add the ISO10646-1 versions of the Adobe and B&H fonts in a few
weeks to XFree86 anyway and the same bug will then show up again. The
fix must be in the application: Either say that you want ISO8859-1, or
make sure that if you get a 16-bit font, that you can handle if it turns
out not to be a JIS font.
Please hunt down and report the reasons for this problem, because it
could turn out to be a significant problem.
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
