intltool

Failure to understand C strings

Bug #964785 reported by Mwelinder
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
intltool
Triaged
High
Unassigned

Bug Description

intltool 0.50.2 fails "make check" for goffice and gnumeric because it thinks
some generated files contain translations. A small sample that shows the
failure is this:

static const char data4[] =
    """"
    """_"
;

Revision history for this message
Mwelinder (mwelinder) wrote :

Origin: https://bugzilla.gnome.org/show_bug.cgi?id=672771

Данило Шеган (danilo)
Changed in intltool:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Данило Шеган (danilo) wrote :

The complication with this is that "intltool-update -m" needs to understand multiple languages. The changes that probably "broke" this for C were those that improved Python string support (which was very flaky beforehand), especially the triple quoted strings. So, now intltool-update reads this as

"""{quote}{newline}{spaces}"""
_"

and the final bits triggers a "translatable string found" (this is used in .scm [scheme, or at least a variant used in "Dr Geo" if I remember correctly] support which we could consider doing away with).

Revision history for this message
Mwelinder (mwelinder) wrote :

It would seem that tokenizing needs to be language dependent.

(I'm actually surprised that you have gotten past the wildly different
comment syntaxes in use without having stuff be language dependent.
Or maybe some parts already are.)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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