From patch.nova at gmail.com  Wed Mar  9 10:19:22 2016
From: patch.nova at gmail.com (Nova Patch)
Date: Wed, 9 Mar 2016 11:19:22 -0500
Subject: CLDR v29 Beta available for review
In-Reply-To: <CAJ2xs_GMx+pxcWwP8O66-FpXO5hRVJFbewshMJ7a3ZbOOruxEw@mail.gmail.com>
References: <CAJ2xs_GMx+pxcWwP8O66-FpXO5hRVJFbewshMJ7a3ZbOOruxEw@mail.gmail.com>
Message-ID: <CANV8b5Y2pTZMrza3+0ZNbobC1nZMtdQSaZmQQarm3UOouEr7iQ@mail.gmail.com>

2016-02-22 2:59 GMT-05:00 Mark Davis ?? <mark at macchiato.com>:
>
> The CLDR v29 beta is available for review. Information on the release and
a summary of the main changes are available at
http://cldr.unicode.org/index/downloads/cldr-29.

I tested out the CLDR v29-beta1 JSON on a number of systems, including Perl
CPAN modules CLDR::Number and Geo::Region. All changes appear to be
expected and there weren't any failing tests.

If you're interested, here's the diff for CLDR::Number, which uses
cldr-core and cldr-numbers-full:
https://github.com/patch/cldr-number-pm5/compare/cldr29

I'm very happy with the introduction of es-BR, as unexpected formatting
using Spanish in Brazil has been brought to my attention several times.

Thanks to everyone involved in CLDR v29! I look forward to the release.

Best,
Nova
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160309/98a375e4/attachment.html>

From mark at macchiato.com  Wed Mar  9 11:24:21 2016
From: mark at macchiato.com (=?UTF-8?B?TWFyayBEYXZpcyDimJXvuI8=?=)
Date: Wed, 9 Mar 2016 18:24:21 +0100
Subject: CLDR v29 Beta available for review
In-Reply-To: <CANV8b5Y2pTZMrza3+0ZNbobC1nZMtdQSaZmQQarm3UOouEr7iQ@mail.gmail.com>
References: <CAJ2xs_GMx+pxcWwP8O66-FpXO5hRVJFbewshMJ7a3ZbOOruxEw@mail.gmail.com>
 <CANV8b5Y2pTZMrza3+0ZNbobC1nZMtdQSaZmQQarm3UOouEr7iQ@mail.gmail.com>
Message-ID: <CAJ2xs_Ge4b=9yoULnqanOT6=8H8hGjE7shmAqQtwA-a+XN2hZA@mail.gmail.com>

Thanks! We're getting down to the wire; looks like we should make the
target date of Idus Martiae.

Mark

On Wed, Mar 9, 2016 at 5:19 PM, Nova Patch <patch.nova at gmail.com> wrote:

> 2016-02-22 2:59 GMT-05:00 Mark Davis ?? <mark at macchiato.com>:
> >
> > The CLDR v29 beta is available for review. Information on the release
> and a summary of the main changes are available at
> http://cldr.unicode.org/index/downloads/cldr-29.
>
> I tested out the CLDR v29-beta1 JSON on a number of systems, including
> Perl CPAN modules CLDR::Number and Geo::Region. All changes appear to be
> expected and there weren't any failing tests.
>
> If you're interested, here's the diff for CLDR::Number, which uses
> cldr-core and cldr-numbers-full:
> https://github.com/patch/cldr-number-pm5/compare/cldr29
>
> I'm very happy with the introduction of es-BR, as unexpected formatting
> using Spanish in Brazil has been brought to my attention several times.
>
> Thanks to everyone involved in CLDR v29! I look forward to the release.
>
> Best,
> Nova
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160309/656550ba/attachment.html>

From gh_online at me.com  Thu Mar 10 15:21:17 2016
From: gh_online at me.com (Gregory Huczynski)
Date: Thu, 10 Mar 2016 21:21:17 +0000
Subject: Correct way for reporting CLDR data errors/tweaks?
Message-ID: <F124FFBE-17C3-40CA-B37C-AF45F24D8EFA@me.com>

Hi there,

What?s the correct way for reporting CLDR data errors/tweaks?
Should I submit tickets using http://unicode.org/cldr/trac/newticket <http://unicode.org/cldr/trac/newticket>?

I?ve been programmatically consuming CLDR in JSON form, and have come across some data inconsistencies that may need correcting.

Many thanks

Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160310/8d11d98a/attachment.html>

From srl at icu-project.org  Thu Mar 10 15:53:31 2016
From: srl at icu-project.org (Steven R. Loomis)
Date: Thu, 10 Mar 2016 13:53:31 -0800
Subject: Correct way for reporting CLDR data errors/tweaks?
In-Reply-To: <F124FFBE-17C3-40CA-B37C-AF45F24D8EFA@me.com>
References: <F124FFBE-17C3-40CA-B37C-AF45F24D8EFA@me.com>
Message-ID: <994274C7-AFE1-4AAF-BF35-7D913F5DAA20@icu-project.org>

That?s a good place to start. But you could outline the issues here in email first if you want.
-s


> El mar 10, 2016, a las 1:21 PM, Gregory Huczynski <gh_online at me.com> escribi?:
> 
> Hi there,
> 
> What?s the correct way for reporting CLDR data errors/tweaks?
> Should I submit tickets using http://unicode.org/cldr/trac/newticket <http://unicode.org/cldr/trac/newticket>?
> 
> I?ve been programmatically consuming CLDR in JSON form, and have come across some data inconsistencies that may need correcting.
> 
> Many thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160310/cb79c2e9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160310/cb79c2e9/attachment.asc>

From srl at icu-project.org  Thu Mar 31 12:07:39 2016
From: srl at icu-project.org (Steven Loomis)
Date: Thu, 31 Mar 2016 10:07:39 -0700
Subject: Duration Lists?
Message-ID: <BD439101-4527-4F64-A9A7-77914918A0B0@icu-project.org>

>From path header:

../../tools/java/org/unicode/cldr/util/data/PathHeader.txt://ldml/listPatterns/listPattern[@type="unit-short"]/listPatternPart[@type="%A"] ; Misc ; Displaying Lists ; Short Duration Lists ; &listOrder($1)


So the type ?unit-short? is named ?Short Duration List?.

What is this list and what is it for? It?s not documented.

I?m at TC39. The question is how CLDR lists map to the following four use cases:


? separating numbers:   ?4, 5, 6? or ?4;5;6"
? separating units: ?5months 3days? or ?5 lb 8 oz?
? separating ?regular? things - ?Monday, Tuesday, and Wednesday?
? separating ?regular" in short form - ?Monday, Tuesday, Wednesday?

Thanks.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160331/657895e0/attachment.html>

From srl at icu-project.org  Thu Mar 31 12:41:49 2016
From: srl at icu-project.org (Steven Loomis)
Date: Thu, 31 Mar 2016 10:41:49 -0700
Subject: Duration Lists?
In-Reply-To: <BD439101-4527-4F64-A9A7-77914918A0B0@icu-project.org>
References: <BD439101-4527-4F64-A9A7-77914918A0B0@icu-project.org>
Message-ID: <473BC477-228D-4A95-B358-1C0C79E8488F@icu-project.org>

 http://cldr.unicode.org/translation/lists does not mention Regular vs Duration/Unit
 PathHeader also has //ldml/listPatterns/listPattern/listPatternPart[@type="%A"] ; Misc ; Displaying Lists ; Regular Lists ; &listOrder($1)  - but ?Regular Lists? doesn?t appear as such in the spec.  

Should ?Regular Lists? be renamed to ?Standard Lists? or ?Other Lists? ? 

Pending discussion of the other bullet items below.

El 3/31/16 10:07 AM, "CLDR-Users en nombre de Steven Loomis" <cldr-users-bounces at unicode.org en nombre de srl at icu-project.org> escribi?:

>From path header:

../../tools/java/org/unicode/cldr/util/data/PathHeader.txt://ldml/listPatterns/listPattern[@type="unit-short"]/listPatternPart[@type="%A"] ; Misc ; Displaying Lists ; Short Duration Lists ; &listOrder($1)


So the type ?unit-short? is named ?Short Duration List?.

What is this list and what is it for? It?s not documented.

I?m at TC39. The question is how CLDR lists map to the following four use cases:


? separating numbers:   ?4, 5, 6? or ?4;5;6"
? separating units: ?5months 3days? or ?5 lb 8 oz?
? separating ?regular? things - ?Monday, Tuesday, and Wednesday?
? separating ?regular" in short form - ?Monday, Tuesday, Wednesday?

Thanks.


_______________________________________________ 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/20160331/942f7ca2/attachment.html>