<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
<DIV class="ReadMsgBody BorderTop">
<DIV class="ExternalClass PlainTextMessageBody" id=MsgContainer><PRE><TABLE cellSpacing=0 cellPadding=0><TBODY><TR><TD><SPAN id=PresenceContainer><B>on behalf of Stephane Bortzmeyer</B> (<A href="mailto:bortzmeyer@nic.fr">bortzmeyer@nic.fr</A>):</SPAN></TD></TR><TR><TD class=SecondaryTextColor></TD><TD></TD></TR></TBODY></TABLE><BR>> Frank Ellermann <nobody@xyzzy.claranet.de> wrote:<BR>>> Just propose RFC 4646 language tags if you think it is important,<BR>>> there is a public comment forum.<BR>> Done at<BR>> <A href="http://forum.icann.org/lists/translation-programme/msg00006.html">http://forum.icann.org/lists/translation-programme/msg00006.html</A><BR>Hi, Sorry for my last email in which I suggested ICANN might do w/out mentioning RFC 4646; Stephane and Peter are right;<BR>BCP 47/RFC 4646 can't be gotten around-- <BR>although I really do not see that there will be much need for scripts to be identified--except for<BR>Korean--as the default script should generally serve for ICANN's purposes, with its choice of languages. <BR>(Unless ICANN at some point down the road decides to publish documents used in or interpretations from meetings in the language of the host country--</PRE><PRE>then, in some host countries. there might be a need to identify a script. </PRE><PRE>However even choosing to tag a document as simply as possible is part of BCP 47.) </PRE><PRE>--C. E. Whitehead</PRE><PRE><A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A> <BR></PRE>
<DIR><FONT face="Times New Roman">From: cewcathar@hotmail.com<BR><BR>>> From: nobody@xyzzy.claranet.de<BR>>> Date: Sat, 1 Mar 2008 10:49:54 +0100<BR>>> Subject: Re: [gnso.secretariat@gnso.icann.org: ICANN Draft Translation Programmeopen for public comment]<BR>>><BR>>> Stephane Bortzmeyer wrote:<BR>>> <BR>>>> Since this draft document, open to comments, talks a lot about<BR>>>> human languages, I feel it is relevant here.<BR>>> <BR><BR>>>> Do note that the plan for language identifiers, in the current<BR>>>> version, is ISO 639 (with just ISO 3166 country codes), not BCP 47 :-(<BR>>> <BR>>> Apparently they use locale indentifiers. After a somewhat obscure <BR>>> procedure they arrived at 11 languages for most of their purposes,<BR>>> likely they don't need RFC 4646 tags for this job. <BR>> Possibly no.<BR>Sorry, my error; they do need to have a tag, regardless, even if the tag has only one or two subtags in it.<BR></FONT><FONT face="Times New Roman"><BR>--C. E. Whitehead<BR></FONT><A href="mailto:cewcathar@hotmail.com"><U><FONT face="Times New Roman" color=#0000ff>cewcathar@hotmail.com</U></FONT></A><FONT face="Times New Roman"> <BR></FONT><FONT face=Arial></DIR></FONT></DIV></DIV></body>
</html>