On Sat, 6 Apr 2002, David Starner wrote: > On Sat, Apr 06, 2002 at 07:16:50PM +0900, Gaspar Sinai wrote: > > o There are errors: > > Unihan-3.2.0.txt: > > U+9B1C kJIS0213 2,93,27 > > Should be: > > U+9B1D kJIS0213 2,93,27 > > And there won't be errors in whatever map you're using? That file was > available for months in beta test, and they still accept fixes, which > they'll get to when they're preparing another release.
That is the whole point - I have no map that I can trust. Browsing though thusands of glyph images make my eyes burn. It is very difficult for me to tell if this is an error. > > I would like to have local encoding -> Unicode character mappings > > published by the Consortium - otherwise I am not convinved that > > Unicode is supporting characters in national standards - which may > > question its usability. > > Every major non-Asian character standard has a complete mapping between > it and Unicode either published with its ISO-2022 registration or with > its RFC registration. As far as I can tell, none of the major Japanese > standards included a mapping with their ISO-2022 registration, which may > question _their_ usability. I give you one example why Unicode Cosortium should care. The only reason I made Yudit is to write Hungarian and Japanese. I found out that I can display glyphs properly if I use Unicode if I use the mapping to fonts conforming to JIS or Hungarian Standard. This way I will not lose anything. If it was not possible to represent Unicode text with glyphs in the local JIS standard I would not even have bothered to use Unicode in my program. If Unicode Consortum does not provide a map for JISX0213 I will transform the whole JISX0213 to a Unicode Private Area above BMP. I already use Private Use area in Yudit for old Hungarian because it old Hungarian is a proposal since 1998 - this is not new. I wish I did not need to use any PUA codes - this will make text non-portable - but when supporting character standards local standard comes *first* and Unicode comes *second*. Unicode Consortium are just plain wrong if they think that someone will throw away the national standard and replace it with nothing. National Standards do not need to prove that Unicode can be transformed to them, the local standard body has no responsibility to make the mapping. If Unicode Consrotium are not publishing the maps it will create greater mess then there really is. Gaspar -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
