© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Ok, so the plan to fix this is:
All translation imports (using web or .po uploads) will be modified so:
- if the translation has '\r\n' but the msgid does not have it, we will remove the '\r' from the translation.
- if the translation has '\n' and the msgid has '\r\n' the translation will have too '\r\n'.
- if the msgid and the translation has '\r\n' nothing will be changed.
Also, when a new .pot is imported, if any msgid has a '\r' char we will warn the uploader because we think is better if the source strings has only '\n' chars as the translator does not have a way to easily see or understand it.