[MAGNOLIA-900] make it possible for end users to localize the GUI Created: 29/May/06  Updated: 23/Jun/14  Resolved: 23/Jun/14

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0 Beta 1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

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?



 Comments   
Comment by Philipp Bracher [ 13/Jun/06 ]

first we need a better documentation of the current state (wiki). We should change in a rush and therefore I postponed

Comment by Philipp Bracher [ 30/Jan/07 ]

I think the current solution is not that bad. But we need a webapp, where 'normal' users can translate the files.

Comment by Magnolia International [ 30/Jan/07 ]

Maybe a maven report could also help in spotting missing translations.
As for Boris' suggestion, it might indeed be interesting for some users to change the GUI wording themselves, within Magnolia, but seems far fetched at the moment.
We could also think about specific svn permissions that would allow more people to help translating (and that would be easier if translations were in separate directories I guess)

Comment by Jan Haderka [ 04/Sep/08 ]

While this is certainly important new feature, it is not system critical (i.e. doesn't cause loss of data or system crash as per definition of critical issue)

Generated at Mon Feb 12 03:21:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.