Bug 694720 - Clients should use MIME-Version/Content-Type/Content-Transfer-Encoding
Summary: Clients should use MIME-Version/Content-Type/Content-Transfer-Encoding
Keywords:
Status: CLOSED DUPLICATE of bug 748727
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Maven
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Runa Bhattacharjee
QA Contact: zanata-dev-internal
URL:
Whiteboard:
Depends On:
Blocks: zanata-1.5.0
TreeView+ depends on / blocked
 
Reported: 2011-04-08 06:34 UTC by Sean Flanigan
Modified: 2013-03-04 02:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-13 01:28:49 UTC
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.