<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cordia New";
        panose-1:2 11 3 4 2 2 2 2 2 4;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.gmailquote
        {mso-style-name:gmail_quote;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That seems reasonable enough. The question is whether it would
be clear to users of the registry what they should do in such cases based on
the contents of the registry and the contents of BCP47.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Peter<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
ietf-languages-bounces@alvestrand.no
[mailto:ietf-languages-bounces@alvestrand.no] <b>On Behalf Of </b>Mark Davis<br>
<b>Sent:</b> Tuesday, July 24, 2007 5:47 PM<br>
<b>To:</b> Randy Presuhn<br>
<b>Cc:</b> ietf-languages@iana.org<br>
<b>Subject:</b> Re: Suppress-Script for Korean?<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal style='margin-bottom:12.0pt'>I agree.<o:p></o:p></p>

<div>

<p class=MsoNormal><span class=gmailquote>On 7/24/07, <b>Randy Presuhn</b> &lt;<a
href="mailto:randy_presuhn@mindspring.com">randy_presuhn@mindspring.com</a>&gt;
wrote:</span><o:p></o:p></p>

<p class=MsoNormal>Hi -<br>
<br>
&gt; From: &quot;Peter Constable&quot; &lt;<a
href="mailto:petercon@microsoft.com">petercon@microsoft.com</a>&gt;<br>
&gt; To: &quot;Mark Davis&quot; &lt;<a href="mailto:mark.davis@icu-project.org">mark.davis@icu-project.org
</a>&gt;; &quot;Addison Phillips&quot; &lt;<a
href="mailto:addison@yahoo-inc.com">addison@yahoo-inc.com</a>&gt;<br>
&gt; Cc: &quot;Randy Presuhn&quot; &lt;<a
href="mailto:randy_presuhn@mindspring.com">randy_presuhn@mindspring.com </a>&gt;;
&lt;<a href="mailto:ietf-languages@iana.org">ietf-languages@iana.org</a>&gt;<br>
&gt; Sent: Tuesday, July 24, 2007 5:25 PM<br>
&gt; Subject: RE: Suppress-Script for Korean?<br>
&gt;<br>
&gt; Are you suggesting that if a document is entirely in (say) hiragana I
shouldn't <br>
&gt;&nbsp;&nbsp;tag it ja-Hira because Hira is considered a subset of Japn and
Japn is to be suppressed?<br>
<br>
For a document longer than a few words to be purely &quot;Hira&quot; would be
*very* artifical,<br>
and consequently I'd expect it to be marked as such, just as an extended document
<br>
solely in Kanji or Katakana would also be quite artifical.&nbsp;&nbsp; On the
other hand, let's say it's<br>
just a quote of a word or two which would normally be written in pure
&quot;Hira&quot;.&nbsp;&nbsp;In that case,<br>
it's not a &quot;marked form&quot;, so I'd say that simply tagging it
&quot;ja&quot; would normally be the <br>
appropriate thing to do.<br>
<br>
I think the real consideration is this: does adding the script subtag provide<br>
information that could not be reasonably inferred from
&quot;ja&quot;.&nbsp;&nbsp;&quot;-Japn&quot; would<br>
not provide useful information.&nbsp;&nbsp;&quot;-Hira&quot; marks the text as
being quite <br>
out of the ordinary.<br>
<br>
Randy<br>
<br>
_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><o:p></o:p></p>

</div>

<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Mark <o:p></o:p></p>

</div>

</div>

</body>

</html>