Last modified by Raphaƫl Jakse on 2022/03/17

From version 12.1
edited by Vincent Massol
on 2013/11/08
Change comment: There is no comment for this version
To version 14.1
edited by Thomas Mortagne
on 2017/03/24
Change comment: Fix jira URLs

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.VincentMassol
1 +XWiki.ThomasMortagne
Content
... ... @@ -51,7 +51,7 @@
51 51  
52 52  = I18n of XWiki Objects =
53 53  
54 -This is currently not implemented (see our logged issue: [[XWIKI-69>>http://jira.xwiki.org/browse/XWIKI-69]]). There are 2 workarounds you can use:
54 +This is currently not implemented (see our logged issue: [[XWIKI-69>>https://jira.xwiki.org/browse/XWIKI-69]]). There are 2 workarounds you can use:
55 55  
56 56  * Have several objects, one for each language, with a language field, and then decide which object to use (for example in a Class Sheet, based on the current language):(((
57 57  {{code language="none"}}
... ... @@ -77,3 +77,5 @@
77 77  * In your document, use the following to get the value associated with a key: {{code language="none"}}$services.localization.render("key"){{/code}}
78 78  
79 79  This will get the value from the Resource Bundle corresponding to the current language you are using in XWiki.
80 +
81 +If you're writing an extension JAR and wish to have static translation resources, you can put them in a ##ApplicationResources*.properties## file at the root of your extension JAR and they'll get picked up by the Localization module. See the [[Localization module>>extensions:Extension.Localization Module||anchor="HProvidetranslationbundleinajar"]] for more details.

Get Connected