Bug 870873

Summary:	RFE: A translator should be able push po files for non-po file projects
Product:	[Retired] Zanata	Reporter:	Ding-Yi Chen <dchen>
Component:	Component-Persistence	Assignee:	Runa Bhattacharjee <runab>
Status:	CLOSED DUPLICATE	QA Contact:	Ding-Yi Chen <dchen>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	development	CC:	ankit, damason, sflaniga, 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-11-13 07:28:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ding-Yi Chen 2012-10-29 05:05:13 UTC

Description of problem:
Zanata provides "Download as po", however, if translators do download the translation this way and do the off-line translation, they won't be able to push it back if the project does not use po files.

A translator should be able push po files for non-po file projects.


Version-Release number of selected component (if applicable):
Zanata version 2.0.1-SNAPSHOT (20121029-1430

How reproducible:
Always

Steps to Reproduce:
1. Push a non-po file project, such as a properties, utf8properties or xliff projects. 
2. Download a document as a po file.
3. Upload that po file
  
Actual results:
File Constants.po uploaded. There were some warnings, see below. 
 Could not find TextFlow for TextFlowTarget 2fd5df9452801bcc015367756752a895 with contents: [] 
  .... and so on ...

Expected results:
Push successfully.

Additional info:

Comment 1 Sean Flanigan 2012-11-07 06:01:37 UTC

Isn't this a duplicate of bug 870876?

Comment 2 David Mason 2012-11-13 07:28:20 UTC

Closing as duplicate.

*** This bug has been marked as a duplicate of bug 870876 ***