Red Hat Bugzilla – Bug 702549
shouldn't add "#, fuzzy" to gettext header
Last modified: 2013-03-03 21:21:16 EST
Description of problem:
mvn client should preserve PO file Meta data correctly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.mvn zanata:publican-push -Dzanata.importPo
2.mvn zanata:publican-pull -Dzanata.dstDir=.
PO file Meta data changed
PO file Meta data preserved correctly
please see the attachments
One is original PO file
The other one is the PO file which is pulled from server.
Created attachment 497291 [details]
Created attachment 497292 [details]
the PO file which is pulled from server
If a text flow is exported, then imported with the same content, a new revision is being created, when in fact the revision shouldn't change. The new revision has no translator credit because it was imported.
Dean, would you please see if you can reproduce this?
Having clarified with Helen, the specific bug being reported is:
1. "#, fuzzy" was added to header comment
2. "Test:Zanata" in the header was changed to "Test: Zanata\n"
1. is a mostly cosmetic bug which we should get around to fixing.
2. is okay, because Zanata normalises the name-value pairs in the header (space after colon, newline at end).
Also, we should avoid adding blank "#:" entries to messages.
Bug reproduced and confirmed with:
Zanata version 1.4-SNAPSHOT (20110712-0601).
Client: maven client API timestamp is 20110623-1549
Assigning to Scrum product owner for prioritisation.
VERIFIED with Zanata maven client API timestamp is 20120217-1255, but server API timestamp is 20120217-1456