make it possible for end users to localize the GUI
--------------------------------------------------
Key: MAGNOLIA-900
URL: http://jira.magnolia.info/browse/MAGNOLIA-900
Project: magnolia
Type: Improvement
Versions: 3.0 Beta 1
Reporter: Boris Kraft
Assigned to: Philipp Bracher
Priority: Critical
Fix For: 3.0 RC1
The new way of putting the strings inside of each module (which in turn is a
jar in the end) makes it currently close to impossible for end users to provide
translations.
We could:
* provide a different mechanism instead of storing translations inside modules
(maybe a localization module?)
* provide documentation so that end users know exactly step by step what to do
* provide a tool that makes it easy no matter how its done below the surface
In any case we need it fast. If we make it so hard to translate the GUI, we
will not get translations. For me that makes it a critical issue as we need the
translations for the final release.
Understand that the people doing the translations need to be able to
* find the file to be translated
* test the translation
* provide the file back to us
Also do the math - if we have 10 modules and 15 languages, *we* have to juggle
150 language files.
Any suggestions?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
