Bug 698028

Summary:	Support .po file as a source for software translation projects
Product:	[Retired] Zanata	Reporter:	Sean Flanigan <sflaniga>
Component:	Component-PythonClient	Assignee:	James Ni <jni>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ding-Yi Chen <dchen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	jni, zanata-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-04 02:57: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:

Description Sean Flanigan 2011-04-20 01:20:01 UTC

Some software projects may name the POT file as if it were a PO file, because the default output of the xgettext command is messages.po.  We should handle this.

Some examples: http://www.google.com/codesearch?hl=en&lr=&q=file%3A^.*%2Fmessages.po%24&sbtn=Search

Comment 1 Ding-Yi Chen 2011-04-20 04:09:20 UTC

FYI. http://www.gnu.org/s/hello/manual/gettext/Template.html#Template

Comment 2 James Ni 2011-04-21 07:22:12 UTC

I have add a command line option named --srcfile, for software projects may name the POT file as a PO file, you could use this option as below:

1)zanata po push --srcfile="path to po file"

2)You could also make the PO file name as a command arguments and specify the source folder for looking up:
zanata po push "pofilename" --srcdir="path to folder contain po file"

the changes is in commit d52f339 and commit 300de0d, please use commit d52f339 of devel branch of zanataclient on github for test.

Best Regards