Hide Forgot
Description of problem: Bug for Translation issue with virt-manager. One Translation bug for RHEL6.1 release. Screen-shots are attached for Reference. Status: French (fr) 90% (920/72/24) Japanese (ja) 90% (919/71/26) Panjabi (Punjabi) (pa) 90% (919/71/26) Spanish (es) 90% (920/71/25) Bengali (India) (bn_IN) 86% (876/101/39) Gujarati (gu) 86% (876/101/39) Kannada (kn) 86% (877/100/39) Korean (ko) 86% (876/101/39) Malayalam (ml) 86% (876/101/39) Marathi (mr) 86% (876/101/39) Oriya (or) 86% (876/101/39) Russian (ru) 86% (876/101/39) Telugu (te) 86% (876/101/39) German (de) 85% (871/101/44) Chinese (China) (zh_CN) 74% (756/198/62) Italian (it) 73% (749/202/65) Tamil (ta) 73% (742/202/72) Hindi (hi) 72% (741/202/73) Assamese (as) 69% (711/201/104) Chinese (Taiwan) (zh_TW) 29% (300/474/242) Version-Release number of selected component (if applicable): virt-manager-0.8.6-1.el6.noarch How reproducible: Steps to Reproduce: 1. run virt-manager in above listed language 2. 3. Actual results: Many messages are in English Expected results: Need to be translated Additional info: Upstream Link: https://translate.fedoraproject.org/projects/p/virt-manager/c/default/
Created attachment 476011 [details] authorization dialog
Created attachment 476012 [details] Detail for virtual Host
Created attachment 476013 [details] Screenshot of Dialog - Translation
Created attachment 476014 [details] Creation of vm - Translation
Created attachment 476015 [details] vm creation Window - Translation
Translations missing because of the recent rebase (0.8.6-1), otherwise virt-manager was completely translated after 0.8.4-5 that we fixed via bug 575681. Now, will need to provide another patch to update rebased virt-manager. Thanks for reporting the bug! Ankit
@crobinso, 1. Would you like to receive translations directly in the upstream repo? https://translate.fedoraproject.org/projects/p/virt-manager/c/default/ 2. By which date you expect this translations? Thanks! Ankit
*** Bug 634049 has been marked as a duplicate of this bug. ***
1) Yes, translations via the fedora translation system is preferable I think. That way we can be sure any changes apply to future versions as best as possible. Sorry that I did not incorporate your 6.0 changes against upstream... 2) Not sure what the final date for this is. String freeze is March 10th, so anytime after that should be fine I think.
Alright, thx.
Since I haven't heard anything yet and it's getting late in the 6.1 cycle, moving to 6.2. Since it is likely we will rebase in 6.2, getting translations as close to 100% upstream is probably the best thing to do, that way the rebase will basically close this bug.
I'm closing this for RHEL. I think best solution for translations is to just have our translators contribute to virt-manager in transifex upstream, then new releases will already have near total string coverage. If I'm way off base please reopen, but since this bug has limped along for a months now I don't see that it's worth tracking.