[loc-en-dev] Revised Locale API proposal

Yoshito Umaoka y.umaoka at gmail.com
Tue Sep 8 10:25:53 PDT 2009


Yoshito Umaoka wrote:
> Hi all,
>
> I reviewed the proposed API docs and updated followings -
>
> 1. Locale class description: Reorganized and provided more 
> comprehensive explanation for logical locale fields.
> 2. Variant: Removed syntactical restrictions on variant, provided some 
> note about BCP47 compatibility.
> 3. Mics changes: Consistent terminology, removed "New API", etc...
>
> I'm attaching a zip file in this message.  Please take a look if this 
> version is good enough for submitting a proposal to OpenJDK.
>
> I'll add some explanation about the updated behavior for candidate 
> list in ResourceBundle.Control and LocaleServiceProvider, but these 
> are behavior changes, not adding/changing APIs.
>
> -Yoshito
In the conf call today, we'll go through the updated API proposal 
attached in the previous message.  Especially, I would like to discuss 
about the variant field design change (which also affect the API 
contract in Builder).  Also, with this change (no syntactical 
restrictions on variant), we probably need to revisit "toString()" 
topic.  We thought toLanguageTag() could be used as Locale ID for valid 
locales, but with no restrictions on variant, this is no longer true.  
I'm wondering if we need to revisit "toString()" - more specifically, 
write out all new Locale internal field values after variant field.  For 
example, en_US_POSIX_script=Latn_ext=a-xxx-x-java-1-7.

Thanks,
Yoshito


More information about the locale-enhancement-dev mailing list