Description of problem: Some strings missing i18n on the operator subscription page Version-Release number of selected component (if applicable): 4.7 How reproducible: Always Steps to Reproduce: 1. Visit the admin console and add the url search params `?pseudolocalization=true&lng=en` 2. Navigate to OperatorHub 3. Click any Operator that isn't already installed in the current Namespace 4. Click Install (dismiss Community operator alert if you encounter it) Actual results: Most of the text on the Operator install page is not pseudolocalized. Expected results: All of the static text (form field labels, help text, static radio options, alerts, button text, etc.) on the Operator install page should be pseudolocalized.
Created attachment 1749647 [details] 01 - placeholder text not pseudolocalized
Created attachment 1749648 [details] 02 - error message not pseudolocalized
1. Placeholder text 'Selected Namespace' for Installed Namespace dropdown is not pseudolocalized, see attachment 01 [details] - placeholder text not pseudolocalized 2. When clicking 'Install' button without choosing namespace, it will throw error `namespaces "undefined" not found`, this error message is not pseudolocalized, see attachment 02 [details] - error message not pseudolocalized Assigning back to double confirm
(In reply to Yadan Pei from comment #4) > 1. Placeholder text 'Selected Namespace' for Installed Namespace dropdown is > not pseudolocalized, see attachment 01 [details] - placeholder text not > pseudolocalized > 2. When clicking 'Install' button without choosing namespace, it will throw > error `namespaces "undefined" not found`, this error message is not > pseudolocalized, see attachment 02 [details] - error message not > pseudolocalized > > Assigning back to double confirm I've opened a follow on PR for #1, but #2 is expected. That error message is coming directly from the API response, so we can't always translate it. We do have a fallback value that is displayed if the API call fails without an error message. I checked and my PR does include that fallback message in the translations, so I think we have covered that error alert as much as we can.
1. Visit the admin console and add the url search params `?pseudolocalization=true&lng=en` 2. Navigate to OperatorHub 3. Click any Operator that isn't already installed in the current Namespace 4. Click Install (dismiss Community operator alert if you encounter it) Check static text (form field labels, help text, static radio options, alerts, button text, etc.) on the Operator install page, all have been pseudolocalized Verified on 4.7.0-0.nightly-2021-01-26-162323
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633