Description of problem: [All-Lang][virt-manager] some contents in virt-manager GUI and error messages are not localized Version-Release number of selected component (if applicable): # rpm -q virt-manager virt-manager-1.2.1-8.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Set local language to russian: # export LANG=ru_RU.UTF8 # echo $LANG ru_RU.UTF8 2. Launch virt-manager to install a guest Step1/5, choose install guest from HTTP, then click forward to next step. Step2/5, fill a url and go to next step. Step3/5, as default setting. Step4/5, change default disk size from 9G to a large size(should larger than host left disk), such as 900G, then go to next step. Step5/5, in last step choose a available disk size, and this step leave guest name with empty, click forward to install guest. Actual results: 1. "xx GiB available in the default location", "Ready to begin the installation" are not translated. Please see "02-1.png" and "02-2.png". 2. "The requested volume capacity will exceed the available pool space when the volume is fully allocated.(xxx M requested capacity > xxx availabe)" is not traslated. Please see "03.png". 3. Some items (For example, "Performance", "Memory", "Boot Options", etc) in hardware deatils are not translated. And all items in add new hardware window are not translated. Please see "04.png". Expected results: All the string in GUI should be localized correctly. Additional info: You can refer bug 1228094 for more details.
Upstream commits: commit 2f775b6bf0038fe1690d88c9f99cfc2a68318b73 Author: Cole Robinson <crobinso> Date: Wed Sep 23 16:28:46 2015 -0400 Mark more UI strings as translatable commit 028ec70fe782ec6c4e8324f5e569e7de3d8a836b Author: Cole Robinson <crobinso> Date: Mon Sep 21 19:16:31 2015 -0400 details: Mark more HW strings as translatable Reported-by: João Pirralha <joaopirralha> commit 5f497b4d79c61179d236aa5147e115db3b2b1ab3 Author: Cole Robinson <crobinso> Date: Sun Aug 9 14:01:01 2015 -0400 Mark a couple strings as translatable There are still some strings that needs to be translated, this is what is fixed so far.
Upstream commit: commit c39592ae7b9d0d09487a964ba75fc21d24b5a03f Author: Pavel Hrdina <phrdina> Date: Fri Feb 5 16:18:16 2016 +0100 localization: mark several strings as translatable Signed-off-by: Pavel Hrdina <phrdina>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
I can reproduce this bug with version: virt-manager-1.3.2-1.el7.noarch Then try to verify this bug with new build: virt-manager-1.4.0-1.el7.noarch virt-install-1.4.0-1.el7.noarch virt-manager-common-1.4.0-1.el7.noarch qemu-kvm-rhev-2.6.0-15.el7.x86_64 libvirt-2.0.0-3.el7.x86_64 libvirt-python-2.0.0-1.el7.x86_64 Steps: 1. Set local language to russian: # export LANG=ru_RU.UTF8 # echo $LANG ru_RU.UTF8 2. Launch virt-manager to install a guest Step1/5, choose install guest from HTTP, then click forward to next step. Step2/5, fill a url and go to next step. Step3/5, as default setting. Step4/5, change default disk size from 9G to a large size(should larger than host left disk), such as 900G, then go to next step. Step5/5, in last step choose a available disk size, and this step leave guest name with empty, click forward to install guest. Results: I. Bug issue in Comment 0, already been translated: 1. In Step5/5, "Ready to begin the installation" has been translated to ru_RU. 2. When turn to hardware details page and 'add new hardware window': All translated excepts 'TPM' and 'RNG' II. Bug issue in Comment 0, always existing: 1. In Step3/5, 'MiB' not translate totally.(p1.png) 2. In Step4/5, Not translate 2.1 'xx GiB available in the default location'(p2.png) 2.2 '11.44 GiB Free/138.49 GiB In Use'(p3.png) 2.3 'There is not enough free space on the storage pool to create the volume.('xxx M requested capacity > xxx available)'(p4.png) so Pavel, about above result please have a look, since according to ZANATA result, not translate to 100%, but issue in p1.png should already translated, since another 'MiB' above has translated, others please help have a look, thanks
Created attachment 1183681 [details] p1.png
Created attachment 1183682 [details] p2.png
Created attachment 1183687 [details] p3.png
Created attachment 1183688 [details] p4.png
(In reply to zhoujunqin from comment #7) > > Steps: > > 1. Set local language to russian: > # export LANG=ru_RU.UTF8 > # echo $LANG > ru_RU.UTF8 > > 2. Launch virt-manager to install a guest > Step1/5, choose install guest from HTTP, then click forward to next step. > Step2/5, fill a url and go to next step. > Step3/5, as default setting. > Step4/5, change default disk size from 9G to a large size(should larger than > host left disk), such as 900G, then go to next step. > Step5/5, in last step choose a available disk size, and this step leave > guest name with empty, click forward to install guest. > > Results: > I. Bug issue in Comment 0, already been translated: > 1. In Step5/5, "Ready to begin the installation" has been translated to > ru_RU. > 2. When turn to hardware details page and 'add new hardware window': All > translated excepts 'TPM' and 'RNG' Those are acronyms and they are not usually translated. > > II. Bug issue in Comment 0, always existing: > 1. In Step3/5, 'MiB' not translate totally.(p1.png) This should be fixed. > 2. In Step4/5, > Not translate > 2.1 'xx GiB available in the default location'(p2.png) The translation is marked as "fuzzy", but it will be fixed by our translation team. > 2.2 '11.44 GiB Free/138.49 GiB In Use'(p3.png) This should be fixed. > 2.3 'There is not enough free space on the storage pool to create the > volume.('xxx M requested capacity > xxx available)'(p4.png) This is translated but there is a small typo in the code, this should be fixed. > so Pavel, about above result please have a look, since according to ZANATA > result, not translate to 100%, but issue in p1.png should already > translated, since another 'MiB' above has translated, others please help > have a look, thanks I'll reuse this BZ to backport the patch that will fix those issues.
Try to verify this bug with build: virt-manager-1.4.0-2.el7.noarch libvirt-2.0.0-8.el7.x86_64 qemu-kvm-rhev-2.6.0-23.el7.x86_64 Steps as Comment 7. > > II. Bug issue in Comment 0, always existing: > > 1. In Step3/5, 'MiB' not translate totally.(p1.png) > > This should be fixed. 'MiB' not translated. > > 2.2 '11.44 GiB Free/138.49 GiB In Use'(p3.png) > > This should be fixed. Has not translated. > > > 2.3 'There is not enough free space on the storage pool to create the > > volume.('xxx M requested capacity > xxx available)'(p4.png) > > This is translated but there is a small typo in the code, this should be > fixed. Not fixed yet, please according to p5.png and p6.png, i think some word missed, but not sure. and what's more i also find another question by operation but don't know how to reproduce, please help check p6.png, thanks.
Created attachment 1199375 [details] when create a volume size large than available
Created attachment 1199376 [details] p6:ZANATA search result
Created attachment 1199377 [details] p7:new issue find
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2269.html