Bug 524188

Summary: Outdated POT file in Repository
Product: [Fedora] Fedora Reporter: Ankit Patel <ankit>
Component: system-config-clusterAssignee: Jim Parsons <jparsons>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: rawhideCC: jparsons, mclasen, piotrdrag, t.chrzczonowicz, tomspur
Target Milestone: ---Keywords: Translation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-21 14:11:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 525052    

Description Ankit Patel 2009-09-18 09:57:29 UTC 
Filed this bug on behalf of FLP based on the following report sent by Tomek on Fedora localization mailing list.

=====
Hello,

While reviewing translations for system-config-cluster (from l10n livecd 2009-09-17 and Transifex .po/.pot files) I noticed that there are many strings in system-config-cluster that are not in .pot file, so they can't be translated.

Actually, it seems like the most of the application has no .pot entries.

.pot files from Transifex and CVS have "POT-Creation-Date: 2005-09-02 15:53-0400\n"

It looks like the .pot file is seriously outdated.

Can you please look into this?

The translation deadline is 2009-09-22. It would be great to be able to
deliver a complete and polished translation for Fedora 12.

Regards,

Tomek Chrzczonowicz
Polish L10n Team member
=====
Comment 1 Tomasz Chrzczonowicz 2009-09-18 12:21:29 UTC 
https://www.redhat.com/archives/fedora-trans-list/2009-September/msg00118.html

Won't fix?
Comment 2 Piotr Drąg 2009-09-21 14:11:12 UTC 
Clearly WONTFIX, see https://www.redhat.com/archives/fedora-trans-list/2009-September/msg00118.html
Comment 3 Piotr Drąg 2009-09-21 14:12:57 UTC 
*** Bug 466828 has been marked as a duplicate of this bug. ***