Bug 490019 - Ensure that your POT and PO files are up-to date
Summary: Ensure that your POT and PO files are up-to date
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-nfs
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 490056
TreeView+ depends on / blocked
 
Reported: 2009-03-12 21:00 UTC by Xavier Conde
Modified: 2009-03-25 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-13 13:02:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Xavier Conde 2009-03-12 21:00:50 UTC 
Hi,

I'm opening this bug on behalf of the FLP team as a reminder for you to ensure that your POT and PO files are up-to date and ready to be translated. Remember that deadline for translators is Apr 7th.

Your current POT and PO files have the following values, at least for Catalan PO:

"POT-Creation-Date: 2008-07-15 16:35+0200\n"
"PO-Revision-Date: 2008-09-20 00:11+0100\n"

Please ensure that your POT file contains the latest strings and PO files have been merged accordingly.

Many thanks in advance and best regards!
Comment 1 Nils Philippsen 2009-03-13 13:02:06 UTC 
Ran "make update-po" and pushed to git.fedorahosted.org.
Comment 2 Noriko Mizumoto 2009-03-25 08:04:07 UTC 
It seems files downloaded via new Tx have not been updated yet.

https://translate.fedoraproject.org/tx/projects/system-config-nfs/master/
https://translate.fedoraproject.org/tx/projects/system-config-nfs/master/view/po/ja.po
14 "POT-Creation-Date: 2008-07-15 16:35+0200\n"
15 "PO-Revision-Date: 2008-09-09 22:55+1000\n"
16 "Last-Translator: Noriko Mizumoto <noriko>\n"
17 "Language-Team: Japanese <fedora-trans-ja>\n"
Comment 3 Nils Philippsen 2009-03-25 10:02:48 UTC 
This is because no strings have been added/changed since that date.
Comment 4 Noriko Mizumoto 2009-03-25 20:27:50 UTC 
Thank you for clarification!
Note You need to log in before you can comment on or make changes to this bug.