Suppress-Script for Korean?
petercon at microsoft.com
Wed Jul 25 02:25:09 CEST 2007
Are you suggesting that if a document is entirely in (say) hiragana I shouldn't tag it ja-Hira because Hira is considered a subset of Japn and Japn is to be suppressed?
From: ietf-languages-bounces at alvestrand.no [mailto:ietf-languages-bounces at alvestrand.no] On Behalf Of Mark Davis
Sent: Tuesday, July 24, 2007 12:46 PM
To: Addison Phillips
Cc: Randy Presuhn; ietf-languages at iana.org
Subject: Re: Suppress-Script for Korean?
As I noted earlier, we have precedent for this: Japn for Japanese. The same basic principles apply.
* 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.
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).
On 7/24/07, Addison Phillips <addison at yahoo-inc.com<mailto:addison at yahoo-inc.com>> wrote:
'Kore' is a new subtag. 'Hang' has existed for awhile. And I suspect but
cannot prove that many Koreans will think of their language as being
written in the Hangul script, whether it is purely Hangul or not.
If we suppress the wrong script, users might think that they have to
identify "other" scripts, like 'Hang', by default. I think we should be
very judicious about what we suppress, especially when there can be
confusion. Besides, I'm not sure what adding 'Kore' achieves.
Randy Presuhn wrote:
> Hi -
>> From: "Addison Phillips" < addison at yahoo-inc.com<mailto:addison at yahoo-inc.com>>
>> To: "Doug Ewell" <dewell at roadrunner.com<mailto:dewell at roadrunner.com>>
>> Cc: <ietf-languages at iana.org <mailto:ietf-languages at iana.org> >
>> Sent: Tuesday, July 24, 2007 9:18 AM
>> Subject: Re: Suppress-Script for Korean?
>>> Are there any objections to adding 'Kore' as a Suppress-Script for the
>> > Korean language?
>> Yes. RFC 4646 only permits a single script to be suppressed. 'Kore' and
>> 'Hang' both seem appropriate for suppression. Since it doesn't seem to
>> be a big problem and plenty of languages don't suppress their scripts, I
>> don't think we should add it at this time.
> I think "Kore" is the appropriate choice for suppression. In the abstract,
> this might seem odd because the "Hang" is a proper subset of "Kore."
> However, if we think about the practical contexts of when something would
> be delibrately written only using "Hang," (rather than merely happening to
> have only "Hang" characters) I think the conclusion is that "Hang"
> is indeed the "marked" case.
> Since there already is a substantial body of tagged Korean text with no
> script subtag, and Korean texts of any substantial length are overwhelmingly
> "Kore", this seems to be exactly what Suppress-Script was intended to cover.
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no<mailto:Ietf-languages at alvestrand.no>
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG
Internationalization is an architecture.
It is not a feature.
Ietf-languages mailing list
Ietf-languages at alvestrand.no<mailto:Ietf-languages at alvestrand.no>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ietf-languages