-
-
Notifications
You must be signed in to change notification settings - Fork 959
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android format: Weblate incorrectly uses CR characters instead of "\n" for newlines [$15 awarded] #359
Comments
What Weblate and translate-toolkit versions are you using? |
|
Apostrophes ( |
Hmm, this sounds strange - these were already fixed and are covered by testsuite (inside translate-toolkit). Have you made manual changes to any of Weblate or translate-toolkit? |
I have not made any changes. Would it help if I created an account for you on my server, or if I sent sample files? |
I've opened a bounty on this issue, hopefully this will help speed up the resolution (despite the rather small amount, sorry)… |
I've tested this with today released 1.7 and I don't see neither of problems:
So to me it looks like it was fixed. Please let me know if there is still something broken with 1.7. |
It does seem to work, thank you! |
When updating a string that contains newlines, Weblate merely uses CR characters rather than the "\n" characters required by Android.
Since Android ignores the CR characters, strings are displayed without newlines in the resulting application.
The text was updated successfully, but these errors were encountered: