Created attachment 1179769 [details] Screen shot reference for the reported issue. Description of problem: While uploading disks in RHEVM with non en_US locales, the 'Disks'->'Upload' window has untranslated entries "Browse..." and "No file selected" Version-Release number of selected component (if applicable): RHEVM Version: 4.0.2-0.2.rc1.el7ev How reproducible: Always Steps to Reproduce: 1. Log into RHEVM administration portal with non en_US locales. 2. Navigate to 'Disks'->'Upload' 3. One can observe untranslated 'Browser...' button as well 'No file selected' status. 4. Mouse hover over 'Browser...' button shows untranslated tool tip message 'No file selected' Actual results: Translations are not available. Expected results: Translations should available. Additional info: Screen-shot attached as a reference.
Verified on RHEVM 4.0.2.4-0.1 , reported issue is still reproducible.
Added translation support for FileUpload. The new strings should be translated in Zanata.
This is already merge to ovirt-engine-4.1. Shouldn't it be on MODIFIED?
(In reply to Allon Mureinik from comment #3) > This is already merge to ovirt-engine-4.1. > Shouldn't it be on MODIFIED? I'm still waiting for the translations to be merged...
Greg - how to we proceed with tracking this BZ? There's no point in leaving it on Daniel/Storage, as neither he, nor anyone else from the team can provide the translations.
At this point, we move it to the i18n component and assign to Yuko. The last upload Scott did to Zanata was 5-Jan-2017, but these new keys were merged after that. Unless this is an urgent translation need, I will push this to 4.2 translation cycle.
I can verify that translations for this change have not been made in 4.1 and are not currently available on the ovirt-4.1 version of the zanata project [1]. The strings will be available for translation, and will be translated, in the 4.2 translation cycle. This hasn't been scheduled yet. Unless there is a critical need to verify that translations are available and have been made for this bug, it can be closed normally. Translations will be performed and verified in the 4.2 translation cycle. [1] - https://translate.zanata.org/iteration/view/ovirt/ovirt-4.1
This bug has been made dependent on the first translation cycle of oVrit 4.2 (1435402). Once that translation cycle is complete, and the translations have been merged to gerrit, this bug can be tested appropriately.
Any idea why it isn't in MODIFIED state?
(In reply to Yaniv Kaul from comment #9) > Any idea why it isn't in MODIFIED state? Not sure why I'm the Assignee here. QA contact is fine, being from QE team (i18n-qe)
(In reply to Bhushan Barve from comment #10) > (In reply to Yaniv Kaul from comment #9) > > Any idea why it isn't in MODIFIED state? > > Not sure why I'm the Assignee here. QA contact is fine, being from QE team > (i18n-qe) Scott?
Commit e9bf24a87c102efba09bdececff0a8ac59678e88 includes the latest translation cycle from Zanata which should include the iamgeio strings that the engine patch was missing, at least for some languages. E.g., the key "uploadImageChooseFile=Choose File" has a Japanese override, but doesn't have a German or French override. I'm not sure if this is intentional (since this string doesn't need translation) or a bug. Regardless, moving to ON_QA so that the I18N stakeholders can either verify or fail this BZ.
Bhushan was set as assignee back in March when a few of us were discussing how to handle i18n bugs from 4.1 that wouldn't see translations until 4.2. This BZ, like others, were set to be blocked by 1435402. Once the blocker was completed, they should all transition to MODIFIED. I reassigned the bug to Bhushan in an attempt to make it easier to find/remember the test this BZ again late in the release cycle. Going forward we can do things differently to cause less confusion.
Checked with 4.2.2.4-0.1.el7 The browse button and the status message is translated now for all the locales. There is no tool-tip now for the same in 4.2. Marking it as verified. Please re-open in case of any issues.
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.