New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What to say about BCP47 Support? #1225
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented svn commit -m "Fixes https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1225, What to say about BCP47 Support?" |
@glassfishrobot Commented git commit -m Fixes https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1225, What to say about BCP47 Support? Commit Log |
@glassfishrobot Commented |
@glassfishrobot Commented |
|
BCP47 defines new rules for the parsing of Locale objects. These rules are implemented in the java.util.Locale class in JDK7. There are several places in the JSF spec that place requirements on how a Locale is encoded as a String.
XSD for supported-locale
XSD for default-locale
Spec section "2.5.2.1 Determining the Active Locale" in the portion of that section that deals with the locale attribute on the <f:view> tag.
In all of these places statements are made regarding the use of "-" or "_" as a separator. This issue asks if we should go further and require the use of JDK7 Locale.forLanguageTag() to obtain the Locale instance before trying the existing methods of obtaining a Locale.
Affected Versions
[2.2]
The text was updated successfully, but these errors were encountered: