chore: Use raw string encoding to prevent AI translation errors #2794
+57
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Crowdin AI pre-translation has issues when using
\n
characters in strings, and it regularly replaces them with new line breaks (which are stripped away in non-raw strings and thus never appear in the app).Using raw strings for new lines fixes it, because even if the AI gets confused and uses the wrong new line encoding, with raw strings it still works because both regular line breaks and
\n
are valid and work as intended.Raw strings are also easier to edit on Crowdin because multiline text is shown and edited as multiline (and not a single line with
\n
sprinkled throughout).