Subject: Re: parsing and translating xml:lang attribute From: David Carlisle <davidc@xxxxxxxxx> Date: Tue, 24 Oct 2000 23:14:17 GMT |
> ...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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: parsing and translating xml:lan, Mike Brown | Thread | RE: parsing and translating xml:lan, Kay Michael |
CDATA Help (in SAXON), Dylan Parker | Date | concat of two strings to create an , Mala Ramakrishnan |
Month |