Bug 724860

Summary:	copyTrans needlessly processes the languages that is missing from zanata.xml
Product:	[Retired] Zanata	Reporter:	Ding-Yi Chen <dchen>
Component:	Component-Logic	Assignee:	zanata-dev-internal <zanata-dev-internal>
Status:	CLOSED NOTABUG	QA Contact:	Ding-Yi Chen <dchen>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.3	CC:	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-01-27 02:00:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ding-Yi Chen 2011-07-22 04:07:12 UTC

Description of problem:
It seems that copyTrans processes all the enabled languages in Zanata server. 
However, it is not all that efficient if zanata.xml only consist a small subset of this.


Version-Release number of selected component (if applicable):
Zanata version 1.4-SNAPSHOT (20110722-0601). 

How reproducible:
Always

Steps to Reproduce:
0. Assume a document project, and version are created.
1. Add af, de, fr, jp, kr in Administration -> Manage languages 
2. Use only one language, af,  in zanata.xml
3. Use python client to push: zanata po push --import-po
  
Actual results:
af, de, fr, jp, kr are all processed.

Expected results:
Only af is needed.

Comment 1 Sean Flanigan 2011-09-07 04:33:16 UTC

Assigning to Scrum product owner for prioritisation.

Comment 2 Sean Flanigan 2012-01-27 02:00:02 UTC

CopyTrans actually processes all locales which are valid for the project/iteration in question.  In some cases, this is the same as the global server locale list, but not always.

See bug 785031 for a possible feature to synchronise the server locale lists with the local zanata.xml list.