Bug 539233 - Make menu entries translatable
Summary: Make menu entries translatable
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils   
(Show other bugs)
Version: rawhide
Hardware: All Linux
low
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords: FutureFeature, i18n, Translation, Triaged
Depends On:
Blocks: 493621 538726
TreeView+ depends on / blocked
 
Reported: 2009-11-19 17:32 UTC by Ville-Pekka Vainio
Modified: 2010-08-03 13:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-03 13:42:11 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Ville-Pekka Vainio 2009-11-19 17:32:05 UTC
Description of problem:
The "SELinux Policy Generation Tool" and the "SELinux Management" menu entries are not translatable, they should be.

The "SELinux Troubleshooter" menu entry is translatable. It's of course in a different package, but maybe the required changes can be taken from there.

Version-Release number of selected component (if applicable):
policycoreutils-gui-2.0.74-4.fc12.x86_64

Comment 1 Martin-Gomez Pablo 2009-12-19 13:50:58 UTC
The problem is that this string came from the .desktop file which came as an additional source and not as part of the upstream project.

Comment 2 Igor Pires Soares 2010-03-25 20:41:10 UTC
This has been a recurring bug from past Fedora releases and still remains in Rawhide (policycoreutils-gui-2.0.81-3.fc13.i686).

Comment 3 Piotr Drąg 2010-07-29 13:35:24 UTC
http://cvs.fedoraproject.org/viewvc/policycoreutils/po/policycoreutils.pot?root=elvis&r1=1.15&r2=1.16

It apparently has been fixed in CVS.

Comment 4 Martin-Gomez Pablo 2010-08-03 13:42:11 UTC
The missing strings are now in the .pot file provided by Transifex, so we can considered the bug fixed.


Note You need to log in before you can comment on or make changes to this bug.