Kaixo! On Sun, Sep 30, 2001 at 09:10:53AM -0700, Keith Packard wrote: > > > For a Japanese document, the font matching code should first > > > look at Japanese fonts not Simplified Chinese, Traditional > > > Chinese, or Korean fonts. > > > > This is of course true for any language. > > Han unification arguably makes these four character sets the most > problematic. What this means is that font selection must be done by a > layer which has language or locale information, not down inside the > Unicode-only Xft library.
That is only relevant to fonts having various versions of the same characters; eg an OpenType font with *both* Japanese and Chinese versions of most han characters. In all other cases there is no real need to know the language: the font names are different for Chinese and Japanese fonts; so there can't be undesired behaviour: The font matching the requested name must always be the first in priority. > problematic. What this means is that font selection must be done by a > layer which has language or locale information, not down inside the > Unicode-only Xft library. Yes. Xft should only answer to requests of font names (and style, size, etc), nothing more. If the language used by the user requires some specific choice of fonts; it is to the program to request the right ones (for example, the requested fontset could be made a translatable ressource, so depending on the language of the user interface the better fonts will be used). And of course the user must always be able to override those defaults, and even use horribly untypographically looking ones if he wants. -- Ki �a vos v�ye b�n, Pablo Saratxaga http://www.srtxg.easynet.be/ PGP Key available, key ID: 0x8F0E4975 _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
