Bug 694720

Summary:	Clients should use MIME-Version/Content-Type/Content-Transfer-Encoding
Product:	[Retired] Zanata	Reporter:	Sean Flanigan <sflaniga>
Component:	Component-Maven	Assignee:	Runa Bhattacharjee <runab>
Status:	CLOSED DUPLICATE	QA Contact:	zanata-dev-internal <zanata-dev-internal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	ankit, 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-02-13 01:28:49 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:
Bug Depends On:
Bug Blocks:	786670

Description Sean Flanigan 2011-04-08 06:34:46 UTC

The Java and Python clients currently assume that all POT/PO files are in UTF-8, ignoring the header fields MIME-Version/Content-Type/Content-Transfer-Encoding.  

These fields should be used to select the correct character encoding when reading POT/PO files.  Also, when generating POT/PO files, we should specify a reasonable value.  I think it's okay to output UTF-8 in all cases, as long as we put the correct encoding into the header.

We should at least check for unsupported encodings when reading, and generate sensible headers when writing.

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

Assigning to Scrum product owner for prioritisation.

Comment 2 Sean Flanigan 2012-02-13 01:28:49 UTC


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