Bug 1954679
| Summary: | "Language Preference" is not translated in Korean language | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yanping Zhang <yanpzhan> | ||||||||
| Component: | Management Console | Assignee: | Zac Herman <zherman> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Yadan Pei <yapei> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 4.8 | CC: | aos-bugs, jokerman, spadgett, yapei | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2021-05-06 15:27:57 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1776774 [details]
string-in-dropdown
Created attachment 1780341 [details]
Language Preference translated
The code is in place to properly translate this value (as seen by my attachment), but the new translation values must not be merged in yet. Closing this as discussed for similar issues. @Zac, hi, As we discussed with Sam， the bug is to track local translation until translation values is merged. @spadget, What's your opinion if we should track this kind of translation issue in bug? Yanping, I spoke with Yadan about this last week. We agreed to use pseudolocalization to verify bugs for missing translations since the actual translations take a while to appear in the product. Yadan, let me know if that is your understanding! Thanks (In reply to Samuel Padgett from comment #6) > Yanping, I spoke with Yadan about this last week. We agreed to use > pseudolocalization to verify bugs for missing translations since the actual > translations take a while to appear in the product. > > Yadan, let me know if that is your understanding! Thanks Hi Sam, excuse me listing my understandings from our last meeting here, point me if I'm wrong : ) 1. To track the lacking of pesudo translations, we tracked them in bug and can move them to VERIFIED as long as they are pseudo translated. 2. If anything issues regarding to real translation/localization such as Japanese/Chinese/Korean specific issues, we also track them in bug and will hand over to Terry's team, these bugs can be moved to VERIFIED only when actual translations landed in. Are we on the same page? |
Created attachment 1776773 [details] string-on-modal Description of problem: When Korean language is set as the preference: 1."Language preference" in the dropdown list is not translated. 2. On the language selection modal, the "Edit language preference" is not translated. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: