Hide Forgot
Description of problem: User Story Epic As a Cloud Administrator I would like to access all commands in the UI in Japanese so that I could set up the cloud in a language that I am most familiar with Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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.