Bug#897449: django-allauth: Invalid character reference 138 in "Last Translator" field in some .po files (Bug#881727 reappeared when uploading 0.35 version)

Le 4 mai 2018 20:05:52 GMT+02:00, Laura Arjona Reina a écrit : >Hello again >I have sent a Pull Request (#2017) to the upstream project fixing the >string of the translator name: >https://github.com/pennersr/django-allauth/pull/2017 > >Cheers I referenced the issue I opened

Bug#897449: django-allauth: Invalid character reference 138 in "Last Translator" field in some .po files (Bug#881727 reappeared when uploading 0.35 version)

Hello again I have sent a Pull Request (#2017) to the upstream project fixing the string of the translator name: https://github.com/pennersr/django-allauth/pull/2017 Cheers -- Laura Arjona Reina https://wiki.debian.org/LauraArjona

Bug#897449: django-allauth: Invalid character reference 138 in "Last Translator" field in some .po files (Bug#881727 reappeared when uploading 0.35 version)

Hello Pierre-Elliot El 04/05/18 a las 13:52, Pierre-Elliott Bécue escribió: > So, I wonder, maybe this error is triggered because the *source* actually > still contains this wrongfully encoded character? But theoretically I'm not > supposed to alter upstream's source. > Yes, that seems to be the

Bug#897449: django-allauth: Invalid character reference 138 in "Last Translator" field in some .po files (Bug#881727 reappeared when uploading 0.35 version)

Le mercredi 02 mai 2018 à 21:20:53+0200, Laura Arjona Reina a écrit : > Package: django-allauth > Severity: wishlist > Tags: patch l10n upstream > > Dear Maintainer, > > When uploading the 0.35 version, the bug Bug#881727 reappeared again: > > Some of the upstream .po files, in the "Last

Bug#897449: django-allauth: Invalid character reference 138 in "Last Translator" field in some .po files (Bug#881727 reappeared when uploading 0.35 version)

Package: django-allauth Severity: wishlist Tags: patch l10n upstream Dear Maintainer, When uploading the 0.35 version, the bug Bug#881727 reappeared again: Some of the upstream .po files, in the "Last translator" field, include a name of translator with a bad encoded character (numeric