> From: Carl W. Brown [mailto:[EMAIL PROTECTED]] > > It seems that the proper solution is to use ISO 15924 which > is part of the > new RCF-1766 sublanguage specifications. However to my > amazment that do not > have separate script designations for traditional and > simplified scripts. > Correct me if I'm wrong, but isn't such a designator unnecessary? GB encoded material is simplified by definition, likewise Big5 encoded material is traditional by definition, and Unicode has encodings for both glyphs of a simplified/traditional pair (note: I am oversimplifying here, since there is not a strict 1-1 traditional-simplified relationship). Therefore, encoding "traditional" or "simplified" as part of the character set would be, at best, redundant. /|/|ike
- Locale ID's again: simplified vs. traditional Steven R. Loomis
- Re: Locale ID's again: simplified vs. traditional Yung-Fong Tang
- Re: Locale ID's again: simplified vs. traditional Doug Ewell
- RE: Locale ID's again: simplified vs. traditional Carl W. Brown
- RE: Locale ID's again: simplified vs. traditional Ayers, Mike
- RE: Locale ID's again: simplified vs. traditional Peter_Constable
- RE: Locale ID's again: simplified vs. traditional Jukka . Korpela
- RE: Locale ID's again: simplified vs. traditional Michael Everson
- RE: Locale ID's again: simplified vs. traditional Marco . Cimarosti
- RE: Locale ID's again: simplified vs. traditional Marco . Cimarosti
- RE: Locale ID's again: simplified vs. traditional Marco . Cimarosti
- RE: Locale ID's again: simplified vs. traditional Carl W. Brown
- RE: Locale ID's again: simplified vs. traditional Thomas Chan
- RE: Locale ID's again: simplified vs. traditional Thomas Chan
- Re: Locale ID's again: simplified vs. traditional John Cowan

