[zanata-bugs] [Bug 740122] New: Zanata does not seem to handle \n well on round trips

[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: Zanata does not seem to handle \n well on round trips

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

           Summary: Zanata does not seem to handle \n well on round trips
           Product: Zanata
           Version: unspecified
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: Usability
        AssignedTo: runab at redhat.com
        ReportedBy: bkearney at redhat.com
         QAContact: dchen at redhat.com
                CC: zanata-bugs at redhat.com
   Estimated Hours: 0.0
    Classification: Community
      Story Points: ---
              Type: ---


When importing translations from zanata, the following msgfmt errors are
encountered.

for lang in as bn de en es fr gu hi it ja kn ko ml mr or pa pt pt_BR ru ta te
zh_CN zh_TW ; do \
  echo $lang ; \
  mkdir -p po/build/$lang/LC_MESSAGES/ ; \
  msgfmt -c --statistics -o po/build/$lang/LC_MESSAGES/rhsm.mo po/$lang.po ; \
 done
as
po/as.po:54: `msgid' and `msgstr' entries do not both end with '\n'
po/as.po:724: `msgid' and `msgstr' entries do not both end with '\n'
po/as.po:758: `msgid' and `msgstr' entries do not both end with '\n'

Per a discussion on IRC, it seems that the \n is not preserved and shown to the
translator. This causes inadvertent mis-translations.

IRC transcript is below:

(09:22:32 PM) Hedda: sflanigan: bryan_kearney1: The problem might be that
Zanata doesn't show the translators those \n in the original message - so we
don't know that we actually need to add one of those to our translation, too. 
Validation checks will then complain if not both messages end in \n.
(09:22:33 PM) bryan_kearney1:
http://git.fedorahosted.org/git/?p=subscription-manager.git
(09:22:43 PM) bryan_kearney1: sflanigan: you can see the commit and revert
(09:23:03 PM) bryan_kearney1: Hedda: as a nOOb, that seems like a critical
issue
(09:23:19 PM) Hedda: it is indeed - one I only just found out about
(09:23:25 PM) sflanigan: Would something like that break msgfmt though?
(09:23:53 PM) bryan_kearney1: sflanigan: that is what those errors are
(09:24:05 PM) sflanigan: Oh, I see. right
(09:24:52 PM) Hedda: same issue just broke my build of a documentation... the
translation had \n inserted into tags, which I didn't see on Zanata.
(09:24:59 PM) Hedda: only publican complained later
(09:26:59 PM) Hedda: so yeah, sflanigan, this is actually a very important new
issue :-(
(09:27:02 PM) CIA-82 left the room (quit: Ping timeout: 260 seconds).
(09:27:26 PM) bryan_kearney1: how does this get raised.. I am waiting on
translations to fix bugs.. but can not use exports from zanata.
(09:27:27 PM) sflanigan: Yes
(09:27:44 PM) CIA-82 [~CIA at cia.atheme.org] entered the room.
(09:29:31 PM) jni [~jni at 203.114.244.88] entered the room.
(09:32:23 PM) bryan_kearney1: sflanigan: do I raise a bug? Cry wolf? something
else?
(09:33:11 PM) Hedda: bryan_kearney1: I think mospina is already working on
it... that's what he just told me
(09:33:15 PM) sflanigan: Raise a zanata bug, but it's going to take a while to
do anything from that side of things.  We'll have to find a way of fixing the
.po files and pushing them back to zanata

-- 
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.