Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-900

make it possible for end users to localize the GUI

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Outdated
    • Major
    • None
    • 3.0 Beta 1
    • None
    • None

    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?

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              pbaerfuss Philipp Bärfuss
              kraft Boris Kraft
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD