"Bad markup found in translations" ('make check' failure with autotools)

Bug #1586292 reported by su_v
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Medium
jazzynico

Bug Description

Recent translation updates cause 'make check' (with autotools-based build) to fail - since Inkscape trunk PPA builds have already switched to cmake, and the cmake test routines do not include tests for po or extensions, this error might have gone unnoticed:

<...>
Making check in po
rm -f missing notexist
srcdir=. /Volumes/magenta/mp-trunk/x11/bin/intltool-update -m
if [ -r missing -o -r notexist ]; then \
   exit 1; \
 fi
nl.po: parsing error for `<Program files>':
#: ../share/extensions/plotter.py:151
msgid " into the following Inkscape folder: C:\\<Program files>\\inkscape\\python\\Lib\\"
msgstr ""

WARNING: Bad markup found in translations. Please consider fixing the above problems.
make check_markup
perl ./po/check-markup ./po/*.po || [ $? = 127 ]
nl.po: parsing error for `<Program files>':
#: ../share/extensions/plotter.py:151
msgid " into the following Inkscape folder: C:\\<Program files>\\inkscape\\python\\Lib\\"
msgstr ""

make[2]: *** [check_markup] Error 1
make[1]: *** [check-am] Error 2
make: *** [check-recursive] Error 1

The unescaped '<' and '>' are in inkscape.pot as well as in nl.po (as of rev 14919). I don't known whether this needs to be fixed in the source file itself (plotter.py) or whether the characters should have been escaped automatically in inkscape.pot on re-generation?

Tags: i18n
su_v (suv-lp)
description: updated
Revision history for this message
jazzynico (jazzynico) wrote :

Confirmed. The error comes from the inkscape.pot file.
Investigations in progress.

Changed in inkscape:
assignee: nobody → jazzynico (jazzynico)
importance: Undecided → Medium
milestone: none → 0.92
status: New → In Progress
Revision history for this message
jazzynico (jazzynico) wrote :

Fixed rev. 14922.

Changed in inkscape:
milestone: 0.92 → none
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.