Bug 877304
Summary: | [ALL_LANG][SAM Web GUI] Unlocalized Login page and tooltips. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Subscription Asset Manager | Reporter: | Lijun Li <lijli> | ||||||
Component: | katello | Assignee: | Mike McCune <mmccune> | ||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | SAM QE List <sam-qe-list> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 1.2 | CC: | agarcia, eng-l10n-bugs, jomara, qe-i18n-bugs, smaitra, tomckay | ||||||
Target Milestone: | rc | Keywords: | Translation | ||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-06-07 18:28:19 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: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 833466 | ||||||||
Attachments: |
|
Description
Lijun Li
2012-11-16 08:29:26 UTC
Created attachment 646233 [details]
Unlocalized Login page tooltips and message
Created attachment 646256 [details]
Login messages are localized when login with local ja_JP firefox browser
Hi Robert It is recommended to report a single bug for every locale, for the translation related issues for the respective locale. Please do not file separate bugs for the same locale, with the translation issues in different pages of the same Web UI. For Example, if you find several translation related issues in ja_JP locale, in SAM Web GUI, you should file a single bug for that, mentioning all the issues where you found untranslated strings in that locale. It is easier for the devel or language maintainers to find all the translation related issues (for a particular version of the component on a particular locale) in a single bug and resolve it. So, for translation, for one component, one bug per language is the standard practice. (In reply to comment #3) > Hi Robert > > It is recommended to report a single bug for every locale, for the > translation related issues for the respective locale. > Please do not file separate bugs for the same locale, with the translation > issues in different pages of the same Web UI. > For Example, if you find several translation related issues in ja_JP locale, > in SAM Web GUI, you should file a single bug for that, mentioning all the > issues where you found untranslated strings in that locale. > It is easier for the devel or language maintainers to find all the > translation related issues (for a particular version of the component on a > particular locale) in a single bug and resolve it. > So, for translation, for one component, one bug per language is the standard > practice. Thanks Satya, yup, I prefer to that file a bug for each components such as Login, User, Roles, Orgs, ... So that L10n team can save time to locate the strings and fix them soon. Note that the SAM Web GUI locale strings based on the browser locale & SAM Web GUI user locale. I do not know the relevance of your last comment. It is known that SAM Web GUI takes the browser locale by default and user can set their own locale, from the list appears after login, and also they can create new user with their preferred locale and login with that preferred credential to get their app to run on that locale. But, it is still recommended as I discussed and informed you earlier, that one translation bug per locale, for one app to maintain. And of course, for CLI, or command line translation issues, you need to file separate bug, even if the problem found is the same with the GUI one. *** Bug 886724 has been marked as a duplicate of this bug. *** c2d0a38e861b4a267cda606c295588f305c5d886 Moving all POST / MODIFIED bugs to ON_QA due to the new builds. We will be doing a new round of translations for the 1.3 drop. Closing out these bugs so that the beta starts with a clean slate. |