RE: windows-1252

[Mike Ksar <mikeksar@microsoft.com>]

My proposed disposition of comments was posted on the alias.  It was not
done behind the scenes.  Unfortunately no one responded and my
contribution and disposition of comments have been sitting idly for
almost one year.

Again, I followed the procedures strictly as outlined for the
registration.  Any additional preferences are not a must but nice to
have.

Mike Ksar
-----Original Message-----
From: Erik van der Poel [mailto:erik@vanderpoel.org] 
Sent: Sunday, January 15, 2006 8:54 AM
To: Mike Ksar; phoffman@imc.org
Cc: Frank Ellermann; ietf-charsets@mail.apps.ietf.org
Subject: Re: windows-1252

My feeling is that it is inappropriate to say that you met with and 
phoned people that had comments. I believe those discussions are 
supposed to happen on this mailing list, so that we can try to achieve 
consensus in an open fashion.

Maybe the charset reviewer should say something at this point. Paul, is 
that you?

Erik

Mike Ksar wrote:
> I am open to do the registrations one at a time.  I am only trying to
> follow the registration procedures as documented and I think I have
done
> so.  I have met with and talked over the phone with several of the
> people that submitted comments.  No one has any objection to the
> registration but some expressed preference to include additional
> information which is not required by the registration rules.
> 
> Mike Ksar
> 
> -----Original Message-----
> From: Erik van der Poel [mailto:erik@vanderpoel.org] 
> Sent: Sunday, January 15, 2006 12:15 AM
> To: Frank Ellermann
> Cc: ietf-charsets@mail.apps.ietf.org
> Subject: Re: windows-1252
> 
> Frank Ellermann wrote:
> 
>>Erik van der Poel wrote:
>>
>>>RFC 2978 does not require a Unicode mapping. It says that
>>>there "SHOULD" be a 10646 mapping, but it does not use the
>>>word "MUST".
>>
>>You need a good excuse to ignore a SHOULD, a typical example
>>are old implementations (= here old charset registrations).
> 
> 
> I agree that it is really a good idea to provide the 10646 mapping.
> 
> 
>>It also says "MUST be stable", that's why we got tons of new
>>registered charsets doing something for the "Euro", like 858
>>instead of 850.
> 
> 
> It is true that the RFC says "stable", but it does not say what
"stable"
> 
> means in the context of charsets. Does it mean that assigned
codepoints 
> must not change? Of course. Does it mean that unassigned codepoints
must
> 
> not change? That is debatable. (And remember that UTF-8 is
specifically 
> permitted to have unassigned codepoints that might change later.)
> 
> 
>>In the case of 1252 all it takes is to explain what the five
>>interesting octets are supposed to be:  Maybe "cp-1252" and
>>windows-1252 are two different charsets, the former with one
>>to one mappings, the latter with five unassigned code points.
> 
> 
> I can't find "cp-1252" in the IANA charset registry:
> 
> http://www.iana.org/assignments/character-sets
> 
> I have been wondering, however, about this "re-registration" of 
> windows-1252. Why is it being registered again? Is it because the 
> contact person/email address is being changed? If so, then that should

> be stated explicitly. I'm not very happy about these 2 URLs supplied 
> with it either:
> 
> http://www.microsoft.com/globaldev/getwr/steps/wrg_unicode.mspx
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/un
> icode_19mb.asp
> 
> Those documents are not 10646 equivalency tables, nor are they even 
> published specs, for 1252.
> 
> Mike, I have a suggestion. How about dealing with windows-1252 
> separately? If we can agree on a change for the windows-1252 
> registration (e.g. contact person/email), then you can apply the same 
> fix to the other re-registrations. It might even be a good idea to
have 
> some non-person email address at Microsoft be the contact. E.g. 
> iana-charsets@microsoft.com. Then it doesn't matter whether Chris
Wendt 
> or Mike Ksar leave Microsoft.
> 
> Then, or in parallel, discuss windows-874 separately. If we can agree
on
> 
> a pattern for that charset, you can apply the same pattern to the
other 
> new windows-NNN charsets.
> 
> Erik
> 
>