[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Registration of Windows Charsets (Thai, Japanese, GBK,Korean,Big-5)

Although it would be great if the original registrant or owner of a
charset supplied lots of helpful information about the charset, we
might make more progress if anybody on this list were allowed to make
suggestions for additions to the "Additional information" section, or
even to the other sections, as long as there is consensus.

Having said that, here are my suggestions/comments for further discussion:

Unicode/10646 mapping tables:

http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WindowsBestFit/

Also, it is possible to see how these charsets have grown over time by
comparing with older tables at:

http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/

Windows-936: already registered as an alias of GBK.

Windows-932: related to Shift_JIS and Windows-31J.

Windows-1252: related to ISO-8859-1, ISO-8859-1-Windows-3.0-Latin-1
and ISO-8859-1-Windows-3.1-Latin-1.

Windows-1254: related to ISO-8859-9 and ISO-8859-9-Windows-Latin-5.

Windows-1250: possibly related to ISO-8859-2-Windows-Latin-2.

Windows-874: related to ISO-8859-11.

Windows-950: related to Big5 and possibly Big5-HKSCS.

Windows-949: related to EUC-KR.

Erik

On 10/8/06, Martin Duerst <duerst@it.aoyama.ac.jp> wrote:
>   Even if a concern is 'minor', if it can easily be addressed
>   with a comment, it's best to do so. An example of this would
>   be the comment from Reuel Robrigado
>   (at http://mail.apps.ietf.org/ietf/charsets/msg01512.html).
>   Just adding a comment about the typo in Nadine Kano's book
>   will help all implementors a lot. Following the minimum
>   registration procedures only may not be enough.