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

support i18n in the GUI

    XMLWordPrintable

Details

    Description

      I have the following requirements for any mechanism that deals with internationalization in Magnolia:

      1) strings must be extracted automatically from java and jsp at least, hopefully also from javascript and anything else that will come along.
      2) anybody must be able to do translations even if he has never written a line of code before
      3) it must be easy to detect if new strings have been introduced into the program
      4) translations must be easy to distribute
      5) the system must support the idea of having "private" translations as well as the standards translations. With that I mean that if I write a custom module, I should not be forced to put its translation into a global translation file. Or to put it otherwise: some kind of hierarchical or cascading mechanism must be possible.
      6) it must be easy to add your own translations (go to www.magnolia.info, check if translation to "schwäbisch" exists, if not, click "add translation", type "schwäbisch", download po files, start your editor, translate to your hearts content, upload the file, thats it.)
      7) Installation of the new language must be supported by Magnolia directly

      These requirements can be solved using GNU gettext. Also see the discussion on the dev list regarding i18n and Gnu gettext.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              kraft Boris Kraft
              kraft Boris Kraft
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: