[publican-list] [Bug 678186] New: update_po produces inconsistent results

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: update_po produces inconsistent results

https://bugzilla.redhat.com/show_bug.cgi?id=678186

           Summary: update_po produces inconsistent results
           Product: Publican
           Version: 2.5
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: publican
        AssignedTo: jfearn at redhat.com
        ReportedBy: r.landmann at redhat.com
         QAContact: rlandman at redhat.com
                CC: mmcallis at redhat.com, publican-list at redhat.com
    Classification: Other


Created attachment 479256
  --> https://bugzilla.redhat.com/attachment.cgi?id=479256
example XML file

Description of problem:

Publican sometimes includes lines in msgid entries in PO files that contain
nothing but two sets of quote marks. This happens when the corresponding XML
file includes a <screen> element with a carriage return before the closing tag.
For example:

<screen>
rhnpush --server=http://localhost/APP -c 'rhel-5.3-beta' -d
/var/satellite/custom-distro/rhel-i386-server-5.3-beta/Server/
</screen>

is represented in the PO file as:

#. Tag: screen
#, no-c-format
msgid "\n"
"rhnpush --server=http://localhost/APP -c 'rhel-5.3-beta' -d
/var/satellite/custom-distro/rhel-i386-server-5.3-beta/Server/\n"
""
msgstr ""

If Publican updates a PO file with an msgid that matches except for the extra
line, Publican doesn't add this line. For example, update_po does not change
this entry:

#. Tag: screen
#, no-c-format
msgid "\n"
"rhnpush --server=http://localhost/APP -c 'rhel-5.3-beta' -d
/var/satellite/custom-distro/rhel-i386-server-5.3-beta/Server/\n"
msgstr ""

We have examples of books where PO files lack these lines for reasons that are
unclear.

These lines aren't a problem in themselves, but Publican also counts each of
these lines as a word when you run publican lang_stats -- which means that the
word count for different languages might be different. 

This doesn't impact on translation directly, but can make life interesting for
anyone managing a translation project; the word counts that lang_stats produces
serve as a crude but handy checksum to make sure that all members of a
translation team are working on up-to-date PO files. When different languages
report different word counts, it's not immediately obvious that everyone's
translating the same thing :)

Version-Release number of selected component (if applicable):
2.5-1

How reproducible:
100%

Steps to Reproduce:
1. generate a PO file from an XML file that includes a <screen> element with
its closing tag on a new line
2. run lang_stats on the target language and note the result
3. edit the PO file to remove any lines in msgid entries that consist only of
'""' 
4. run lang_stats on the target language and note the result
5. run publican update_po to refresh the PO file
6. open the PO file to note that the '""' lines are not restored
7. run lang_stats on the PO file yet again and note the result

Actual results:
results in steps 4 and 7 are the same, but differ from result in step 2

Expected results:
same results in steps 2, 4, and 7

Additional info:

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.