Dataset for all ISO639 code sorted by country/territory?

[Steven R. Loomis]

El 11/21/16 2:58 PM, "CLDR-Users en nombre de Richard Wordingham" <cldr-users-bounces at unicode.org en nombre de richard.wordingham at ntlworld.com> escribió:

>On Mon, 21 Nov 2016 14:15:01 -0800
>"Steven R. Loomis" <srl at icu-project.org> wrote:
> 
>> 2016-11-21 1:50 GMT+01:00 Richard Wordingham
>> <richard.wordingham at ntlworld.com>
>
>>> The minimal data set can be difficult to collect, and may actually be
>>> impossible.  There may be technical issues - can one actually specify
>>> that today's date is "a.d. XI Kal. Dec. a.u.c. MMDCCLXIX" in
>>> Classical Latin?
>
>> Yes, you can use numbering system “roman” (uppercase)
>> http://www.unicode.org/repos/cldr/trunk/common/bcp47/number.xml
>
>It was the '11 days (inclusive) before the Calends of December' bit
>that had me worried.
>
>Is the following rule built into ICU?
>
>"In March, July, October, May
> The Nones are on the 7th day."

Not yet. 

>> El 11/21/16 11:08 AM, "CLDR-Users en nombre de Philippe Verdy"
>> <cldr-users-bounces at unicode.org en nombre de verdy_p at wanadoo.fr>
>> escribió:
>
>>> This
>>> remark will apply as well to Biblic Greek, Biblic/Masoretic Hebrew,
>>> Biblic Geez (in Ethiopia), Biblic Georgian, or Coranic Arabic that
>>> have significant and important differences with the vernacular modern
>>> "standard" languages for Greek, Hebrew, Geez, Georgian, and Arabic:
>>> these **living** religious variants should be IMHO encoded in CLDR.
>
>> If someone provides data for them and maintains them, yes. 
>
>The most important data will be the locale-based data for text
>manipulation, rather than much of the other stuff.

Sure.
I think the point is that ‘here is some data for X’ is probably more helpful to everyone than ‘CLDR ought to include X’

-s