| Summary: | [RFE] Internationalization of UI In Japanese | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Anandeep Pannu <apannu> |
| Component: | openstack-tripleo-ui | Assignee: | Florian Fuchs <flfuchs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ola Pavlenko <opavlenk> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 11.0 (Ocata) | CC: | achernet, ccollett, flfuchs, jjoyce, jpichon, jschluet, lbopf, qe-i18n-bugs, sclewis, slinaber, sshedmak, tvignaud, ykatabam |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, i18n |
| Target Release: | 11.0 (Ocata) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/tripleo/+spec/tripleo-ui-i18n-support-for-js | ||
| Whiteboard: | upstream_milestone_ocata-rc1 upstream_definition_approved upstream_status_implemented | ||
| Fixed In Version: | Doc Type: | Release Note | |
| Doc Text: |
With this update, the user interface is now partially internationalized and available in Japanese and Simplified Chinese. Note that only the interface itself is internationalized at this stage. The strings that come from other services such as the parameters, templates, and environments for the TripleO Heat Templates, the validations, and the notifications are not yet internationalized.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-05-22 17:19:24 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: | |
|
Description
Anandeep Pannu
2016-10-18 15:42:20 UTC
Changing to Assigned since I know that team is working on it upstream Upstream blueprint: https://blueprints.launchpad.net/tripleo/+spec/tripleo-ui-i18n-support-for-js A quick status update: 5 of 8 upstream patches that are preparing the string extraction are awaiting reviews. Once all have been merged, the strings can be extracted from source to start work on the translation itself. AFAIK the translation work is expected to be started end of January which should be enough time to land all necessary patches. This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release. All 8 patches have been been merged and the blueprint has been closed. Also, the infrastructure to automatically propose new translations is now in place and working. There's still one unmerged patch which internationalizes the notifications and will probably be merged pretty soon. Once the Japanese translation is complete, it will can added as a bugfix or backport to Ocata. Making a shot at writing a Doc Text release note, following on the various conversations around the current i18n limitations. (In reply to Julie Pichon from comment #12) > Making a shot at writing a Doc Text release note, following on the various > conversations around the current i18n limitations. Thank you very much, Julie. Switching status on ON_QA since the i18n QE team has been working on this since March 13. Sandeep, could you switch the status to VERIFIED if/when you are done? I'm not sure if the QA contact should be changed? My impression at the moment is that this RFE should probably be marked as VERIFIED as it has generally been proven to work, and the remaining bugs should be handled separately, though correct me if I'm wrong. From Comment 14 and Comment 14, moving to VERIFIED for sure. (In reply to sandeep shedmake from comment #16) > From Comment 14 and Comment 14, moving to VERIFIED for sure. correction: Comment 14 and Comment 15 Thank you Sandeep! Setting rhos-11.0 release flag to ensure this bug is pulled into the RHOSP 11 Release Notes. |