[
https://issues.jboss.org/browse/GTNPORTAL-2337?page=com.atlassian.jira.pl...
]
Peter Palaga updated GTNPORTAL-2337:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/gatein/gatein-portal/pull/71
The patch adds the ability to the I18N class and its tests to run under Java 7. However,
the Java 7-specific locale IDs (with e.g. #u-... and #{script} suffixes) are still
unsupported. Only two IDs comming from the Java 7 world are supported now:
"ja_JP_JP_#u-ca-japanese" and "th_TH_TH_#u-nu-thai"; see
http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html
I18N locale identifier parsing code does not support all valid cases
in Java 7
------------------------------------------------------------------------------
Key: GTNPORTAL-2337
URL:
https://issues.jboss.org/browse/GTNPORTAL-2337
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Internationalization and Localization
Affects Versions: 3.2.0-Beta01
Reporter: Chris Laprun
Assignee: Peter Palaga
Labels: java7
According to the Locale Java 7 javadoc:
Java has used ja_JP_JP to represent Japanese as used in Japan together with the Japanese
Imperial calendar. This is now representable using a Unicode locale extension, by
specifying the Unicode locale key ca (for "calendar") and type japanese. When
the Locale constructor is called with the arguments "ja", "JP",
"JP", the extension "u-ca-japanese" is automatically added.
This results in a ja_JP_JP_#u-ca-japanese Locale which is currently parsed as invalid.
Note that there is a similar issue for Thai.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira