pt_BR translation broke Python syntax highlighting

[LKRaider]

Binary package hint: gedit

Using the pt_BR gedit, the Python syntax highlighting is broken for non-multiline strings (as in -> "String" will not be highlighted).

The problem is the translation of the following terms are equal:
Multiline Double Quoted String == Double Quoted String == Texto entre aspas duplas
Multiline Single Quoted String == Single Quoted String == Texto entre aspas simples

Changing the file python.lang so that these terms are not translated fixes the issue.

[Sebastien Bacher (seb128)]

Thank you for your bug. What version of Ubuntu do you use?

[Og Maciel (ogmaciel)]

I have checked the upstream versions of gEdit for both 2.18 and 2.20 branches and wasn't able to find said strings. Am checking Ubuntu's version now...

Are you sure this is a gEdit issue?

Cheers,

Og

[Sebastien Bacher (seb128)]

it's like gtksourceview or gtksourceview2, depending of the version of Ubuntu

[Og Maciel (ogmaciel)]

Confirmed for gtksourceview from upstream. I'll work on it today and will correct Ubuntu's version as well. Thanks Sebastien! :)

[Og Maciel (ogmaciel)]

This was a bug with the translation of the gtksourceview package (thanks Sebastien for pointing it out). I have fixed the translation in Ubuntu for the time being but the fix will also be sent to GNOME's bugzilla either today or tomorrow.

[Daniel M. Basso (dmbasso)]

As a work around, it is possible to just remove the translation file at:
/usr/share/locale-langpack/pt_BR/LC_MESSAGES/gtksourceview-1.0.mo

Worked without warnings, and those translations weren't really necessary (for me, at least).

[Og Maciel (ogmaciel)]

Your work around would prevent Brazilian Portuguese people from getting information in pt_BR... :)

[Og Maciel (ogmaciel)]

These strings don't exist anymore in upstream gtksourceview and have already been released.

[Daniel M. Basso (dmbasso)]

Og Maciel escreveu:
> Your work around would prevent Brazilian Portuguese people from getting
> information in pt_BR... :)
>
>
Apenas o nome das tags para o highlight, o que, como eu disse, não é
muito relevante. No meu código, por exemplo, muito mais importante que
ter a tradução dos nomes das tags (que não apareciam em lugar algum) era
que o syntax highlight funcionasse.

[]'s

Daniel