Author: kwin
Date: Tue Jun 28 11:58:51 2016
New Revision: 1750490
URL: http://svn.apache.org/viewvc?rev=1750490&view=rev
Log:
clarify which language string formats are supported
Modified:
sling/site/trunk/content/documentation/bundles/internationalization-support-i18n.mdtext
Modified:
sling/site/trunk/content/documentation/bundles/internationalization-support-i18n.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/internationalization-support-i18n.mdtext?rev=1750490&r1=1750489&r2=1750490&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/bundles/internationalization-support-i18n.mdtext
(original)
+++
sling/site/trunk/content/documentation/bundles/internationalization-support-i18n.mdtext
Tue Jun 28 11:58:51 2016
@@ -37,7 +37,7 @@ The `org.apache.sling.i18n` Bundle imple
### JCR Repository based `ResourceBundleProvider`
-The sling.i18n Bundle provides the implementation of the
`ResourceBundleProvider` interface, which may also be used outside of Sling
requests for service tasks. This implementation gets the messages from a JCR
Repository stored below nodes of the mixin node type `mix:language`. These
language nodes have a `jcr:language` property naming the language of the
resources. In the context of the JCR based `ResourceBundleProvider` this is of
course expected to be the string value of respective `Locale`. The format may
either be the format as described in
[Locale.toString](http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#toString%28%29)
or as described in [RFC4646](https://www.ietf.org/rfc/rfc4646.txt) (both
formats are also accepted in lower-case).
+The sling.i18n Bundle provides the implementation of the
`ResourceBundleProvider` interface, which may also be used outside of Sling
requests for service tasks. This implementation gets the messages from a JCR
Repository stored below nodes of the mixin node type `mix:language`. These
language nodes have a `jcr:language` property naming the language of the
resources. In the context of the JCR based `ResourceBundleProvider` this is of
course expected to be the string value of respective `Locale`. The format may
either be the format as described in
[Locale.toString](http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#toString%28%29)
or as described in [BCP 47](https://tools.ietf.org/html/bcp47), while for the
latter you may only provide ISO 3166-1 country codes (for the region) and ISO
639-1 alpha 2 language codes (for the language). Both formats are also accepted
in lower-case.
The exact location of these nodes is not relevant as the
`ResourceBundleProvider` finds them by applying a JCR search.
