Keld, > Maybe there are flaws in 14651, but it is ISO 14651 which is > used in Linux.
That is a problem, not a feature. While UAX 10 is conforming to 14651, it does specify a number of requirements in addition to 14651. Specifically, for Thai, Lao, and combining characters support. > > > and the ISO TR 14652 locale standard. > > > > 14652 is NOT a standard. It is also very unlikely to ever > develop into one. > > Keld, please stop promoting it as a standard, when you very > well know > > that it is NOT a standard. > > It is as much a standard as Unicode in the generic sense of the word > "standard", but it is not an ISO standard. Please understand that. It's an ISO TR that became a TR because it FAILED to become an ISO standard. Please understand that. ... > The mappings used are at least also from the RFC 1345 (recode uses that) > or the IS 15897 which uses many if the same names and mappings. > Specifically I have seen that Linux is *not* using the Unicode data > because of copyright issues. Hmmm. From http://www.unicode.org/Public/UNIDATA/UnicodeCharacterDatabase.html: Limitations on Rights to Redistribute This Data Recipient is granted the right to make copies in any form for internal distribution and to freely use the information supplied in the creation of products supporting the UnicodeTM Standard. The files in the Unicode Character Database can be redistributed to third parties or other organizations (whether for profit or not) as long as this notice and the disclaimer notice are retained. Information can be extracted from these files and used in documentation or programs, as long as there is an accompanying notice indicating the source. I don't see this as restrictive for use in Linux. I'm sure Unicode consortium would like to see its data being used also in open source project, like Linux. Note that IBM has its own open source project on Unicode support (ICU). Kind regards /kent k -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
