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

[Martin Duerst]

Hello Mike,

Ned Freed and me just very recently have been appointed as IETF Charset
Reviewers, and are now together with IANA working on the backlog that
has piled up. IANA asked us to look at five registration requests that
you sent in last year or early this year (see below).

Can you please resend these registration requests with the following
corrections:
1) You don't seem to use the right form. The form for charset
registrations can be found at http://www.ietf.org/rfc/rfc2978.txt
(Section 5). In particular, you don't need a security section,
but you have to indicate whether or not the charset is suitable
for use in MIME text. Also, please make sure that the charset
name also appears in the registration request body, not only in
the Subject, and submit the registrations as plain text, in the
body of the email, not as an attachment.
2) Some of your registrations seem to refer to already registered
charsets but request an independent registration. For example,
you request "Windows-932" but in parentheses say "Japanese
Shift-JIS". However, Japanese Shift-JIS is already registered
and widely used with the label "Shift_JIS". What's the relation-
ship of your request to Shift_JIS? Is it supposed to be the
same, or is it different? If different, what's different?
Such explanations, which can help people a lot when they
try to understand the various registrations, should go into
the "Additional information:" field.

IANA also has mentioned some updates that you tried to make.
For the updates, please send in a registration form that contains
the new information that should be registered. In the "Additional
information" section, please mention that this is an update and
list up both the formal (e.g. change of contact person, change
of Web location for defining documents) and the material changes
(additions/clarifications of codepoints,...).

Many thanks for your collaboration. Please feel free to ask
us on the list or privately if you have any questions.
I hope that we can move these registrations forward quickly.

Regards, Martin.

>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-874 (Thai)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 779-782
>
>2) http://www.microsoft.com/globaldev/reference/sbcs/874.htm
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>---------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-932 (Japanese
>Shift-JIS)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 773-775
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>---------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-936 (Simplified
>Chinese GBK)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 776
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>
>---------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-949 (Korean)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 777
>
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>----------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-950 (Traditional
>Chinese Big-5)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 778
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.


#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp

[Mike Ksar]

Martin,

After two years I submit the request for registration new character sets and updating existing ones you one me to start from scratch?

Ned Freed provided me then with guidance as to which form I should use and which RFC to follow. If the forms changed since then it should be possible for you and Ned, as the new registrar's to recreate my submission using the data that I submitted. I even prepared a disposition of comments on the feedback. There is no reason that I see to restart from scratch.


Mike Ksar
________________________________________
From: Martin Duerst
Sent: Sunday, October 08, 2006 2:10 AM
To: Mike Ksar
Cc: ietf-***@iana.org; Ned Freed
Subject: Registration of Windows Charsets (Thai, Japanese, GBK, Korean, Big-5)

Hello Mike,

Ned Freed and me just very recently have been appointed as IETF Charset
Reviewers, and are now together with IANA working on the backlog that
has piled up. IANA asked us to look at five registration requests that
you sent in last year or early this year (see below).

Can you please resend these registration requests with the following
corrections:
1) You don't seem to use the right form. The form for charset
registrations can be found at http://www.ietf.org/rfc/rfc2978.txt
(Section 5). In particular, you don't need a security section,
but you have to indicate whether or not the charset is suitable
for use in MIME text. Also, please make sure that the charset
name also appears in the registration request body, not only in
the Subject, and submit the registrations as plain text, in the
body of the email, not as an attachment.
2) Some of your registrations seem to refer to already registered
charsets but request an independent registration. For example,
you request "Windows-932" but in parentheses say "Japanese
Shift-JIS". However, Japanese Shift-JIS is already registered
and widely used with the label "Shift_JIS". What's the relation-
ship of your request to Shift_JIS? Is it supposed to be the
same, or is it different? If different, what's different?
Such explanations, which can help people a lot when they
try to understand the various registrations, should go into
the "Additional information:" field.

IANA also has mentioned some updates that you tried to make.
For the updates, please send in a registration form that contains
the new information that should be registered. In the "Additional
information" section, please mention that this is an update and
list up both the formal (e.g. change of contact person, change
of Web location for defining documents) and the material changes
(additions/clarifications of codepoints,...).

Many thanks for your collaboration. Please feel free to ask
us on the list or privately if you have any questions.
I hope that we can move these registrations forward quickly.

Regards, Martin.

>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-874 (Thai)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 779-782
>
>2) http://www.microsoft.com/globaldev/reference/sbcs/874.htm
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>---------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-932 (Japanese
>Shift-JIS)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 773-775
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>---------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-936 (Simplified
>Chinese GBK)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 776
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>
>---------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-949 (Korean)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 777
>
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.
>
>----------------------------------------------------------------------------------------
>
>To: ietf-***@iana.org
>Subject: Registration of MIME character set name: Windows-950 (Traditional
>Chinese Big-5)
>
>Security Considerations
>Security issues are not discussed in this memo.
>
>Published specification:
>
>1) Dr. International "Developing International Software, Second Edition",
>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 778
>
>
>ISO/IEC 10646/Unicode equivalency table:
>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>
>
>Person & email information
>
>Mike Ksar
>Microsoft Corporation
>Email: ***@microsoft.com
>
>Address:
>One Microsoft Way,
>Redmond, WA 98052
>U.S.A.


#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp

[Martin Duerst]

At 04:13 06/10/09, Mike Ksar wrote:
>Martin,
>
>After two years I submit the request for registration new character sets
>and updating existing ones you one me to start from scratch?

Hello Mike,

I very much understand your frustration.
I would be quite frustrated, too, if I were in your position.

>Ned Freed provided me then with guidance as to which form I should use and
>which RFC to follow.

RFC 2278 was published in October 2000. I very much doubt that Ned gave
you any other reference.

>If the forms changed since then it should be possible
>for you and Ned, as the new registrar's to recreate my submission using the
>data that I submitted.

The IETF and the IANA do not work that way. IANA is the registrar,
but they do not understand character encodings. Ned and me are the
expert reviewers, i.e. we


>I even prepared a disposition of comments on the
>feedback. There is no reason that I see to restart from scratch.
>
>
>Mike Ksar
>________________________________________
>From: Martin Duerst
>Sent: Sunday, October 08, 2006 2:10 AM
>To: Mike Ksar
>Cc: ietf-***@iana.org; Ned Freed
>Subject: Registration of Windows Charsets (Thai, Japanese, GBK, Korean, Big-5)
>
>Hello Mike,
>
>Ned Freed and me just very recently have been appointed as IETF Charset
>Reviewers, and are now together with IANA working on the backlog that
>has piled up. IANA asked us to look at five registration requests that
>you sent in last year or early this year (see below).
>
>Can you please resend these registration requests with the following
>corrections:
>1) You don't seem to use the right form. The form for charset
> registrations can be found at http://www.ietf.org/rfc/rfc2978.txt
> (Section 5). In particular, you don't need a security section,
> but you have to indicate whether or not the charset is suitable
> for use in MIME text. Also, please make sure that the charset
> name also appears in the registration request body, not only in
> the Subject, and submit the registrations as plain text, in the
> body of the email, not as an attachment.
>2) Some of your registrations seem to refer to already registered
> charsets but request an independent registration. For example,
> you request "Windows-932" but in parentheses say "Japanese
> Shift-JIS". However, Japanese Shift-JIS is already registered
> and widely used with the label "Shift_JIS". What's the relation-
> ship of your request to Shift_JIS? Is it supposed to be the
> same, or is it different? If different, what's different?
> Such explanations, which can help people a lot when they
> try to understand the various registrations, should go into
> the "Additional information:" field.
>
>IANA also has mentioned some updates that you tried to make.
>For the updates, please send in a registration form that contains
>the new information that should be registered. In the "Additional
>information" section, please mention that this is an update and
>list up both the formal (e.g. change of contact person, change
>of Web location for defining documents) and the material changes
>(additions/clarifications of codepoints,...).
>
>Many thanks for your collaboration. Please feel free to ask
>us on the list or privately if you have any questions.
>I hope that we can move these registrations forward quickly.
>
>Regards, Martin.
>
>>To: ietf-***@iana.org
>>Subject: Registration of MIME character set name: Windows-874 (Thai)
>>
>>Security Considerations
>>Security issues are not discussed in this memo.
>>
>>Published specification:
>>
>>1) Dr. International "Developing International Software, Second Edition",
>>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 779-782
>>
>>2) http://www.microsoft.com/globaldev/reference/sbcs/874.htm
>>
>>
>>ISO/IEC 10646/Unicode equivalency table:
>>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>>
>>
>>Person & email information
>>
>>Mike Ksar
>>Microsoft Corporation
>>Email: ***@microsoft.com
>>
>>Address:
>>One Microsoft Way,
>>Redmond, WA 98052
>>U.S.A.
>>
>>---------------------------------------------------------------------------------------
>>
>>To: ietf-***@iana.org
>>Subject: Registration of MIME character set name: Windows-932 (Japanese
>>Shift-JIS)
>>
>>Security Considerations
>>Security issues are not discussed in this memo.
>>
>>Published specification:
>>
>>1) Dr. International "Developing International Software, Second Edition",
>>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 773-775
>>
>>
>>ISO/IEC 10646/Unicode equivalency table:
>>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>>
>>Person & email information
>>
>>Mike Ksar
>>Microsoft Corporation
>>Email: ***@microsoft.com
>>
>>Address:
>>One Microsoft Way,
>>Redmond, WA 98052
>>U.S.A.
>>
>>---------------------------------------------------------------------------------------
>>
>>To: ietf-***@iana.org
>>Subject: Registration of MIME character set name: Windows-936 (Simplified
>>Chinese GBK)
>>
>>Security Considerations
>>Security issues are not discussed in this memo.
>>
>>Published specification:
>>
>>1) Dr. International "Developing International Software, Second Edition",
>>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 776
>>
>>
>>ISO/IEC 10646/Unicode equivalency table:
>>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>>
>>
>>Person & email information
>>
>>Mike Ksar
>>Microsoft Corporation
>>Email: ***@microsoft.com
>>
>>Address:
>>One Microsoft Way,
>>Redmond, WA 98052
>>U.S.A.
>>
>>
>>---------------------------------------------------------------------------------------
>>
>>To: ietf-***@iana.org
>>Subject: Registration of MIME character set name: Windows-949 (Korean)
>>
>>Security Considerations
>>Security issues are not discussed in this memo.
>>
>>Published specification:
>>
>>1) Dr. International "Developing International Software, Second Edition",
>>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 777
>>
>>
>>
>>ISO/IEC 10646/Unicode equivalency table:
>>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>>
>>
>>Person & email information
>>
>>Mike Ksar
>>Microsoft Corporation
>>Email: ***@microsoft.com
>>
>>Address:
>>One Microsoft Way,
>>Redmond, WA 98052
>>U.S.A.
>>
>>----------------------------------------------------------------------------------------
>>
>>To: ietf-***@iana.org
>>Subject: Registration of MIME character set name: Windows-950 (Traditional
>>Chinese Big-5)
>>
>>Security Considerations
>>Security issues are not discussed in this memo.
>>
>>Published specification:
>>
>>1) Dr. International "Developing International Software, Second Edition",
>>Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 778
>>
>>
>>ISO/IEC 10646/Unicode equivalency table:
>>http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_19mb.asp
>>
>>
>>Person & email information
>>
>>Mike Ksar
>>Microsoft Corporation
>>Email: ***@microsoft.com
>>
>>Address:
>>One Microsoft Way,
>>Redmond, WA 98052
>>U.S.A.
>
>
>#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
>#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp


#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp

[Martin Duerst]

[An earlier version of this mail went off before being finished, sorry.
This is the completed version.]

At 04:13 06/10/09, Mike Ksar wrote:
>Martin,
>
>After two years I submit the request for registration new character sets
>and updating existing ones you one me to start from scratch?

Hello Mike,

I very much understand your frustration.
I would be quite frustrated, too, if I were in your position.
I'm very committed to make sure that delays as the ones you have
suffered won't occur anymore.

>Ned Freed provided me then with guidance as to which form I should use and
>which RFC to follow. If the forms changed since then

RFC 2278 was published in October 2000. I very much doubt that Ned gave
you any other reference.

> it should be possible
>for you and Ned, as the new registrar's to recreate my submission using the
>data that I submitted.

The IETF and the IANA do not work that way. IANA is the registrar,
but they do not understand character encodings. Ned and me are the
expert reviewers, i.e. we advise IANA on when we think a registration
is in good shape and consensus has been achieved about it on this
list. Preparation of the registrations, and improvement of the
registration forms based on comments on the this mailing list,
have always been the responsibility of the registrant.
Also, I have pointed out some missing information (e.g.
no information about "Suitability for use in MIME text:").
I'm not sure how I'm supposed to "recreate" that information.

Having volunteered for the job of charset reviewer (just a few weeks ago),
I'm very committed to make sure that the current backlog gets
discussed and moved forward as quickly as possible, and that we
don't see any delays anymore just because the reviewer is not around.

However, I have not volunteered to do work such as recreating
registration forms that the previous reviewer wouldn't have done
if he had been around, and that I wouldn't have done if I had
been a reviewer at that time.

Also, I'm not ready to accept any registrations that I think are
incomplete, can easily be substantially improved, or do not address
reasonable comments on this mailing list, even if these registrations
have started quite some time ago.

Obviously, I cannot speak for Ned.


>I even prepared a disposition of comments on the
>feedback. There is no reason that I see to restart from scratch.

Looking through my mail archives (from the time I was just a
participant on this list, in no official function), I have found
some mails in the June 2005 timeframe entitled

IANA Character Set Registration Submittal - Disposition of comments
also archived at:
http://mail.apps.ietf.org/ietf/charsets/msg01522.html

While this mail lists a series of filenames, neither the above
location nor my archive contain any of these files, while
earlier attachments from you got through in both places.

Also, the supposed "disposition of comments" looks like it
is just a summary statement (unless it was contained in the
missing files):

>>>>>>>>
I have met face-to-face and/or contacted people by email/phone who posed questions on the IANA Character Set Registration submittal that I sent out on March 15, 2005.

As I explained to the people that responded, I followed the registration
guidelines and the few concerns that were expressed are not a serious
concern. I was informed by most of those who provided feedback on the
registration submittal that they do not object to the registration submittal.
>>>>>>>>

Given that I can find neither the actual files nor a point-by-point
disposition of comments, it's very difficult to judge, and even more so
to accept, any of the above. If there was a longer disposition of comments,
please resent it (or point to it in the archives).

Also, as I can't see the changes you may have made, it is difficult to
comment on anything, but simply judging from the above text, there
are two potential problems:

- As reviewers, we have to judge consensus, but this is difficult
to do based just on a statement like "I talked to people, and
they seem to be fine as is."
- Charset registrations are not just a bureaucratic procedure.
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.


Looking through the archives, I also found the folowing from
you (January 2006, archived at
http://mail.apps.ietf.org/ietf/charsets/msg01532.html)

>>>>>>>>
I am ready to pursue this when IANA is ready and when Paul Hoffman is ready
to iron out any pending issues to register Windows-874 and the rest of my
contribution.
>>>>>>>>

Well, it turned out that Paul got replaced by Ned and myself
just very recently. I very much hope you are ready to iron out the
pending issues with us, and I look forward to work with you on this.

What Ned and me want to make sure is that you get the two
week max turnaround that RFC 2978 mentions. What we can't
do is write the registration forms for you, or approve something
just because somebody else has left it lying around for more than a year.

With kind regards, Martin.



#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp

[Frank Ellermann]

Martin Duerst wrote:

> I have found some mails in the June 2005 timeframe entitled

> IANA Character Set Registration Submittal - Disposition of comments
> also archived at:
> http://mail.apps.ietf.org/ietf/charsets/msg01522.html

> While this mail lists a series of filenames, neither the above
> location nor my archive contain any of these files, while
> earlier attachments from you got through in both places.

Probably some anti-spam magic at work. The last state I'm
aware of was two months and two messages later:

<http://mail.apps.ietf.org/ietf/charsets/msg01524.html>

That's supposed to be the same (raw = undecoded) as
<http://article.gmane.org/gmane.ietf.charsets:31:raw>

With a newsreader you can grab it from
<news://news.gmane.org/***@RED-MSG-42.redmond.corp.microsoft.com>
<nntp://news.gmane.org/gmane.ietf.charsets:31>

I didn't test the nntp URL.

Frank

[Erik van der Poel]

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 <***@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.

[Martin Duerst]

At 02:18 06/10/10, Erik van der Poel wrote:
>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.

There is absolutely nothing against other people trying to help.
Indeed, that's what the mailing list is for, in large part.

There is also, in my view, nothing against third-party registrations
(registrations of e.g. vendor character sets by somebody not affiliated
with the vendor), although it is of course better if somebody from
the vendor does it directly.

Regards, Martin.


>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 <***@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.


#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-# http://www.sw.it.aoyama.ac.jp mailto:***@it.aoyama.ac.jp

[Ned Freed]

> At 02:18 06/10/10, Erik van der Poel wrote:
> >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.

I think this is an excellent way to make more progress.

> There is absolutely nothing against other people trying to help.
> Indeed, that's what the mailing list is for, in large part.

Quite true.

> There is also, in my view, nothing against third-party registrations
> (registrations of e.g. vendor character sets by somebody not affiliated
> with the vendor), although it is of course better if somebody from
> the vendor does it directly.

Exactly so. We've long allowed both media type, charset, and no doubt other
sorts of registrations from third parties. In many cases it was the only way to
get a much-needed registration to happen.

Ned