Localization Workflow tools

XMLWordPrintable

    • Critical
    • Hide
      Refactoring of Localization: Customized locale-files in ./client-specific/locales are automatically reformatted to ".zxliff". The old ".xliff" files can be deleted. Use the CLI command "l10n:upgrade-clientspecific" if this somehow did not work.
      NOTE: the command must run with root credentials.
      NOTE: The git-based client specific folders must be committed/pushed after the update was rolled out
      Show
      Refactoring of Localization: Customized locale-files in ./client-specific/locales are automatically reformatted to ".zxliff". The old ".xliff" files can be deleted. Use the CLI command "l10n:upgrade-clientspecific" if this somehow did not work. NOTE: the command must run with root credentials. NOTE: The git-based client specific folders must be committed/pushed after the update was rolled out
    • Hide
      7.34.0: First set of internal CLI tools for internal application translation management released

      [x.xx.xx] Finalize refactoring of Localization:
      * replace most german localizations with the english targets to clean up the source code
      * Add several tools to enable a localzation workflow independant from developers (CLI tools to extract, update and create tasks for the localization of t5)
      * JSON based localizations now also will be exported/imported as XLIFF in the localization tasks to enable the proper use of TMs
      Show
      7.34.0: First set of internal CLI tools for internal application translation management released [x.xx.xx] Finalize refactoring of Localization: * replace most german localizations with the english targets to clean up the source code * Add several tools to enable a localzation workflow independant from developers (CLI tools to extract, update and create tasks for the localization of t5) * JSON based localizations now also will be exported/imported as XLIFF in the localization tasks to enable the proper use of TMs

      Some tools need to be developed to fully suppport our new localization workflow

      See: https://jira.translate5.net/browse/TRANSLATE-5188

      See: https://confluence.translate5.net/display/MI/Localization+in+translate5

      Needed changes & tools

      • add new global function Localization::trans() to localize (-> DONE)
      • include translations from ZfExtended_ResponseExceptionTrait::createResponse  (-> DONE)
      • Change source-strings in all XLIFFs to EN target (-> DONE)
      • Change IDs to MD5 (-> NOT DONE, this needs further discussing as it is not technically feasible)
      • Add statistic about new strings / missing translations per language to t5 l10n:update  (-> DONE)
      • Move from programmatic localizations in comments to PHP attribute/annotation based ones (->DONE)
      • Add resname-atrtributes to trans-units: module & plugin (->DONE)
      • The generated Import-ZIPs for localization tasks non EN shall contain the EN localized JSON Files renamed to the desired target-locale. The translation is expected to be done with a TM. This ensures, developers need only to add/amend EN localized json-files (->DONE)
      • Add command to autmatically create a localization task for each locale. Task name shall be: translate5-localization-[VERSION] - [locale] (->DONE)
      • Add command to automatically import a localization task from translate.translate5.net for the current - and if not found - last version of t5. If not found, the command shall give a selection of the last 5 localization-tasks and automatically import all 4 tasks (-> NOT DONE, will be seperate issue)

            Assignee:
            Axel Becher
            Reporter:
            Axel Becher
            Thomas Lauria
            Stephan Bergmann, Sylvia Schumacher
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: