XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Critical Critical
    • openshift-4.7, openshift-4.8
    • None
    • None
    • None
    • No
    • 0% To Do, 0% In Progress, 100% Done

       Feature Overview

      This will be phase 1 of Internationalization of the OpenShift Console.

       Phase 1 will include the following:

      1. UI based language Selector instead of using browser detection
      2. Externalize all hard coded strings in the client code including all OpenShift static plugins
        1. Admin Console
        2. Dev Console
        3. Serverless
        4. Pipelines
        5. CNV
        6. OCS
        7. CSO
      3. Localized Date\Time
      4. Setup all processes, infrastructure, and testing required
      5. We will start with support for Chinese and Japanese lang

      Phase 1 will not include:

      1. Dynamically generated UI (Operator, OpenAPIV3Schema)
        1. Operators that surface informational messages may not have translations available
      2. Strings from non client code
        1. This may include items such as events surfaced from Kuberenetes, alerts, and error messages displayed to the user or in logs
      3. Localization of logging messages at any level is not in scope
      4. Any CLI
      5. Language support for left to right languages ie Arabic

      Initial List of Languages to Support

      ---------- 4.7* ----------

      1. Japanese - Code: ja 
      2. Chinese - Code: zh_CN, zh_TW 
      3. Korean - Code: ko

      *This will be based on the ability to get all the strings externalized, there is a good chance this gets pushed to 4.8.

      ---------- Post 4.7 ----------

      1. Spanish: - Code: es_419, es 
      2. German: - Code: de
      3. French - Code: fr
      4. Italian - Code: it
      5. Portuguese - Code: pt_BR
      6. Korean - Code: ko
      7. Hindi - Code: hi

      POC

       Initial POC PR

      Goals

      Internationalization has become table stakes. OpenShift Console needs to support different languages in each of the major markets. This is key functionality that will help unlock sales in different regions.

       

      Requirements

       

      Requirement Notes isMvp?
      Language Selector   YES
      Localized Date. + Time   YES
      Externalization and translation of all client side strings   YES
      Translation for Chinese and Japanese   YES
      Process, infra, and testing capabilities put into place   YES
      CI - MUST be running successfully with test automation This is a requirement for ALL features. YES
           

        

      Out of Scope

      1. Dynamically generated UI (Operator, OpenAPIV3Schema)
        1. Operators that surface informational messages may not have translations available
      2. Strings from non client code
        1. This may include items such as events surfaced from Kuberenetes, alerts, and error messages displayed to the user or in logs
      3. Localization of logging messages at any level is not in scope
      4. Any CLI support
      5. Language support for left to right languages ie. Arabic

       

      Assumptions

      • Each static plugin team will be responsible for externalizing all their client code strings.
      • Quick Starts will need to be translated.

      Customer Considerations

      We are rolling this feature in phases, based on customer feedback, there may be no phase 2.

      Documentation Considerations

      I believe documentation already supports a large language set.

            amobrem Ali Mobrem
            amobrem Ali Mobrem
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: