<div><font face="georgia,serif">More on those at <a href="http://cldr.unicode.org/index/bcp47-extension">http://cldr.unicode.org/index/bcp47-extension</a></font></div><div><font face="georgia,serif"><br clear="all"></font><font face="georgia, serif">Mark<br>
<br><i>— Il meglio è l’inimico del bene —</i></font><br>
<br><br><div class="gmail_quote">On Fri, Feb 4, 2011 at 08:35, Ian Abbott <span dir="ltr"><<a href="mailto:abbotti@mev.co.uk">abbotti@mev.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 04/02/11 16:00, <a href="mailto:yoshito_umaoka@us.ibm.com">yoshito_umaoka@us.ibm.com</a> wrote:<br>
> Unicode CLDR defines locale identifiers based on BCP47 language tag<br>
> (<a href="http://www.ietf.org/rfc/bcp/bcp47.txt" target="_blank">http://www.ietf.org/rfc/bcp/bcp47.txt</a>)<br>
> BCP47 provides a mechanism for extending language tags for use in<br>
> various applications.<br>
><br>
> We recently published RFC6067 (<a href="http://datatracker.ietf.org/doc/rfc6067/" target="_blank">http://datatracker.ietf.org/doc/rfc6067/</a>)<br>
> to allocate BCP47 extension letter "u" for the use of Unicode Locale<br>
> Identifiers. Unicode Locale Identifier has its own subtag for specifying<br>
> time zone IDs. Unfortunately, zone IDs in the tz database cannot be used<br>
> in language tag because each subtag in extension must be 2 to 8<br>
> alpha/numeric characters. For this reason, we defined "short ID" for<br>
> zones based on UN/LOCODE [<a href="http://www.unece.org/cefact/locode/" target="_blank">http://www.unece.org/cefact/locode/</a>]. Most of<br>
> exemplar cities by the tz database are covered by LOCODE, with small<br>
> exceptions.<br>
><br>
> For example, zone "America/New_York" is represented by "usnyc". The<br>
> mapping data is provided in the file -<br>
> <a href="http://www.unicode.org/repos/cldr/trunk/common/bcp47/timezone.xml" target="_blank">http://www.unicode.org/repos/cldr/trunk/common/bcp47/timezone.xml</a><br>
><br>
> With the extension, you can exchange locale data including time zone<br>
> information with a language tag - for example, "en-US-u-tz-usnyc"<br>
><br>
> I'm wondering if zone.tab can include LOCODE - for example, LOCODE<br>
> consist from ISO3166 2-letter country code + 3-letter location code.<br>
><br>
> #locode coordinates TZ comments<br>
> AD ALV +4230+00131 Europe/Andorra<br>
> AE DXB +2518+05518 Asia/Dubai<br>
> AF KBL +3431+06912 Asia/Kabul<br>
> AG ANU +1703-06148 America/Antigua<br>
> ...<br>
><br>
> -Yoshito Umaoka (ICU / CLDR project)<br>
<br>
</div></div>Including LOCODE in zone.tab may or may not be a good idea, but I'm<br>
trying hard to think why you'd want to encode a time zone in a language tag.<br>
<font color="#888888"><br>
--<br>
-=( Ian Abbott @ MEV Ltd. E-mail: <<a href="mailto:abbotti@mev.co.uk">abbotti@mev.co.uk</a>> )=-<br>
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-<br>
<br>
</font></blockquote></div><br></div>