Description of problem: A comment on the bottom of entry in the po file will result in failing to push po to server.Both python and maven client have this issue. Po files should be able to be pushed to server regardless wherever comments go Version-Release number of selected component (if applicable): 1.6.0-alpha-3-SNAPSHOT How reproducible: always Steps to Reproduce: 1.put a comment in the end of a entry in a po file ex: msgid " source text" msgstr " translation text " # a comment in the end resulting in failure to push po 2. push this po file using zanata push --push-trans Actual results: po being pushed to server Expected results: error: Syntax error in po file /home/jochang/test/ibus-chewing/po/zh_TW.po (line 25) additional info. same issue happens when pushing pot
Actually, pot is still able to be pushed to server, with a comment in the end of an entry. sorry~~
(In reply to comment #2) i managed to reproduce the bug precisely, i realized whether po or pot, a comment in the end of the file will result in failing to be pushed to server like what Runa said( Bug 822344 ).So, it did happened to pot as well, when pushing it, with a comment in the end
See http://l10n.gnome.org/POT/gdm.master/gdm.master.bn_IN.po for another file which breaks polib, and thus zanata-python-client. In this case, it seems to be a "previous msgid" which is a problem: #~| msgid "AT SPI Registry Wrapper
Hi, I have commit a patch to polib to fix this issue, which is accepted by owner of polib. Please see the patch and issues description: https://bitbucket.org/izi/polib/pull-request/5/ignore-obsolete-previous-msgid-entries https://bitbucket.org/izi/polib/issue/28/ioerror-on-reading-obsolete-previous-msgid So i think we need to build a new release for python-polib.
VERIFIED with 1.8.0-SNAPSHOT (20120827-0014) zanata-python-client-1.3.11, python-polib-1.0.0