This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: parsing and translating xml:lang attribute
- To: xsl-list at mulberrytech dot com
- Subject: Re: parsing and translating xml:lang attribute
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Tue, 24 Oct 2000 23:14:17 GMT
- References: <200010242148.PAA46994@skew.org>
- Reply-To: xsl-list at mulberrytech dot com
> ...so if you are intending to put 3-letter codes in an xml:lang value in
> the target document, then you're wrong to do so :)
were wrong if you were doing it before this month, but now xml2e says:
The values of the attribute are language identifiers as defined by <a
href="#RFC1766">[IETF RFC 1766]</a>, <cite>Tags for the Identification
of Languages</cite>, or its successor on the IETF Standards Track.</p>
<div class="note"><p class="prefix"><b>Note:</b></p> <p><a
href="#RFC1766">[IETF RFC 1766]</a> tags are constructed from two-letter
language codes as defined by <a href="#ISO639">[ISO 639]</a>, from
two-letter country codes as defined by <a href="#ISO3166">[ISO
3166]</a>, or from language identifiers registered with the Internet
Assigned Numbers Authority <a
href="#IANA-LANGCODES">[IANA-LANGCODES]</a>. It is expected that the
successor to <a href="#RFC1766">[IETF RFC 1766]</a> will introduce
three-letter language codes for languages not presently covered by <a
href="#ISO639">[ISO 639]</a>.</p>
David
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list