|Title|Wiki-based localization
|Date|20-Mar-2007 15:35:08 EET
|JSPWiki version|2.6
|Submitter|JanneJalkanen
|[Idea Category]|UserInterfaceIdea
|Reference|
|[Idea Status]|NewIdea

Translating property files is boring and error-prone, and they easily fall out of use.  We should have a LocalizationPlugin (or some other tool), which takes the contents of a wiki page, and creates a regular property file out of it.

The contents could e.g. look like this:

{{{
[{Localize source='LatestBaseBuild/i18n.properties' language='fi_FI' version='2.6.1'

info.title = Sivuhistoria
info.welcome = Tervetuloa
}]
}}}

Which would generate something like this:

__Language__: fi_FI\\
__Version__: 2.6.1\\
__Latest source version__: 2.6.5

|| ID || English || fi_FI
| info.title | Page History | Sivuhistoria
| info.welcome | Welcome | Tervetuloa
| info.goodbye | Goodbye |

Where "info.goodbye" is an addition between 2.6.1 and 2.6.5, and therefore appears as blank.  That would make it really easy with one glance to see what is missing from localization.

It would also be relatively trivial to convert the contents of the plugin to a property file automatically and include it in a build.

The base for the translation would be taken from the default language bundle which ships with JSPWiki; someone would just need to upload the new version into wiki.

This idea works also for multiple files.

This is not without precendent, [Meebo|http://www.meebo.com] is already using a wiki for translations.  It has spawned translations for useless languages as well, such as "l33t" and "bork", but I think we could survive those ;-)

Problem: How to defend against vandalism?  Maybe allow only trusted users to edit?


----

Additional issue: how to add missing/new localization id's automatically to the page?

--JanneJalkanen, 20-Mar-2007


----

Second issue: somehow comments need to be included as well so that users know in which context a particular string appears.

--JanneJalkanen, 20-Mar-2007