Bug 711249 - Import should skip over obsolete translations
Summary: Import should skip over obsolete translations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Logic
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: James Ni
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 00:26 UTC by Sean Flanigan
Modified: 2011-10-28 07:25 UTC (History)
1 user (show)

Fixed In Version: 1.4
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-10-28 07:25:20 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 712281 0 unspecified CLOSED REST interface should accept TextFlowTargets in any order 2021-02-22 00:41:40 UTC

Internal Links: 712281

Description Sean Flanigan 2011-06-07 00:26:57 UTC 
When importing a PO file containing msgids which don't appear in the POT, the server currently rejects the entire file.

error: Unexpected target: 8fae3ebb2c1d08ded523938133b96fcc

The user is supposed to run msgmerge before importing the PO file, which comments out the obsolete messages and thus avoids the error when importing.  But if we change the server to skip over these obsolete messages with a warning, the user would not need to run msgmerge.

NB: the same problem will probably occur with XLIFF and .properties, but they don't even come with a tool like msgmerge.
Comment 1 Sean Flanigan 2011-06-16 08:03:24 UTC 
This has been implemented on the server (should be in 1.4).  The Java client will output a warning if returned by the server.

James, could you please update the Python client to do the same?
Comment 2 James Ni 2011-09-29 08:43:08 UTC 
This feature is implemented in python client. please check the latest version 1.3.0 and 1.3.1
Comment 3 Ding-Yi Chen 2011-10-04 02:09:42 UTC 
VERIFIED with Zanata version 1.4.1-SNAPSHOT (20111003-1737)
Python client 1.3.1
maven client 1.4.1-SNAPSHOT
Note You need to log in before you can comment on or make changes to this bug.