Prevent translators from using \r\n

Bug #560652 reported by Jens Beyer
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

It is possible for the translators to use \r\n in translations.
This causes warnings by gettext utilities and (in case of widelands project) program errors (making the translated language unusable).

I accept that it is a warning severity, not an error, so it might be unwise to reject translations using \r\n completely.

But it would really be great if the great Launchpad services for translations would give us a way to handle those, from the widelands point of view, illegal translations; e.g. reject the translation with a meaningful error message, or at least a functionality for the project owner to find those easily in Launchpad.

Thanks for the good work :-)

Revision history for this message
Jens Beyer (qcumber-some) wrote :

I've just seen that there is also the Launchpad Translations project ("rosetta"). I was not able to find that from the help documents, they just linked to this project.
Sorry for any inconvenience.

William Grant (wgrant)
affects: launchpad → rosetta
Revision history for this message
Данило Шеган (danilo) wrote :

Unless msgid is using \r\n, we shouldn't allow it in the translation either. There are a few related bugs with \r handling, such as bug 88831, bug 61112, bug 61096 and bug 30358.

Changed in rosetta:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers