Red Hat Bugzilla – Bug 176097
Untranslated license agreement dialogue
Last modified: 2007-11-30 17:07:22 EST
firstboot uses eula_strings.py as the source of strings for the translations (as
can be seen in po/firstboot.pot).
However, the strings in eula_strings.py aren't synced with eula.py which
actually uses the translations.
firstboot should use eula.py directly, rather than a useless eula_strings.py
1. Launch firstboot in japanese:
LC_ALL=ja_JP LANG=ja_JP sudo firstboot
2. Decline the license on the second screen
3. Check the dialogue, it says:
Do you want to reread or reconsider the Licence Agreement?
If not, please shut down the computer and remove this product
from your system.
where the translations (in the .pot, the .po, and the eula_strings.py) say:
Do you want to reread or reconsider the License Agreement?
Also, it should be "License" in those messages, not "License" (licence is a
verb, not a noun).
For this to happen, redhat-release will need to start shipping translation files
of its own and use its own domain for translation. We're only using
eula_strings.py right now because nobody else is providing those strings.
Yeah, the eula.py module is part of redhat-release, and should really contain
its own translations, rather than relying on firstboot to be kept in sync.
Taking ownership of the ticket. Chris, I'll ping you soon to find out what
needs to be done.
Dennis - any info you need from me on this?
NEEDINFO_ENG has been deprecated in favor of NEEDINFO or ASSIGNED. Changing
status to ASSIGNED for ENG review.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Although this bugzilla was approved for RHEL 4.5, we were unable
to resolve it in time to be included in the release. Therefore
it is now proposed for RHEL 4.6.
We don't have the resources for fixing this in 4.6, so I'm NAKing.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.