W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > July 2007

Re: [WCAG2 TECHS] i18n comment: RFC 3066 links

From: Ben Caldwell <caldwell@trace.wisc.edu>
Date: Tue, 10 Jul 2007 11:29:10 -0500
Message-ID: <4693B3D6.4040901@trace.wisc.edu>
To: Richard Ishida <ishida@w3.org>
CC: public-comments-wcag20@w3.org, public-i18n-core@w3.org

Richard Ishida wrote:
>> -----Original Message-----
>> From: public-i18n-core-request@w3.org 
>> [mailto:public-i18n-core-request@w3.org] On Behalf Of ishida@w3.org
>> Sent: 27 June 2006 19:49
>> To: public-comments-wcag20@w3.org; public-i18n-core@w3.org
>> Subject: [WCAG2 TECHS] i18n comment: RFC 3066 links
>>
>>
>> Comment from the i18n review of:
>> http://www.w3.org/TR/2006/WD-WCAG20-TECHS-20060427/
>>
>> Comment 6
>> At http://www.w3.org/International/reviews/0606-wcag2-techniques/
>> Editorial/substantive: S
>> Owner: RI
>>
>> Location in reviewed document:
>> H57, H58, Resources
>>
>> Comment: 
>> There is a pointer to RFC 3066 'Tags for the Identification 
>> of Languages'. This specification has now been superceded by 
>> RFC3066bis, although, unfortunately, there is no number for 
>> the new RFC just yet. We suggest that you add a new link as 
>> soon as possible.
>>
>>
>> In the meantime, you may wish to point to 
>> http://www.w3.org/International/core/langtags/rfc3066bis.html
> 
> =================================
>> From: Loretta Guarino Reid [mailto:lorettaguarino@google.com]
>> Sent: 18 May 2007 00:43
>> To: Richard Ishida
>> Cc: public-comments-WCAG20@w3.org
>> Subject: Your comments on WCAG 2.0 Last Call Draft of April
>> 2006 (2 of 2)
> 
>> Comment 17:
> 
>> ----------------------------
>> Response from Working Group:
>> ----------------------------
>>
>> We have updated the reference to refer to the updated RFC 4646.
> 
> 
> Now that things have settled down, the best strategy is to replace all links
> to RFC 4646 with links to BCP 47. RFC 4646 will be replaced fairly soon with
> another RFC, but BCP 47 will continue to refer to the latest relevant RFC.
> The link is:
> 
> http://www.rfc-editor.org/rfc/bcp/bcp47.txt
> 
> You can still use the same title as the link text.
> 
> Hope that helps.

Thank you for the updated references. We have included them in an 
updated draft.

All the best,

-Ben


-- 
Ben Caldwell | <caldwell@trace.wisc.edu>
Trace Research and Development Center <http://trace.wisc.edu>
Received on Tuesday, 10 July 2007 16:29:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 17 October 2017 07:46:01 UTC