THIS IS A PLACEHOLDER TICKET FOR A POTENTIAL L10N WORK IN RHEL 7.6
Your package is on the list of the top priority packages for RHEL 7 localization https://mojo.redhat.com/docs/DOC-1145886
After String Freeze date (https://pp.engineering.redhat.com/pp/schedules/rhel-7-6):
- the amount of translated strings will be checked for the supported languages (Japanese, all other languages would need to be requested by RHEL 7 PM).
- all untranslated/marked for Translation strings in those languages (Japanese atm) are going to be localized and you'll receive a localization patch (in form of a PO file or you'll be given access to our internal Zanata)
- in case no untranslated strings are detected in concerned languages or no internal or other localization work out of scope and policy of Red Hat Localization team happened, this placeholder ticket may be closed.
- during translation work, the placeholder BZ will be assigned to l10n PgM or respective Translator.
- post translation and commit, the placeholder BZ should be assigned to respective package maintainer(developer) by l10n PgM or respective translator with a note marking end of translation work and a request to rebuild the package to include latest translated strings.
- after your package is rebuilt with the localization patch, the ticket moves to ON_QA and the i18n QE and l10n QA will follow to check sanity and coherency of translated strings.
Version-Release number of selected component (if applicable):7.6
100% translated strings in Japanese (+ other language in case of specific RHEL 7 PM specification)
Additional info: n/a
Note: As per bug 1568728, Cockpit will be rebased for RHEL 7.6.0. The deadline for this is June 11, I'm going to do that the week before though (so around June 4). This will change a lot of translations. String freeze is in August, so this should match up well. But it doesn't make much sense to start working on translations before the rebase.
Updating translations and doing validation in https://github.com/cockpit-project/cockpit/pull/9871
I have a patch and a build, but this is now blocked on https://projects.engineering.redhat.com/browse/RCM-39641
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.