Bug 885934 - RFE: option to avoid encoding tab as \t
Summary: RFE: option to avoid encoding tab as \t
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Maven
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2.1
Assignee: Sean Flanigan
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-11 04:01 UTC by Sean Flanigan
Modified: 2013-02-27 07:57 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-02-27 07:57:43 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 879441 None None None Never

Internal Trackers: 879441

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


Note You need to log in before you can comment on or make changes to this bug.