This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/struts-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f2b4550 Updates production by Jenkins
f2b4550 is described below
commit f2b455055618e596491446977839d45fc60457e9
Author: jenkins
AuthorDate: Sun Jun 10 14:00:56 2018 +
Updates production by Jenkins
---
content/core-developers/localization.html | 36 +++
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/content/core-developers/localization.html
b/content/core-developers/localization.html
index 7ef0160..2764e37 100644
--- a/content/core-developers/localization.html
+++ b/content/core-developers/localization.html
@@ -172,7 +172,7 @@
global resource properties
-This is how it is implemented in a default implementation of the LocalizedTextProvider interface. You can
provide your
+This is how it is implemented in a default implementation of the LocalizedTextProvider interface. You can
provide your
own implementation using TextProvider
and TextProviderFactory interfaces.
To clarify #5, while traversing the package hierarchy, Struts 2 will look
for a file package.properties:
@@ -188,7 +188,7 @@ own implementation using TextProvider and
- If FooAction.properties does not
exist, com/acme/action/package.properties will be
searched for, if not found
+ If FooAction.properties does not
exist, com/acme/action/package.properties will be
searched for, if not found
com/acme/package.properties, if not
found com/package.properties, etc.
@@ -202,12 +202,12 @@ own implementation using TextProvider and
-it will use a default class defined with default-class-ref in struts-default.xml which is
+it will use a default class defined with default-class-ref in struts-default.xml which is
com.opensymphony.xwork2.ActionSupport.
It means you have two options here to get I18N working in that case:
define com/opensymphony/xwork2/ActionSupport.properties
and put messages there
- point default-class-ref to your
base class and then defined appropriated .properties file (corresponding to
+ point default-class-ref to your
base class and then defined appropriated .properties file (corresponding to
class’ name or package)
@@ -224,7 +224,7 @@ technique is especially useful for labels of UI tags.)
-The default implementation of TextProvider which is used in ActionSupport perform evaluation of value read
from
+The default implementation of TextProvider which is used in ActionSupport perform evaluation of value read
from
bundle base on the provided key, see [Localizing Output] for an example.
Using the text tag
@@ -241,16 +241,16 @@ bundle base on the provided key, see [Localizing Output]
for an example.
Using the I18n tag
-The i18n tag pushes an arbitrary
resource bundle on to the value stack. Other tags within the scope of the i18n
tag
+The i18n tag pushes an arbitrary
resource bundle on to the value stack. Other tags within the scope of the i18n
tag
can display messages from that resource bundle.
-s:i18n name="some.package.bundle"/s:i18n
+s:i18n name="some.package.bundle"
s:text name="some.key" /
/s:i18n
-Internationalizing SiteMesh decorators is possible, but there are quirks.
See SiteMesh Plugin
+Internationalizing SiteMesh decorators is possible, but there are quirks.
See SiteMesh Plugin
for more.
Using the Key attribute of UI
Tags
@@ -263,7 +263,7 @@ for more.
I18n Interceptor
-Essentially, the i18n Interceptor pushes a locale into the ActionContext
map upon every request. The framework
+Essentially, the i18n Interceptor pushes a locale into the ActionContext
map upon every request. The framework
components that support localization all utilize the ActionContext locale. See
I18n Interceptor f
or details.
@@ -277,15 +277,15 @@ or details.
Comparison with Struts 1
-Struts 1 users should be familiar with the application.properties resource
bundle, where you can put all the messages
-in the application that are going to be translated. Struts 2, though, splits
the resource bundles per action or model
-class, and you may end up with duplicated messages in those resource bundles.
A quick fix for that is to create a file
-called ActionSupport.properties in com/opensymphony/xwork2 and put it on your
classpath. This will only work well if
+Struts 1 users should be familiar with the application.properties resource
bundle, where you can put all the messages
+in the application that are going to be translated. Struts 2, though, splits
the resource bundles per action or model
+class, and you may end up with duplicated messages in those resource bundles.
A quick fix for that is to create a file
+called ActionSupport.properties in com/opensymphony/xwork2 and put it on your
classpath. This will only work well
