Details

    • Sprint:
      [2.3] Sprint 2
    • Story Points:
      2

      Description

      Changes

      • Make ezsystems/ezplatform-i18n and ezplatform-i18n/* compatible with ezplatform 2.0
      • Prepare extraction & synchronization script for ezsystems/ezplatform-admin-ui to https://github.com/ezsystems/ezplatform-i18n.
      • Consider reusing the existing ezsystems/PlatformUIBundle translations for ezplatform-admin-ui, as there are a lot in common. It could be by copying the files, or using some semi-automated procedure.
      • Add the crowdin in-context translation to ezplatform-admin-ui, with the same behaviour than in v1.

      Expectations

      As a maintainer, I can install any of the ezplatform-i18n/ packages on eZ Platform v2.

      Given that I am using eZ Platform v2
      When I install any of the ezplatform-i18n/* packages using composer
      Then I don't get an error from composer
      And the package is installed.

      As an editor, the UI is translated to my language

      given that my browser is set to accept my language
      and that language package is installed and complete,
      Then the v2 admin UI is translated to that language.

      As a translator, I can translate the v2 UI to my language with Crowdin's in-context tool

      Given that I am on the admin UI
      When I add an ez_in_context_translation cookie with the value 1 to my eZ Platform requests,
      And I reload the admin UI
      Then crowdin's in context translation UI is displayed

        Activity

        Hide
        Bertrand Dunogier added a comment - - edited

        ezplatform-i18n master now contains the translations for 2.x in master. The previous translations were branched to 1.0 so that we can still release / update them.

        Crowdin has been configured for this, with the two versions separated. All previously existing translations can be copied over using TM (Translation Memory). Done for french for testing, needs to be done for the other.

        Remaining is to generate v2.x of the translation packages (https://github.com/ezplatform-i18n).

        Some string in the backoffice don't show up for in-context translation, meaning that they aren't known to the ach-UG translation. May require a re-sync of translations from ezplatform-admin-ui to ezplatform-i18n (done at 12:00).

        Show
        Bertrand Dunogier added a comment - - edited ezpublish-kernel#2342 : updates how the custom locale is set using a cookie ezplatform-admin-ui#499 : adds the JS code that enables in-context translation ezplatform-i18n master now contains the translations for 2.x in master . The previous translations were branched to 1.0 so that we can still release / update them. Crowdin has been configured for this, with the two versions separated. All previously existing translations can be copied over using TM (Translation Memory). Done for french for testing, needs to be done for the other. Remaining is to generate v2.x of the translation packages ( https://github.com/ezplatform-i18n ). Some string in the backoffice don't show up for in-context translation, meaning that they aren't known to the ach-UG translation. May require a re-sync of translations from ezplatform-admin-ui to ezplatform-i18n (done at 12:00).
        Hide
        Bertrand Dunogier added a comment - - edited

        PR against ezplatform-i18n that prepares master for 2.x translations: ezsystems/ezplatform-i18n#36.

        Show
        Bertrand Dunogier added a comment - - edited PR against ezplatform-i18n that prepares master for 2.x translations: ezsystems/ezplatform-i18n#36 .
        Hide
        Łukasz Serwatka added a comment - - edited

        Bertrand Dunogier You can skip ezstudio-from-builder and ezstudio-notifications. First one is obsolete and second one will be merged into the ezplatform-admin-ui.

        What is valid is:

        ezplatform-page-fieldtype
        ezplatform-page-builder
        flex-workflow
        date-based-publisher

        Show
        Łukasz Serwatka added a comment - - edited Bertrand Dunogier You can skip ezstudio-from-builder and ezstudio-notifications. First one is obsolete and second one will be merged into the ezplatform-admin-ui. What is valid is: ezplatform-page-fieldtype ezplatform-page-builder flex-workflow date-based-publisher
        Hide
        Bertrand Dunogier added a comment -

        ezsystems/ezplatform-i18n#36 merged to master.

        Show
        Bertrand Dunogier added a comment - ezsystems/ezplatform-i18n#36 merged to master.
        Hide
        Bertrand Dunogier added a comment -

        Updates to the script that copies the source translations from our various packages to ezplatform-i18n: https://github.com/ezsystems/ezplatform-i18n/pull/37.

        I'll update the directories list based on your feedback, Łukasz Serwatka.

        Show
        Bertrand Dunogier added a comment - Updates to the script that copies the source translations from our various packages to ezplatform-i18n: https://github.com/ezsystems/ezplatform-i18n/pull/37 . I'll update the directories list based on your feedback, Łukasz Serwatka .
        Hide
        Bertrand Dunogier added a comment -
        Show
        Bertrand Dunogier added a comment - added the EE packages to ezplatform-i18n fixed the sync script ( https://github.com/ezsystems/ezplatform-i18n/pull/37 ) updated crowdin to make those files translatable updated the ach-UG package with the EE strings
        Hide
        Sylvain Guittard added a comment -

        For next sprint, here are the elements to add:

        • sub-items
        • missing elements of Page Builder
        • Universal Discovery Widget
        • Multi-File Upload
        Show
        Sylvain Guittard added a comment - For next sprint, here are the elements to add: sub-items missing elements of Page Builder Universal Discovery Widget Multi-File Upload
        Hide
        Bertrand Dunogier added a comment -

        Once the strings extracted from JS code are in their respective repositories, the next step will be to copy them to ezplatform-i18n, and configure crowdin for them. Once we have done that, the strings can be translated from crowdin. An update of the ach-UG package will be required to get in-context on the new strings.

        Show
        Bertrand Dunogier added a comment - Once the strings extracted from JS code are in their respective repositories, the next step will be to copy them to ezplatform-i18n, and configure crowdin for them. Once we have done that, the strings can be translated from crowdin. An update of the ach-UG package will be required to get in-context on the new strings.

          People

          • Assignee:
            Unassigned
            Reporter:
            Bertrand Dunogier
          • Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Agile