From mark at macchiato.com  Thu Sep  4 14:32:59 2014
From: mark at macchiato.com (=?UTF-8?B?TWFyayBEYXZpcyDimJXvuI8=?=)
Date: Thu, 4 Sep 2014 21:32:59 +0200
Subject: CLDR 26 final beta
Message-ID: <CAJ2xs_GRMBtdVG1YOtetNapKq2X4ZCRTKB=rEU0tBR9AMS1CEA@mail.gmail.com>

The CLDR version 26 data and specification is available for a final beta
review.

The modifications to the spec can be reviewed at:
http://www.unicode.org/reports/tr35/proposed.html#Modifications

The data is available at:
http://unicode.org/Public/cldr/26/

Beta data charts are available at
http://www.unicode.org/repos/cldr-aux/charts/26/index.html

To file feedback, go to http://unicode.org/cldr/trac/newticket. At this
point, we are particularly interested in "showstopper bugs"; others are
absolutely worth filing, but would not be handed in this release. The final
review is only open for a short period, until the morning of Wed, Sept 10.

The data and spec may have further (small) changes during the course of the
beta: a few outlying bugs are still being worked on, and the JSON data is
not yet in the beta.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140904/80bee1c7/attachment.html>

From srloomis at us.ibm.com  Thu Sep  4 23:22:01 2014
From: srloomis at us.ibm.com (Steven R Loomis)
Date: Thu, 4 Sep 2014 21:22:01 -0700
Subject: CLDR 26 final beta
In-Reply-To: <CAJ2xs_GRMBtdVG1YOtetNapKq2X4ZCRTKB=rEU0tBR9AMS1CEA@mail.gmail.com>
References: <CAJ2xs_GRMBtdVG1YOtetNapKq2X4ZCRTKB=rEU0tBR9AMS1CEA@mail.gmail.com>
Message-ID: <OF18800D09.AD762669-ON88257D4A.0017C711-88257D4A.0017FD5C@us.ibm.com>

Initial JSON data has been posted at the same location,
http://unicode.org/Public/cldr/26/

The JSON data is "alpha" quality at this point and may change.

-s



From:	Mark Davis ?? <mark at macchiato.com>
To:	"cldr-users at unicode.org" <cldr-users at unicode.org>, UTC
            <unicore at unicode.org>, Unicode Public <unicode at unicode.org>
Date:	09/04/2014 12:39 PM
Subject:	CLDR 26 final beta
Sent by:	"CLDR-Users" <cldr-users-bounces at unicode.org>



The CLDR version 26 data and specification is available for a final beta
review.

The modifications to the spec can be reviewed at:
http://www.unicode.org/reports/tr35/proposed.html#Modifications

The data is available at:
http://unicode.org/Public/cldr/26/

Beta data charts are available at
http://www.unicode.org/repos/cldr-aux/charts/26/index.html

To file feedback, go to?http://unicode.org/cldr/trac/newticket. At this
point, we are particularly interested in "showstopper bugs"; others are
absolutely worth filing, but would not be handed in this release. The final
review is only open for a short period, until the morning of Wed, Sept 10.

The data and spec may have further (small) changes during the course of the
beta: a few outlying bugs are still being worked on, and the JSON data is
not yet in the beta._______________________________________________
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/20140904/b1004b17/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140904/b1004b17/attachment.gif>

From srl at icu-project.org  Thu Sep  4 23:22:58 2014
From: srl at icu-project.org (Steven R. Loomis)
Date: Thu, 04 Sep 2014 21:22:58 -0700
Subject: Fwd: CLDR 26 final beta
In-Reply-To: <CAJ2xs_GRMBtdVG1YOtetNapKq2X4ZCRTKB=rEU0tBR9AMS1CEA@mail.gmail.com>
References: <CAJ2xs_GRMBtdVG1YOtetNapKq2X4ZCRTKB=rEU0tBR9AMS1CEA@mail.gmail.com>
Message-ID: <54093AA2.3030406@icu-project.org>

Alpha quality JSON data is available at http://unicode.org/Public/cldr/26/
This is an initial cut of the JSON data and may change.


-------- Original Message --------
Subject: 	CLDR 26 final beta
Date: 	Thu, 4 Sep 2014 21:32:59 +0200
From: 	Mark Davis ?? <mark at macchiato.com>
To: 	cldr-users at unicode.org <cldr-users at unicode.org>, UTC
<unicore at unicode.org>, Unicode Public <unicode at unicode.org>



The CLDR version 26 data and specification is available for a final beta
review.

The modifications to the spec can be reviewed at:
http://www.unicode.org/reports/tr35/proposed.html#Modifications

The data is available at:
http://unicode.org/Public/cldr/26/

Beta data charts are available at
http://www.unicode.org/repos/cldr-aux/charts/26/index.html

To file feedback, go to http://unicode.org/cldr/trac/newticket. At this
point, we are particularly interested in "showstopper bugs"; others are
absolutely worth filing, but would not be handed in this release. The
final review is only open for a short period, until the morning of Wed,
Sept 10.

The data and spec may have further (small) changes during the course of
the beta: a few outlying bugs are still being worked on, and the JSON
data is not yet in the beta.
//



From srl at icu-project.org  Mon Sep 29 17:27:59 2014
From: srl at icu-project.org (srl)
Date: Mon, 29 Sep 2014 15:27:59 -0700
Subject: CLDR 26: FYI: MediaWiki Language Extension Bundle 2014.09 released
Message-ID: <c660df62fb13c6b195e797029826d760@icu-project.org>

See release below:

https://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-September/000920.html

"I would like to announce the release of MediaWiki Language Extension
Bundle 2014.09??Update to CLDR 26"


From markus.icu at gmail.com  Tue Sep 30 15:01:44 2014
From: markus.icu at gmail.com (Markus Scherer)
Date: Tue, 30 Sep 2014 13:01:44 -0700
Subject: Unicode locale ID vs. POSIX variant
Message-ID: <CAN49p6ptyHNLrT2_p_LXJnCWtmjY3LrCbrAZbLCNHh=vkZSyog@mail.gmail.com>

Please help me understand the POSIX locale variant.

I assume that en_US_POSIX is still valid in the old syntax. For example,
see common/collation/en_US_POSIX.xml
<http://unicode.org/cldr/trac/browser/trunk/common/collation/en_US_POSIX.xml>

I assume that en-US-POSIX is a valid Unicode Language Identifier
<http://www.unicode.org/reports/tr35/tr35.html#Unicode_language_identifier>
(new
syntax) because CLDR supplemental metadata includes POSIX as a valid
variant.

CLDR also defines -u-va-posix.

It looks like in non-CLDR BCP 47, en-US-POSIX is not valid because POSIX is
not a registered language subtag.

Legacy Variants
<http://www.unicode.org/reports/tr35/tr35.html#Legacy_Variants> says to
convert the old-syntax variant POSIX to -u-va-posix.

Should a Unicode Language Identifier use variant POSIX but when converting
to non-CLDR BCP 47 convert that variant to -u-va-posix? Or should one
always convert from old syntax to new -u-va-posix (just in case the
recipient only understands BCP 47)?

When and where else should one convert between the POSIX variant and the
-u-va-posix extension?

Part of the problem is that old and new syntax are indistinguishable when
there is no '@' and no singleton subtag, and - and _ are both accepted as
separators, as usual.

Is en-US-POSIX-u-va-posix valid?
Is it the same as en-US-u-va-posix?

*References:*

supplementalMetadata.xml
<http://unicode.org/cldr/trac/browser/trunk/common/supplemental/supplementalMetadata.xml>
includes
"POSIX" in <variable id="$variant" type="choice">

I see http://www.unicode.org/reports/tr35/tr35.html#Key_Type_Definitions

Locale variant

*bcp47/variant.xml*
"va"Common variant type"posix"POSIX style locale variant
and http://unicode.org/repos/cldr/trunk/common/bcp47/variant.xml
<key name="va" description="Common locale variant type key">
<type name="posix" description="POSIX style locale variant"/>

https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
does not mention POSIX.

markus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20140930/4521db80/attachment.html>

From mark at macchiato.com  Tue Sep 30 23:50:17 2014
From: mark at macchiato.com (=?UTF-8?B?TWFyayBEYXZpcyDimJXvuI8=?=)
Date: Wed, 1 Oct 2014 06:50:17 +0200
Subject: Unicode locale ID vs. POSIX variant
In-Reply-To: <CAN49p6ptyHNLrT2_p_LXJnCWtmjY3LrCbrAZbLCNHh=vkZSyog@mail.gmail.com>
References: <CAN49p6ptyHNLrT2_p_LXJnCWtmjY3LrCbrAZbLCNHh=vkZSyog@mail.gmail.com>
Message-ID: <CAJ2xs_H0b4j1NPp7nM=kb3A5EquZN_tv9YMJuO2urEgauc=tdQ@mail.gmail.com>

en_US_POSIX is the "old style", which would be represented as
en-US-u-va-posix in BCP47.

We use pre-bcp47 IDs in the file and identifier tree for main (although
we've switched over for keyboards/). So the term POSIX does occur in
http://www.unicode.org/repos/cldr/tags/release-1-7/common/supplemental/supplementalMetadata.xml,
in
<variable id="$variant" type="choice">. These variables, however, are not
meant to indicate bcp47 compliance, but rather are used for verifying the
'old style' IDs that are used in the tree. They are also limited:
the <variable id="$language" type="choice"> doesn't include all the valid
language subtags.

I agree that this is not nearly as clean as we'd like. You should probably
file a ticket, and mention the text that led you astray, or where you see a
good point in the text where we can clarify this better.


Mark <https://google.com/+MarkDavis>

*? Il meglio ? l?inimico del bene ?*

On Tue, Sep 30, 2014 at 10:01 PM, Markus Scherer <markus.icu at gmail.com>
wrote:

> Please help me understand the POSIX locale variant.
>
> I assume that en_US_POSIX is still valid in the old syntax. For example,
> see common/collation/en_US_POSIX.xml
> <http://unicode.org/cldr/trac/browser/trunk/common/collation/en_US_POSIX.xml>
>
> I assume that en-US-POSIX is a valid Unicode Language Identifier
> <http://www.unicode.org/reports/tr35/tr35.html#Unicode_language_identifier> (new
> syntax) because CLDR supplemental metadata includes POSIX as a valid
> variant.
>
> CLDR also defines -u-va-posix.
>
> It looks like in non-CLDR BCP 47, en-US-POSIX is not valid because POSIX
> is not a registered language subtag.
>
> Legacy Variants
> <http://www.unicode.org/reports/tr35/tr35.html#Legacy_Variants> says to
> convert the old-syntax variant POSIX to -u-va-posix.
>
> Should a Unicode Language Identifier use variant POSIX but when converting
> to non-CLDR BCP 47 convert that variant to -u-va-posix? Or should one
> always convert from old syntax to new -u-va-posix (just in case the
> recipient only understands BCP 47)?
>
> When and where else should one convert between the POSIX variant and the
> -u-va-posix extension?
>
> Part of the problem is that old and new syntax are indistinguishable when
> there is no '@' and no singleton subtag, and - and _ are both accepted as
> separators, as usual.
>
> Is en-US-POSIX-u-va-posix valid?
> Is it the same as en-US-u-va-posix?
>
> *References:*
>
> supplementalMetadata.xml
> <http://unicode.org/cldr/trac/browser/trunk/common/supplemental/supplementalMetadata.xml> includes
> "POSIX" in <variable id="$variant" type="choice">
>
> I see http://www.unicode.org/reports/tr35/tr35.html#Key_Type_Definitions
>
> Locale variant
>
> *bcp47/variant.xml*
> "va"Common variant type"posix"POSIX style locale variant
> and http://unicode.org/repos/cldr/trunk/common/bcp47/variant.xml
> <key name="va" description="Common locale variant type key">
> <type name="posix" description="POSIX style locale variant"/>
>
>
> https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
> does not mention POSIX.
>
> markus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20141001/c44f64ad/attachment.html>