[loc-en-dev] Norwegian special lookup

[Naoto Sato]

Your proposal sounds good to me.

Another reasoning for that is, if we don't insert "no_NO_NY" for "nn", 
applications which want to support Nynorsk translation on both JDK7 and 
JDK6 would have to provide duplicate resource bundles for "nn" and 
"no_NO_NY".

Naoto

On 7/13/10 8:45 PM, Yoshito Umaoka wrote:
> Hi Naoto,
>
> I was thinking about it actually. The reason I did not try to save that
> case was that language code "nn" is never generated from Java's
> supported locale "no_NO_NY". But if we really want to support the
> situation, the rule is going to be a little bit more complicated.
>
> Request: "nn"
> Candidates: "nn", "no_NO_NY", "no"
>
> But I guess we do not want to insert "no_NO_NY" when region is not NO.
> For example,
>
> Request: "nn_US"
> Candidates: "nn_US", "nn", "no"
>
> More complex case - if no region, but there is a variant.
>
> Request: "nn__JAVA"
> Candidates: "nn__JAVA", "nn", "no_NO_NY", "no"
>
> Probably, the rule is, when language is "nn", but no region is
> available, insert "no_NO_NY", then "no" after "nn"? What do you think?
>
> -Yoshito
>
>
> Naoto Sato wrote:
>> I have one comment on the last bullet.
>>
>> Currently applications have to specify the country code "NO" even for
>> the cases just providing Nynorsk translation regardless of the
>> country. So I think it'd be better to fall back to "no_NO_NY" for "nn"
>> being requested.
>>
>> Naoto
>>
>> (7/13/10 9:07 AM), Yoshito Umaoka wrote:
>>> Hi All,
>>>
>>> http://sites.google.com/site/openjdklocale/design-notes/resource-bundle-lookup-order
>>>
>>>
>>>
>>> I put the comprehensive Norwegian lookup order list in the section
>>> "Special Case 3: Norwegian Locales".
>>>
>>> The algorithm used for this is also described after the table.
>>>
>>> * If request contains language "no", but not matching pattern
>>> "no_NO_NY[_*]", create the default candidate list, then insert
>>> locale replacing "no" with "nb" at each level after "no" version.
>>> * If request contains language "nb", create the default candidate
>>> list, then insert locale replacing "nb" with "no" at each level
>>> after "nb" version.
>>> * If request matches pattern "no_NO_NY[_*]", insert "nn_NO[_*]"
>>> before every level. Once it reaches "no_NO_NY", then append "nn",
>>> "no_NO" and "no" in this order.
>>> * If request matches pattern "nn_NO[_*], insert "no_NO_NY[_*]" after
>>> every level. Once it reaches "no_NO_NY", then append "nn", "no_NO"
>>> and "no" in this order.
>>> * If request contains language "nn", but region is not "NO", append
>>> "no" at the end of default candidate list.
>>>
>>> Please review the list and algorithm by the end of today. If you have
>>> any questions, please post your response in this ML.
>>>
>>> -Yoshito
>>
>>
>