From emmo at us.ibm.com Tue Sep 1 00:09:28 2015 From: emmo at us.ibm.com (John Emmons) Date: Tue, 1 Sep 2015 00:09:28 -0500 Subject: Preliminary JSON available for release 28 Message-ID: A preliminary version of the JSON for the upcoming CLDR release 28 is now available on github for testing. Please see https://github.com/unicode-cldr/cldr-json for details. Any errors or omissions should be reported via CLDR trac by filing a new ticket at http://unicode.org/cldr/trac/newticket Regards, John C. Emmons Globalization Architect & Unicode CLDR TC Chairman IBM Software Group Internet: emmo at us.ibm.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.wordingham at ntlworld.com Wed Sep 2 13:19:03 2015 From: richard.wordingham at ntlworld.com (Richard Wordingham) Date: Wed, 2 Sep 2015 19:19:03 +0100 Subject: Status of Sanskrit Message-ID: <20150902191903.15e1b5fc@JRWUBU2> I am confused by the status of Sanskrit in CLDR. I can't find it in the CLDR 27.0.1 release, yet I find a live ticket on its collation going back 5 years. Could someone please explain what is going on, or better, how I should have been able to find this information myself. Richard. From rick at unicode.org Thu Sep 3 11:32:21 2015 From: rick at unicode.org (Rick McGowan) Date: Thu, 03 Sep 2015 09:32:21 -0700 Subject: The proposed update LDML specification for CLDR Release 28 now available for review Message-ID: <55E87615.6010307@unicode.org> A proposed update to the LDML specification (UTS #35) will be available for review as of Monday, September 7 at 06:00 GMT. The open review period closes on Monday, September 14 at 06:00 GMT. (This is a short review period, because CLDR 28 is scheduled for release in the week of September 16.) The proposed update will be at http://unicode.org/reports/tr35/proposed.html To report bugs in the specification, please use http://unicode.org/cldr/trac/newticket From Christopher.Chapman at monotype.com Mon Sep 14 12:49:55 2015 From: Christopher.Chapman at monotype.com (Chapman, Christopher) Date: Mon, 14 Sep 2015 17:49:55 +0000 Subject: Missing some language names? Message-ID: <2f08474732424672ad9ade2c136aa530@wob-maildb-03.agfamonotype.org> Hi Folks, I'm just starting to use the CLDR and I apologize if this is a na?ve question, but should I be able to find mappings of all the language tags used in the CLDR to their full names in the sections of the files in core/common/main (e.g. core/common/main/en.xml)? I ask, because I found only some of them there, not all of them. For example, in core/common/supplemental/supplementalData.xml, I see entries like this: ...and in core/common/main/en.xml, I see some (but not all) of those language tags mapped to their English names, e.g.: Persian Pashto Uzbek Turkmen Baluchi Uyghur Kazakh Missing from that file (and missing from all the files in core/common/main) are entries for "haz" and "prd". Should they be there? If not, where should I find them? In case it helps, here's the version info. from the core/common/main/en.xml that I'm using: ...and here's the version of core/common/supplemental/supplementalData.xml that I'm using: Thanks! Cheers, Christopher -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at macchiato.com Mon Sep 14 13:56:09 2015 From: mark at macchiato.com (=?UTF-8?B?TWFyayBEYXZpcyDimJXvuI8=?=) Date: Mon, 14 Sep 2015 20:56:09 +0200 Subject: Missing some language names? In-Reply-To: <2f08474732424672ad9ade2c136aa530@wob-maildb-03.agfamonotype.org> References: <2f08474732424672ad9ade2c136aa530@wob-maildb-03.agfamonotype.org> Message-ID: There is no requirement that all language codes that are used in any CLDR file have translations. English names are always available as a backup in the language subtag registry, should one desire. Mark *? Il meglio ? l?inimico del bene ?* On Mon, Sep 14, 2015 at 7:49 PM, Chapman, Christopher < Christopher.Chapman at monotype.com> wrote: > Hi Folks, > > > > I?m just starting to use the CLDR and I apologize if this is a na?ve > question, but should I be able to find mappings of all the language tags > used in the CLDR to their full names in the sections of the > files in core/common/main (e.g. core/common/main/en.xml)? I ask, because I > found only some of them there, not all of them. > > > > For example, in core/common/supplemental/supplementalData.xml, I see > entries like this: > > literacyPercent="28.1" population="31822800"> > > type="fa" populationPercent="50" officialStatus="official"/> > > > type="ps" populationPercent="43" officialStatus="official" > references="R1055"/> > > type="haz" populationPercent="5.9"/> > > type="uz_Arab" populationPercent="4.7" > officialStatus="official_regional"/> > > type="tk_Latn" populationPercent="1.7" > officialStatus="official_regional"/> > > type="prd" populationPercent="1.2"/> > > type="bal" populationPercent="0.67" > officialStatus="official_regional"/> > > type="ug_Arab" populationPercent="0.0094" > references="R1165"/> > > type="kk_Arab" populationPercent="0.0063" > references="R1119"/> > > > > > > ?and in core/common/main/en.xml, I see some (but not all) of those > language tags mapped to their English names, e.g.: > > Persian > > Pashto > > Uzbek > > Turkmen > > Baluchi > > Uyghur > > Kazakh > > > > Missing from that file (and missing from all the files in > core/common/main) are entries for ?haz? and ?prd?. Should they be there? > If not, where should I find them? > > > > In case it helps, here?s the version info. from the > core/common/main/en.xml that I?m using: > > > > > > > > ?and here?s the version of core/common/supplemental/supplementalData.xml > that I?m using: > > > > > > > > Thanks! > > > > > > Cheers, > > Christopher > > > > _______________________________________________ > CLDR-Users mailing list > CLDR-Users at unicode.org > http://unicode.org/mailman/listinfo/cldr-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From isaac.jurado at roiback.com Mon Sep 28 19:19:18 2015 From: isaac.jurado at roiback.com (Isaac Jurado) Date: Tue, 29 Sep 2015 02:19:18 +0200 Subject: Where is the Kurdish locale? Message-ID: Hello, After reviewing the following URL: http://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code I'm a bit confused regarding the mentions to the Kurdish locale. Specially since I was unable to find any XML file in the CLDR distribution named "ku.xml" nor anything similar. Am I looking in the wrong place? Best regards. -- Isaac Jurado I+D Senior Web Developer ROIBACK T. (+34) 971 406 149 E. isaac.jurado at roiback.com http://www.roiback.com From mark at macchiato.com Tue Sep 29 02:28:44 2015 From: mark at macchiato.com (=?UTF-8?B?TWFyayBEYXZpcyDimJXvuI8=?=) Date: Tue, 29 Sep 2015 09:28:44 +0200 Subject: Where is the Kurdish locale? In-Reply-To: References: Message-ID: On Tue, Sep 29, 2015 at 2:19 AM, Isaac Jurado wrote: > I'm a bit confused regarding the mentions to the Kurdish locale. > Specially since I was unable to find any XML file in the CLDR > distribution named "ku.xml" nor anything similar. > ?CLDR has Central Kurdish (ckb), but not Northern Kurdish (ku)?. See http://www.unicode.org/cldr/charts/latest/summary/root.html There is a ku.xml in the /seed/ directory but the data is not sufficient, nor is it sufficiently validated, to warrant inclusion into the /common/ directory. Mark *? Il meglio ? l?inimico del bene ?* -------------- next part -------------- An HTML attachment was scrubbed... URL: From isaac.jurado at roiback.com Tue Sep 29 02:39:36 2015 From: isaac.jurado at roiback.com (Isaac Jurado) Date: Tue, 29 Sep 2015 09:39:36 +0200 Subject: Where is the Kurdish locale? In-Reply-To: References: Message-ID: On Tue, Sep 29, 2015 at 9:28 AM, Mark Davis ?? wrote: > > On Tue, Sep 29, 2015 at 2:19 AM, Isaac Jurado > wrote: >> >> I'm a bit confused regarding the mentions to the Kurdish locale. >> Specially since I was unable to find any XML file in the CLDR >> distribution named "ku.xml" nor anything similar. > > > CLDR has Central Kurdish (ckb), but not Northern Kurdish (ku). > > See http://www.unicode.org/cldr/charts/latest/summary/root.html > > There is a ku.xml in the /seed/ directory but the data is not > sufficient, nor is it sufficiently validated, to warrant inclusion > into the /common/ directory. Oh, now I see it. Thank you very much. Then I believe it is a matter of time and public interest to "promote" the "ku" locale into the /common/ directory: http://cldr.unicode.org/index/process Thanks again. Best regards. -- Isaac Jurado I+D Senior Web Developer ROIBACK T. (+34) 971 406 149 E. isaac.jurado at roiback.com http://www.roiback.com From mark at macchiato.com Tue Sep 29 05:03:41 2015 From: mark at macchiato.com (=?UTF-8?B?TWFyayBEYXZpcyDimJXvuI8=?=) Date: Tue, 29 Sep 2015 12:03:41 +0200 Subject: Where is the Kurdish locale? In-Reply-To: References: Message-ID: The key to doing that is to get people from Kurdish organizations involved in contributing to ku data. There are a number of other languages where volunteer groups organize to contribute the data for their languages. Mark *? Il meglio ? l?inimico del bene ?* On Tue, Sep 29, 2015 at 9:39 AM, Isaac Jurado wrote: > On Tue, Sep 29, 2015 at 9:28 AM, Mark Davis ?? wrote: > > > > On Tue, Sep 29, 2015 at 2:19 AM, Isaac Jurado > > wrote: > >> > >> I'm a bit confused regarding the mentions to the Kurdish locale. > >> Specially since I was unable to find any XML file in the CLDR > >> distribution named "ku.xml" nor anything similar. > > > > > > CLDR has Central Kurdish (ckb), but not Northern Kurdish (ku). > > > > See http://www.unicode.org/cldr/charts/latest/summary/root.html > > > > There is a ku.xml in the /seed/ directory but the data is not > > sufficient, nor is it sufficiently validated, to warrant inclusion > > into the /common/ directory. > > Oh, now I see it. Thank you very much. Then I believe it is a matter > of time and public interest to "promote" the "ku" locale into the > /common/ directory: > > http://cldr.unicode.org/index/process > > Thanks again. Best regards. > > -- > Isaac Jurado > I+D Senior Web Developer > ROIBACK > T. (+34) 971 406 149 > E. isaac.jurado at roiback.com > http://www.roiback.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: