On 22/10/2014 20:52, Naoto Sato wrote:
Hi Mandy,
As I wrote in a separate email, my preference is the following module
names:
jdk.localedata.jre
jdk.localedata.cldr
This way, they both come under localedata (btw, they don't provide
Locale, but the data for locale sensitive services such as
On 10/23/2014 4:58 PM, Alan Bateman wrote:
jdk.localedata.XXX looks right. I wonder if we can find something
better than jre for the suffix of the first one. I ask because
linking that into a runtime that isn't the what we know today as the
JRE might be confusing.
Actually Naoto and I
On 23/10/2014 09:17, Masayoshi Okutsu wrote:
On 10/23/2014 4:58 PM, Alan Bateman wrote:
jdk.localedata.XXX looks right. I wonder if we can find something
better than jre for the suffix of the first one. I ask because
linking that into a runtime that isn't the what we know today as the
JRE
Thanks for the naming suggestion, Alan. I will use classic then.
I also think we should introduce CLASSIC as a property name for the
java.locale.providers system property which should be an alias to JRE,
this requires a CCC though.
Naoto
On 10/23/14, 6:55 AM, Alan Bateman wrote:
On
+1
On 10/23/2014 4:52 AM, Naoto Sato wrote:
Hi Mandy,
As I wrote in a separate email, my preference is the following module
names:
jdk.localedata.jre
jdk.localedata.cldr
This way, they both come under localedata (btw, they don't provide
Locale, but the data for locale sensitive services
On 21/10/2014 01:25, Naoto Sato wrote:
I think we can rename the original jdk.localedata to
jdk.localedata.jre solely for the legacy JRE locale data, and create
the new jdk.localedata.cldr. Or re-purpose jdk.localedata to represent
the legacy JRE locale data, and newly create
On 17/10/2014 23:31, Naoto Sato wrote:
Hello,
Please review the proposed changes to the following bug:
https://bugs.openjdk.java.net/browse/JDK-8061382
The webrev is available at:
http://cr.openjdk.java.net/~naoto/8061382/webrev.00/
This is mainly build changes to separate CLDR locale data
On 10/20/14, 12:49 AM, Alan Bateman wrote:
Will it eventually be possible to create a runtime that has the CLDR
locale data but does not have the legacy JRE locale data? I'm assuming
the CLDR does not have any dependences on the classes in the JRE locale
data.
Yes, that should be possible in
