Changes for page Localization Module
Last modified by Anca Luca on 2023/11/22 12:02
From version 40.1
edited by Thomas Mortagne
on 2018/09/12 17:23
on 2018/09/12 17:23
Change comment:
There is no comment for this version
To version 41.1
edited by Oana Florea
on 2019/12/03 15:44
on 2019/12/03 15:44
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki.T homasMortagne1 +xwiki:XWiki.OanaTabaranu
- ExtensionCode.ExtensionClass[0]
-
- Description
-
... ... @@ -67,6 +67,10 @@ 67 67 my.other.translation.key=Some other translation message 68 68 {{/code}} 69 69 70 +{{info}}**Tip:** the single quotes inside values need to be doubled. Example: 71 +my.translation.key=des droits d''auteur 72 +{{/info}} 73 + 70 70 == Provide translation bundle in a jar == 71 71 72 72 A jar (installed extension or core extension) can come with its own translations bundle. For that all is needed is to name it ##ApplicationResources.properties## for the default language and ##ApplicationResources_<locale>.properties## (for example ##ApplicationResources_pt_BR.properties##) for its translations and put them in the default package (i.e. root of your JAR). It will be automaticlally registered at startup for core extensions and when installed for installed extension (it will also be unregistered automatically if the jar extension is uninstalled).