suppress-script values for fil, mi, pes, prs, qu members
petercon at microsoft.com
Tue Oct 19 22:15:40 CEST 2010
> If that's the problem you're trying to solve... and if you have locale data related to the particular language. BCP 47 tags support thousands of languages for which nobody has locale data.
I forgot to add: And I'm trying to solve different problems.
From: ietf-languages-bounces at alvestrand.no [mailto:ietf-languages-bounces at alvestrand.no] On Behalf Of Peter Constable
Sent: Tuesday, October 19, 2010 1:07 PM
To: Philip Newton
Subject: RE: suppress-script values for fil, mi, pes, prs, qu members
From: Philip Newton [mailto:philip.newton at gmail.com]
> Isn't that the sort of thing CLDR addresses?
Inherently, no: CLDR provides data designed to live inside particular _locale_ bundles. The scenarios I described involved working with _language_ tags that have not been mapped into a locale and for which no locale data may be available.
> Sure, it might be useful to know what keyboard layouts and fonts are relevant, but it would also be useful to know what calendar is used...
If that's the problem you're trying to solve... and if you have locale data related to the particular language. BCP 47 tags support thousands of languages for which nobody has locale data.
> I don't see the language subtag registry providing that information any time soon.
And I'm not asking for that.
> (And I don't think s-s is *intended* to provide information on the
> default script for a language, though it does happen to do so for
> languages that do contain this field.)
Ummm... If it's not giving a default script, then what is it giving?
> Personally, I don't think that this one piece of data should be added
> to the registry when there are so many pieces of data that are potentially useful.
Again, you're thinking in terms of locales. I'm explicitly _not_ thinking in terms of locales, but rather in terms of languages.
Ietf-languages mailing list
Ietf-languages at alvestrand.no
More information about the Ietf-languages