On Tuesday 26 November 2002 06:38 am, Bruno Haible wrote: > Jason Maiorana wrote: > > > Also, there is the problem that its really not possible to show both > > > chinese and japanese together in a simple text document, because no > > > one font can show chinese, simplified chinese, and japanese all at > > > once. > > No single font can, and that's why these language tags have been added > to Unicode 3.2.
Nonsense. There are numerous fonts covering the entire CJK Unified Ideographs block of Unicode, and have been some since MS Arial Unicode in the time of Unicode 1.0. This includes Big5 for Traditional Chinese, GB3212 for Simplified Chinese, the JIS standards for Japanese, and KSC-5601 for Korean, and a good deal more. The results of using these fonts are ugly, but no worse than using the Latin alphabet sections of Chinese and Japanese fonts for English. Since I am creating Unicode plain-text documents that combine Chinese, Korean, and Japanese, I have some experience in using such fonts. When I can, I use culturally-appropriate fonts for each language and country. When I can't, I manage, and so do my readers. There are commercial fonts covering the A and B extensions, and will be for anything else that gets added. Various groups and individuals are working on Free fonts for all of these characters. > Karl Eichwalder replied: > > The rest can go for a tagged file format > > Unicode 3.2 _is_ this tagged file format. > > Bruno Language tags are deprecated. Some people argue this claim, and are fighting it, but it is made at the highest levels of the Unicode organization. The only tagged format with a real future is XML, IMNSHO. -- Edward Cherlin Generalist "A knot! Oh, do let me help to undo it!" --Alice in Wonderland -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
