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

Steven R. Loomis srl at icu-project.org
Mon Jul 14 23:52:52 CDT 2014


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140714/1c5bc9d1/attachment.html>


More information about the CLDR-Users mailing list