The offline registration page embeds the URL to post the data to Sun and open the JDK registration page in the browser.  The URL parameter for all register.html, register_ja.html, and register_zh_CN.html should have the corresponding locale set in the locale parameter.  Currently it is incorrectly set to the default locale as the link for the online registration page.
Posted Date : 2008-03-18 03:53:30.0

In addition, the Registration Relay Service (RRS) doesn't support all 3 forms of locales:
 Locale(String language)
 Locale(String language, String country)
 Locale(String language, String country, String variant)

It's one-to-one mapping of a given locale parameter passed in the URL. 

The offline registration page should have the locale parameter matched to the locale for that page. i.e. locale=en for register.html, locale=ja for register_ja.html, and locale=zh_CN for register_zh_CN.html.  Ideally the RRS should recognize all 3 forms of locales and show the best candidate.  Due to the one-to-one mapping design, we have to leave with this restriction and with the assumption that only ja and zh_CN are only supported. The URL for the online registration will also have the locale parameter set to either a JDK supported locale or the default one.


 If the registration is translated for a new locale in the future, JDK will have to make change
Posted Date : 2008-03-18 06:12:58.0

N/A

We need to fix in JDK 6u6.  The Sun Connection registration web application will support L10N in the March release.  Once it hosts the translated page, the users may see a Japanese translated page even for Chinese developers.
Posted Date : 2008-03-18 03:53:30.0