This is an ideas page for wiki localization (aka localisation).

I'm not very good in jsp so i just post this idea instead of develop it myself.
my idea is to read all langusge specific visible text from a extra file, where variables for e.g the text [[Search Wiki] are stored like search_wiki = Wiki durchsuchen. This variables (here in german) could easy be edited and devolping a language specific jspwiki would be easyier.

--[Heinz-Josef Lücking|http://webgis.dyndns.org:8080/giswiki/Wiki.jsp?page=HeinzJosefL%FCcking]

----

Yes.  We should basically develop language-specific bundles to the different plugins, tags, etc, that cannot be directly edited in a JSPWikiTemplate.

I'll add more once I get my thoughts straight on this matter :-).

-- JanneJalkanen

----
From mine point of view this should be very easyly be done.

just one basic files called e.g. {{language_de.jsp}} (for german language)
this file are used by every other files {{include ...}} by settings within the jspwiki.properties like e.g. {{language_file = language_de}} and {{language_default = language_en}}. That would be all. 

sounds easy or?

this language_xx file should just contain variables for specific language support, not more!
e.g.\\
  {{Search_Wiki = Wiki Durchsuchen}}\\
etc...

One basic file in english i think would be enough to get this working.

--[Heinz-Josef Lücking]

If you want it really well done, think about a multilingual Wiki, where the user can define the language of the interface. 

(But I'm not sure, if that really is of matter, as WikiLinks themselves are language dependend and most of the Wiki content would be language specific anyway ...)

--[MarcAndreDumont]

Hey Marc

Your german templates have two (!) zip files. One for the txt-files (very good) and one for the jsp-files

the jsp-file are (1') not that easy and can (2') change by change of this wiki.
for those two reasons i think a basic language variable-file would things much more easyier.
You made your one translation whith links to names you prefer.
This would be  a further enhancement to a basic language file; additional links to language specific txt-files with defaults aon english files

the configuration should be easy!!

--[Heinz-Josef Lücking]

My proposal is to the JSP-part of the JSPWiki, not the texts:
Currently I have collected some experience using the localization features of java (using the [ResourceBundle|http://java.sun.com/j2se/1.4.1/docs/api/java/util/ResourceBundle.html]). The last JSP-code of JSPWiki I have looked into was sub 2.x; but it seemed for me to be possible to use a ResourceBundle in there.

There is some more documentation about JSP and localization at [http://developer.java.sun.com/developer/technicalArticles/Intl/MultilingualJSP/].

In fact I would like to contribute the switch of JSP-Pages of JSPWiki to internationalization. This would include the English language as default.

--[Olaf K]

!Using Struts
I see 2 main advantages in using Struts 1.1 framework (http://jakarta.apache.org/struts):
* I18N is supported through property files (more exactly resource bundles) using taglibs
* You would benefit from the tiles API to create JSPWiki templates.

I have the idea that moving JSPWiki to Struts is not difficult (I actually have a very basic version working). Since Struts is getting widespread, that would be a good improvement and the occasion to bring in 2 major features.

--[Denis Balazuc|DenisBalazuc]

I'm actually far more interested in [Velocity] than [Struts] :-).  Velocity would allow far better templating support.

I have nothing against Struts as such, but I think we can do localization easily without it as well.  It is a very complicated (and big) piece of code to bring in to do something that we can do without it as well.

-- [JanneJalkanen]