Tomohiro KUBOTA wrote on 2002-08-26 08:48 UTC:
> The first is that simply using *-iso10646-1 fonts as defaults.
This could already be achieved by changing in /usr/lib/X11/fonts/misc/fonts.alias
the line
fixed -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
to
fixed -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
This was my goal many years ago, when I started with the misc-fixed
extension project and had no idea, how awful the X font system really
is. Unfortunately, merely changing "fixed" turned out to be not feasible
because
a) The X protocol is very inefficient in handling sparse 16-bit encodings.
b) Some legacy applications were unfortunately hardwired to assume that
"fixed" is an 8-bit font.
I think a) is the more critical reason, and a 16-bit font should be used
by xterm by default only, if a better font API such as Xft is used instead of
XLoadQueryFont().
> The second solution is to implement UTF-8-specific font configuration
> items, like "uFont", "uFont2", "uWideFont4", and so on.
This is a very good idea, and I remember that it was discussed and
welcome here before. I also had thought that someone had already written
a patch to do this, or had planed to do so, but apparently it never made
it into xterm. Using an independent set of font resource entries in
UTF-8 mode seems the right thing to do to me.
> I think the second one is better, though the first one is simpler and
> not very harmful. However, I don't have enough time to work on these
> solutions.
I agree that the second solution is what should be done (but I don't have
the time to submit a patch myself either).
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
