I hereby nominate Naoto Sato to Internationalization Group Lead [1].
Naoto had been the lead of the Internationalization group until he left
the team in April this year.
Votes are due by 2016-12-14T00:00:00Z.
Only the current Members of the Internationalization Group [2] are
eligible to vote
I am resigning as the lead of this group because I'm leaving the company.
Thanks,
Masayoshi
Hi,
Please review
http://cr.openjdk.java.net/~ljiang/7037368/
for bug
https://bugs.openjdk.java.net/browse/JDK-7037368
I checked the currency names listed in the bug description, and got the fix
according to CLDR data.
Thanks,
Leo
Hi Stephen,
Please find my comments inlined.
On 30/11/16 5:07 PM, Stephen Colebourne wrote:
The ISO-3166-3 code is of a complex form and not widely used as far as
I know. As far as I can tell, it is not legal to create a Locale
instance using the ISO-3166-3 code as the country.
Yes, Agreed..AP
The ISO-3166-3 code is of a complex form and not widely used as far as
I know. As far as I can tell, it is not legal to create a Locale
instance using the ISO-3166-3 code as the country.
At the very least, the PART3 constant should describe the meaning and
structure of the codes.
What might be us
Looks good to me.
Masayoshi
On 11/22/2016 6:30 PM, Rachna Goel wrote:
Hi,
Please review fix for JDK-8075577.
Bug : https://bugs.openjdk.java.net/browse/JDK-8075577
webrev : http://cr.openjdk.java.net/~rgoel/JDK-8075577/webrev.01/
Fix is to introduce new private spi
"sun.text.spi.JavaTimeD
Hi Stephen,
Thanks a lot for the review.
On 30/11/16 3:15 AM, Stephen Colebourne wrote:
I'm concerned that this is not the friendliest of new APIs. There is
little description of the meaning of the ISO-3166 parts - what is
being added is directly exposing the underlying data rather than
providi
