Uploaded image for project: 'Content Translation Support'
  1. Content Translation Support
  2. MGNLCTS-69

As an editor I want i18n support with no trade-offs, to create multisite & multilanguage websites.

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None

    Description

      Essential i18n features are missing today, which makes a lot of customization necessary in projects:

      Examples:

      • translated urls (not just uri-parts like the language, but the whole url with categories etc.)
      • global, local and "glocal" content (shared, copied, inherited content)
      • differentiation between country/language combinations, for example de-de != ch-de or uk-en != us-en
      • separate publication of languages (for example when content is not fully translated yet in all languages, publication of specific translation should be possible)
      • translation view (two languages on the screen, see Contens CMS http://www.itespresso.de/wp-content/uploads/2013/02/contens_formular.jpg)

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                mbperi Michael Büchele
                AuthorX
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Checklists

                    Task DoD