Brunoe Haible wrote: Jason Maiorana wrote: JM> Also, there is the problem that its really not possible to show both JM> chinese and japanese together in a simple text document, because no JM> one font can show chinese, simplified chinese, and japanese all at JM> once.
BH> No single font can, A single font of some advanced types can do it. For instance, an opentype font can have multiple glyph variants for a single character one of which can be selected (depending on the locale, language, script or whatever external info. available) by intelligent rendering engines like Pango, Uniscribe, Graphite and ATSUI. BH> and that's why these language tags have been added BH> to Unicode 3.2. No, plane 14 language tags had been a part of Unicode/ISO 10646 long before the release of Unicode 3.2 this year. The Unicode 3.0 has an extensive information on it in section 5.11 'Language Information in Plain text' (p. 114 - p. 116).(see also UTR #7?) Needless to say, ISO 10646-1:2000 also has a devoted section to Plane 14 tags. Karl Eichwalder replied: KE> The rest can go for a tagged file format BH> Unicode 3.2 _is_ this tagged file format. UTC is now considering deprecating plane 14 language tag. Deprecating it does not mean that it cannot be used, but that its use will be strongly discouraged. If you have a strong case against its deprecation, you may want to express your opinion to UTC because it's under public review until sometime early next year. Jungshik -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
