adding all of iso639_3 to either en.xml or root.xml

[Philippe Verdy]

May be the CLDR can prepare itself the content of IANA registry in a
supplemental file in LDML format (to be used as an optional supplementary
fallback file for the English locale before the root). OR it could
conveince the IANA database maintainers to publish it in LDML format
instead of its legacy format described in the existing RFCs.


2014-07-15 16:35 GMT+02:00 Mark Davis ☕️ <mark at macchiato.com>:

> We can talk about this at the meeting, if you want to put it on the menu.
> However, I had strong doubts about it, because it means adding about 24,000
> lines to en.xml, when it is not that hard to process the registry document.
>
>
> Mark <https://google.com/+MarkDavis>
>
>  *— Il meglio è l’inimico del bene —*
>
>
> On Tue, Jul 15, 2014 at 4:33 PM, Steven R. Loomis <srl at icu-project.org>
> wrote:
>
>> Maybe we could have a cldrmodify pass that fills in en could work, then
>> someone could fill out any missing translations before doing other
>> processing. But, cldr wouldn't come that way out of the box.  Then this is
>> about ldml(interchange) and not cldr (common data).
>>
>> Enviado desde nuestro iPhone.
>>
>> El jul 14, 2014, a las 11:54 PM, Mark Davis ☕️ <mark at macchiato.com>
>> escribió:
>>
>> I'm not sure it would be worth it. People can always pick up a copy of
>> the language subtag registry and use it to back-fill.
>>
>> We do keep a copy of the registry in our tooling data directory, and
>> that's what we do in our tooling, such as myCldrFile.getName(language).
>>
>>
>> Mark <https://google.com/+MarkDavis>
>>
>>  *— Il meglio è l’inimico del bene —*
>>
>>
>> On Tue, Jul 15, 2014 at 6:52 AM, Steven R. Loomis <srl at icu-project.org>
>> wrote:
>>
>>> If anything should be in en and not root.
>>>
>>> Wonder if it could go into seed/en or something.
>>>
>>> It's not in en right now because of translation burden. But I'd think we
>>> could set controls via coverage.
>>>
>>> En.xml is hand curated now, that would be another distinction.
>>>
>>> Steven
>>>
>>> Enviado desde nuestro iPhone.
>>>
>>> El jul 14, 2014, a las 9:47 PM, Martin Hosken <martin_hosken at sil.org>
>>> escribió:
>>>
>>> Dear All,
>>>
>>> I notice that en.xml only contains localeDisplayNames/languages/language
>>> entries for a subset of iso639-3. Is there a case for filling out the list
>>> based on iso639-3 reference names so that people don't have to fallback to
>>> data not in the CLDR? Or, given iso639 has these reference names, is there
>>> a case for putting them into the root. I realise it's a bit odd to put what
>>> amounts to English names into root.xml. OTOH these are the official
>>> reference names and so act as fallback for all languages, so perhaps it
>>> would be appropriate. I'm happy either way. But I think CLDR would benefit
>>> from having the complete reference name mapping of iso639-3 in it.
>>>
>>> Yours,
>>> Martin
>>> _______________________________________________
>>> CLDR-Users mailing list
>>> CLDR-Users at unicode.org
>>> http://unicode.org/mailman/listinfo/cldr-users
>>>
>>>
>>> _______________________________________________
>>> CLDR-Users mailing list
>>> CLDR-Users at unicode.org
>>> http://unicode.org/mailman/listinfo/cldr-users
>>>
>>>
>> _______________________________________________
>> CLDR-Users mailing list
>> CLDR-Users at unicode.org
>> http://unicode.org/mailman/listinfo/cldr-users
>>
>>
>
> _______________________________________________
> CLDR-Users mailing list
> CLDR-Users at unicode.org
> http://unicode.org/mailman/listinfo/cldr-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140715/5971e9fc/attachment.html>