Bug 985836 - dates in PO files should be in "%Y-%m-%d %H:%M%z" format
Summary: dates in PO files should be in "%Y-%m-%d %H:%M%z" format
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 3.2
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-18 10:58 UTC by Raphaël Hertzog
Modified: 2013-08-09 04:47 UTC (History)
4 users (show)

Fixed In Version: 3.2.0
Clone Of:
Environment:
Last Closed: 2013-08-09 04:47:28 UTC
Embargoed:

Attachments (Terms of Use)
Suggested patch (352 bytes, text/plain)
2013-07-18 10:58 UTC, Raphaël Hertzog 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Debian BTS 714739 0 None None None Never

Description Raphaël Hertzog 2013-07-18 10:58:08 UTC 
Created attachment 775251 [details]
Suggested patch

(I'm filing this bug on behalf of Jakub Wilk <jwilk> who filed it at http://bugs.debian.org/714739)

publican generates PO files with dates like this:

POT-Creation-Date: 2012-07-29T20:56:34

This is a different format than GNU gettext tools use, e.g.:

POT-Creation-Date: 2013-07-02 12:57+0200

It would be better to follow the GNU convention here too. I'm attaching Jakub's suggested and untested patch.
Comment 2 HSS Product Manager 2013-07-18 22:37:32 UTC 
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.
Comment 3 Jeff Fearn 🐞 2013-07-18 22:52:59 UTC 
$ grep POT-Creation-Date pot/Book_Info.pot
"POT-Creation-Date: 2013-07-19 08:51+1000\n"

To ssh://git.fedorahosted.org/git/publican.git
   cc28d75..2d9e256  HEAD -> devel
Comment 4 Scott Radvan 2013-07-19 00:24:18 UTC 
pot date now follows GNU format, eg:

"POT-Creation-Date: 2013-07-19 10:20+1000\n"

verified with publican-3.1.5-0.fc19.t61.noarch
Comment 5 Jeff Fearn 🐞 2013-08-09 04:47:28 UTC 
The fix for this bug has been shipped in publican 3.2.0
Note You need to log in before you can comment on or make changes to this bug.