Bug 2210970 - Data Foundation - i18n misses
Summary: Data Foundation - i18n misses
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.13
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Timothy Asir
QA Contact: Prasad Desala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-30 07:28 UTC by Krishna Babu K
Modified: 2023-08-09 16:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Krishna Babu K 2023-05-30 07:28:09 UTC
Created attachment 1967825 [details]
Storage - Data Foundation (i18n misses)

Description of problem (please be detailed as possible and provide log
snippests):
  Found English entries on non-en_US UI of Data Foundation. (Reference screenshots attached)
  
1)  Navigation:
              Storage - Data Foundation
    Issue:
              Found following entries in English on non-en_US UI(ja_JP,ko_KR,zh_CN)
              'Topology' 'Backing Store' 'Bucket Class' 'Namespace Store' 
              '1 Storage System'
2)  Navigation:
              Storage - Data Foundation - Backing Store - <click name>

    Issue:
              Found following entries in English on non-en_US UI(ja_JP,ko_KR,zh_CN)
              'Actions' 'Details' 'Events'

Version of all relevant components (if applicable):
4.13.0-202.stable

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Translation is missing due to unmarked stings.

Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
yes

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:
Translations missing due to unmarked strings

Expected results:
Mark the strings for translation so that translation would reflect on target UI upon completion of translation

Additional info:


Note You need to log in before you can comment on or make changes to this bug.