DR 09-0060 - WML, Fonts: Names should be registered at IANA

[John Haug]

Hi all -
As a reminder, here are the 6 items requested in DR 09-0060 and the resolution to each.  I've attached the proposed wording based on our last conference call.  Please let me know if I've remembered something wrong between that call, many e-mails and lots of other verbal discussions we have had.

Note: I based the text changes off the latest version of the 2012 consolidated reprint draft.  I added comments to point out changes that are part of COR2 (29500:2011 COR 1).  I'm not sure which doc this change will finally apply to.  I also didn't find specific guidance for list webpages and websites in normative references, so I copied one of the existing formats.  Rex may need to fiddle with the formatting.

Requested:
 1. 0x80: shift_jis should be replaced by Windows-31J.
 2. 0x81: Microsoft Windows Codepage 949 should be registered in IANA, and use the name in the description.
 3. 0x82: Microsoft Windows Codepage 1361 should be registered in IANA and use the name in the description.
 4. 0x86: GB2312 should be replaced by GBK.
 5. 0x88: Microsoft Windows Codepage 950 should be registered in IANA, and use the name in the description, because there are various Big5 diversions.
 6. 0xDE: windows-874 is not registered in IANA. It should be registered.

Resolutions:
1. Microsoft has registered Windows-31J with IANA as a variant of shift_jis.  -->  Leave the reference to shift_jis.  Add a reference to the IANA documentation.
2. CP 949 is documented with Unicode.  -->  Add reference to the Unicode documentation.
3. CP 1361 is documented with Unicode.  -->  Add reference to the Unicode documentation.
4. -->  GB2312 replaced with GBK.
5. CP 950 is documented with Unicode.  -->  Add reference to the Unicode documentation.
6. Microsoft registered windows-874 with IANA.  -->  Add a reference to the IANA documentation.

So, this all comes down to one change (#4) and adding references to IANA and Unicode documentation.  Since this should apply to all vendors/implementers, I created references to the general pages where links take the reader to specific platform information.

John

-----Original Message-----
From: suzuki toshiya [mailto:mpsuzuki at hiroshima-u.ac.jp] 
Sent: Wednesday, May 30, 2012 6:15 AM
To: Jim Thatcher
Cc: John Haug; SC34
Subject: Re: DR 09-0060 - WML, Fonts: Names should be registered at IANA

Dear Jim and John,

Thank you for revisiting and the clarification about "what is the defect and what is the solution". Today I discussed with other Japanese experts, and I understand that the names of the charsets in commented part of the spec are NOT used in the document (what used in the document is hexadecimal values), and the names are only used by the description in the spec, so the essential solution is the clarification what the quoted charsets are.

OK, now I agree with the position that the references to the mapping tables in Unicode website or MSDN would be sufficient to close this defect.
Because these charsets are defined by Microsoft, so I prefer the references to MSDN, but the reference to the mapping tables in Unicode website is acceptable solution.

Regards,
mpsuzuki

Jim Thatcher wrote:
> Suzuki-san,
> 
> You are correct that the original request was to have the codepages registered with IANA. However, in our discussions during the Prague meetings WG4 agreed that it would be reasonable to reference documentation of the codepages at Unicode.org or MSDN to allow reference to the source that most accurately describes the codepages expected by existing OOXML documents that reference those codepages.
> 
> Best regards,
> Jim
> 
> -----Original Message-----
> From: John Haug [mailto:johnhaug at exchange.microsoft.com]
> Sent: Tuesday, May 29, 2012 3:46 PM
> To: suzuki toshiya
> Cc: SC34
> Subject: RE: DR 09-0060 - WML, Fonts: Names should be registered at 
> IANA
> 
> Hm, my understanding from prior discussions was simply to have references to documentation of any differences, in order to support better interoperability.  That seems a good goal to me, and would spare us many months of trying to get things registered with IANA.
> 
> -----Original Message-----
> From: suzuki toshiya [mailto:mpsuzuki at hiroshima-u.ac.jp]
> Sent: Tuesday, May 29, 2012 12:40 PM
> To: John Haug
> Cc: SC34
> Subject: Re: DR 09-0060 - WML, Fonts: Names should be registered at 
> IANA
> 
> Dear John,
> 
> I think the document at Unicode.org is describing "what Windows Codepage xxx is", but what DR 09-0060 requests is the utilization of the standard names officially registered in IANA (and, if no appropriate names are registered, they should be registered). If you had experienced any difficulty to register Windows Codepage as a charset name to IANA registry, please let WG4 members know. It will help the discussion what we should do (in next) to close the DR.
> 
> Regards,
> mpsuzuki
> 
> John Haug wrote:
>> Hi all -
>> My fonts contact here asked me about this, which reminded me there was no response to it.
>>
>> Is the documentation for #2, 3, 5 at the link below sufficient?
>>
>> Thanks,
>> John
>>
>> From: John Haug [mailto:johnhaug at exchange.microsoft.com]
>> Sent: Thursday, March 22, 2012 12:31 PM
>> To: SC34
>> Subject: DR 09-0060 - WML, Fonts: Names should be registered at IANA
>>
>> I realized all the mail I've been sending and receiving on this DR 
>> have been with individuals.  Let me take the opportunity to recap 
>> this one for the whole list, and to capture discussion from the call 
>> this morning.  Please take a look at the code page 949, 950, 1361 
>> documents here and let's discuss whether these cover how we wanted to 
>> handle this DR.
>> http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WindowsBestFit
>>
>>
>> DR requested changes:
>>   1. 0x80: shift_jis should be replaced by Windows-31J.
>>   2. 0x81: Microsoft Windows Codepage 949 should be registered in IANA, and use the name in the description.
>>   3. 0x82: Microsoft Windows Codepage 1361 should be registered in IANA and use the name in the description.
>>   4. 0x86: GB2312 should be replaced by GBK.
>>   5. 0x88: Microsoft Windows Codepage 950 should be registered in IANA, and use the name in the description, because there are various Big5 diversions.
>>   6. 0xDE: windows-874 is not registered in IANA. It should be registered.
>>
>> Status:
>>   - As covered in Prague (2012), #1, #4, #6 are done.
>>   - I only recently found that #2 and #5 are documented on unicode.org.  I had #3 documented there last week.
>>
>> WG 4 review request:
>> Please take a look at the code page 949, 950, 1361 documents here and let's discuss whether these cover how we wanted to handle this DR.
>> Recall from the Prague meeting notes:
>> "In order to provide for the greatest degree of interoperability and fidelity of documents across implementations WG4 has made an exception to reference the Windows Codepage 949, 1361, and 950 character sets, which are defined by Microsoft and broadly implemented across the industry.
>> John will investigate whether sufficient public document exists to use as references for bullets 2, 3, and 5."
>>
>>
> 
> 
> 
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: DR 09-0060 proposed changes 2.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 59903 bytes
Desc: DR 09-0060 proposed changes 2.docx
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20120607/a110fa9e/attachment-0001.bin>