As I noted earlier, we have precedent for this: Japn for Japanese. The same basic principles apply. <br><ul><li>Suppress-Script should be supplied when it would be very uncommon in modern usage for the language to be written in text not encompassed by the script.
</li></ul>In the case of Japn or Kore, it would be very uncommon for Japanese to be written in scripts outside of Japn (Han, Katakana, or Hiragana); in the case of Korean, it would be very uncommon for Korean to be written in scripts outside of Kore (Han or Hang).
<br><br>Mark<br><br><div><span class="gmail_quote">On 7/24/07, <b class="gmail_sendername">Addison Phillips</b> <<a href="mailto:addison@yahoo-inc.com">addison@yahoo-inc.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
'Kore' is a new subtag. 'Hang' has existed for awhile. And I suspect but<br>cannot prove that many Koreans will think of their language as being<br>written in the Hangul script, whether it is purely Hangul or not.
<br><br>If we suppress the wrong script, users might think that they have to<br>identify "other" scripts, like 'Hang', by default. I think we should be<br>very judicious about what we suppress, especially when there can be
<br>confusion. Besides, I'm not sure what adding 'Kore' achieves.<br><br>Addison<br><br>Randy Presuhn wrote:<br>> Hi -<br>><br>>> From: "Addison Phillips" <<a href="mailto:addison@yahoo-inc.com">
addison@yahoo-inc.com</a>><br>>> To: "Doug Ewell" <<a href="mailto:dewell@roadrunner.com">dewell@roadrunner.com</a>><br>>> Cc: <<a href="mailto:ietf-languages@iana.org">ietf-languages@iana.org
</a>><br>>> Sent: Tuesday, July 24, 2007 9:18 AM<br>>> Subject: Re: Suppress-Script for Korean?<br>>><br>>>> Are there any objections to adding 'Kore' as a Suppress-Script for the<br>
>> > Korean language?<br>>><br>>> Yes. RFC 4646 only permits a single script to be suppressed. 'Kore' and<br>>> 'Hang' both seem appropriate for suppression. Since it doesn't seem to
<br>>> be a big problem and plenty of languages don't suppress their scripts, I<br>>> don't think we should add it at this time.<br>> ...<br>><br>> I think "Kore" is the appropriate choice for suppression. In the abstract,
<br>> this might seem odd because the "Hang" is a proper subset of "Kore."<br>> However, if we think about the practical contexts of when something would<br>> be delibrately written only using "Hang," (rather than merely happening to
<br>> have only "Hang" characters) I think the conclusion is that "Hang"<br>> is indeed the "marked" case.<br>><br>> Since there already is a substantial body of tagged Korean text with no
<br>> script subtag, and Korean texts of any substantial length are overwhelmingly<br>> "Kore", this seems to be exactly what Suppress-Script was intended to cover.<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><br><br>--<br>Addison Phillips<br>Globalization Architect -- Yahoo! Inc.<br>Chair -- W3C Internationalization Core WG<br><br>Internationalization is an architecture.<br>It is not a feature.<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><br></blockquote></div><br><br clear="all"><br>-- <br>Mark