Bug 885934

Summary: RFE: option to avoid encoding tab as \t
Product: [Retired] Zanata Reporter: Sean Flanigan <sflaniga>
Component: Component-MavenAssignee: Sean Flanigan <sflaniga>
Status: CLOSED CURRENTRELEASE QA Contact: Ding-Yi Chen <dchen>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: zanata-bugs
Target Milestone: ---   
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.1-SNAPSHOT (20121214-0032) Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-27 07:57:43 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:

Description Sean Flanigan 2012-12-11 04:01:54 UTC
Description of problem:

Publican doesn't like it when a PO file uses \t in msgids for a string which is a tab in the original DocBook XML.  We should add an option to avoid encoding tab as \t, and just use tab characters.  The default will still be to encode tabs, because this is how the Gettext tools behave (eg msgmerge, msgcat).

Version-Release number of selected component (if applicable):
2.0.2-SNAPSHOT

How reproducible:
100%

Steps to Reproduce:
1. Push a POT file containing tab characters into Zanata
2. Pull a PO file from Zanata
3. Observe the representation of the tab characters in the PO's msgid and msgstr fields.
  

Additional info:

The new option (in Maven's "pull" goal) will be -Dzanata.encodeTabs, which will default to true.  If the option -Dzanata.encodeTabs=false is provided, tabs should be as-is.

Comment 2 Ding-Yi Chen 2012-12-14 08:03:18 UTC
VERIFIED with Zanata version 2.1-SNAPSHOT (20121214-0032)
[INFO] client API version: 2.0.0, server API version: 2.0.1