Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-1826

i18n keys: As a developer I don’t have to define i18n keys for every translatable item, if they follow the convention, so that the process is less redundant and error prone

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Fixed
    • Icon: Critical Critical
    • 5.1
    • 5.0.1
    • None
    • Yes
    • 5.1 Beta1- Frontend, 5.1 - Final
    • 8

      In Magnolia 5.0, many Strings used in UI are either hardcoded, or used from configuration without i18n. To allow full i18n in M5.1, such Strings have to be replaced by message keys, and the proper i18n code has to be used.

      See http://wiki.magnolia-cms.com/display/DEV/i18n+in+Magnolia+5
      And See Progress:
      http://wiki.magnolia-cms.com/pages/viewpage.action?pageId=72974954

      Meeting notes:
      https://www.evernote.com/shard/s249/sh/659d7e8a-3e37-4026-aaac-61b016b3c94a/a18676c38f7ed947d87b408523f90ec4

        Acceptance criteria

          There are no Sub-Tasks for this issue.

              gjoseph Magnolia International
              jchocholacek Jozef Chocholacek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD

                    Estimated:
                    Original Estimate - 8d
                    8d
                    Remaining:
                    Remaining Estimate - 8d
                    8d
                    Logged:
                    Time Spent - Not Specified
                    Not Specified