Red Hat Bugzilla – Bug 888030
[i18n] some package set descriptions not translated
Last modified: 2014-03-16 23:32:50 EDT
Created attachment 665118 [details]
screenshot showing package set descriptions in English, not Spanish
Description of problem:
Some package set descriptions are not translated.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start DVD.
2. Select Spanish as the language.
3. Click on Seleccion de Software.
Some package set descriptions are displayed in English.
See attached screenshot.
All package set descriptions are displayed in Spanish.
Bug 858628, Comment 23.
$ qemu-kvm -m 2048 -hda f18-test-1.img -cdrom ~/xfr/fedora/F18/F18-Final/TC2/Fedora-18-TC2-x86_64-DVD.iso -usb -vga qxl -boot menu=on -usbdevice mouse
I've just pulled updates from transifex.
Thanks, Bill. This string for Robotics is not in the English source:
Suite of packages for robotics development
NB: I checked every one ... :-)
The tags are missing underscores. Isn't there a tool that could detect this problem?
$ grep -n description comps-f18.xml.in | grep -v '_'
4805: <description>Suite of packages for robotics development</description>
Thanks, fixed in git and re-pushed to TX.
Proposing F18 blocker per Fedora 18 Final Release Criterion:
"14. All critical path actions on release-blocking desktop environments should correctly display all sufficiently complete translations available for use"
1. Users need to be able to read package set descriptions to be informed about what they are installing.
2. Cannot be fixed with an update.
I've just pushed the current transifex contents to git. Anything not translated there... we don't have translations for, and would need translators to submit translations to transifex.
Discussed at 2012-12-21 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-21/f18final-blocker-review-7.2012-12-21-18.33.log.txt . Doesn't seem critical enough to block for, but accepted as NTH. The fix has already been pushed to comps, apparently, so this can be closed.
Why are you closing a bug before it has been _verified_ as fixed?
Moving to MODIFIED. Also, new translations pushed to git today (although there aren't many changes).
steve: we don't verify fixes as a matter of course, only for blockers really.