Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-16392

Translation Tracker - Pull 100% completed translations from the Phrase (a.k.a Memsource) for all the Satellite Resources, and package them into installable build, to determine readiness for Satellite L10N QA milestone

XMLWordPrintable

      Created attachment 1939123 [details]
      Transtats screenshot, wherein translations statistics is not 100% for locales: ja, zh-CN, fr, for build foreman-3.5.1.2-1.el8sat, implying completed Phrase translations are not pulled and packaged yet

      Description of problem:
      This is Translation tacker to track: Pull 100% completed translations from the Translation Platform - Phrase (a.k.a Memsource) for all the following Sat-6.13 Resources (also listed at http://satellite.transtats.psi.redhat.com/pipelines/release/sat-6-13), and package them into installable build, to determine readiness for Sat-6.13 L10N QA event:

      bastion_katello
      foreman
      foreman_ansible
      foreman_azure_rm
      foreman_bootdisk
      foreman_discovery
      foreman-discovery-image
      foreman_fog_proxmox
      foreman_google
      foreman_kubevirt
      foreman_leapp
      foreman_openscap
      foreman_puppet
      foreman_remote_execution
      foreman_salt
      foreman_scc_manager
      foreman_setup
      foreman_snapshot_management
      foreman_statistics
      foreman_tasks
      foreman_templates
      foreman_virt_who_configure
      hammer-cli
      hammer-cli-foreman
      hammer-cli-foreman-admin
      hammer_cli_foreman_ansible
      hammer_cli_foreman_azure_rm
      hammer_cli_foreman_bootdisk
      hammer_cli_foreman_discovery
      hammer_cli_foreman_kubevirt
      hammer_cli_foreman_openscap
      hammer-cli-foreman-puppet
      hammer-cli-foreman-remote-execution
      hammer_cli_foreman_tasks
      hammer-cli-foreman-templates
      hammer-cli-foreman-virt-who-configure
      hammer-cli-katello
      katello

      Version-Release number of selected component (if applicable):
      Satellite-6.13 Snap 6

      How reproducible:
      Always

      Steps to Reproduce:
      1. Do a preferred login at Satellite Web-UI with Japanese google-chrome
      2. Navigate most of the web UI to spot strings obviously in English
      3. Additionally, do following in a terminal too:
      3.1 Visit the Brew build system
      3.2 Enter the downstream package name for the aforementioned said Sat-6.13 resource (say, foreman)
      3.3 Download the said srpm
      3.4 Unpack the sprm
      3.5. Unpack the sources from the SPEC file
      3.6. Calculate the Translation statistics of PO file using msgfmt utility: find . -name "*.po" -exec msgfmt -vvv -o /dev/null {} \;

      Actual results:
      1. English strings visible while navigating localized web-UI
      2. Not 100% complete for in-house locales: ja, zh_CN, fr; eventually not getting user experience in native language

      Expected results:
      1. No English strings visible while navigating localized web-UI
      2. Should be 100% complete for in-house locales: ja, zh_CN, fr; eventually should get user experience in native language

      Additional info:
      1. For each aforementioned Sat-6.13 Resource, respective (Build) Changelog could possibly mention: Pull Translations from Phrase or similar, so as to figure it out if downstream Translations are packaged or not
      2. Please refer http://satellite.transtats.psi.redhat.com/jobs/log/dcf426e0-96bc-428d-81a3-e15f4115daf3/detail
      3. Pleaser refer https://cloud.memsource.com/web/project2/show/ASQQUcSoKMp1pag1fdbooa - as it shows foreman resource being completed for in-house locales: ja, zh_CN and fr
      4. Currently, did not find downstream bugzilla components for the aforementioned Sat-6.13 Resource i.e. foreman_* plugins and hammer-cli_* plugins
      5. Please, suggest if there are other workarounds to know if downstream translations are ideally packaged or not (ideally: fixed_in_version of the build incorporating 100% completed translations pulled from Translation Platform - Phrase, is what is expected here, towards effective resolution of the reported problem)

              ekohlvan@redhat.com Ewoud Kohl van Wijngaarden
              sshedmak@redhat.com Sandeep Shedmake
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: