[Pike] json list of not_i18n strings, when in a localized interface/LANG
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Description:
This bug report is about strings which are not i18nized, when in a localized interface or LANG (say Japanese)
Steps to reproduce:
Access the Web UI (TripleO) in preferred LANG
Navigate the Web UI
Register Nodes in the Web UI
Inspect the Hardware of Nodes in the Web UI
Edit Overcloud Plan Parameters in the Web UI
Tag Nodes into Roles in the Web UI
Expected result:
100% Translated
Actual result:
Not 100% Translated (perhaps due to partial i18nization)
Environment:
Pike release
Logs & Configs:
1. Attaching not_i18n.json file, dictionary of current_url (key) and list_of_not_i18n strings (value)
2. In logs.html, one can drill down the test case (written using robotframework) to reach current URL and scrapped text (screenshot attached)
Note: scrapped text gets filtered to get list of strings (which are not localized) and get collected into not_i18n.json file
tags: | added: ui |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in tripleo: | |
milestone: | none → queens-3 |
description: | updated |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
status: | Triaged → Won't Fix |
json list of not_i18n strings for downstream (based on Pike), when in ja google-chrome