Fix multi-line i18n strings #1704
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anvit
added
the
Type: bug
|
@jraddaoui No problem! To be honest it wasn't as bad as I thought it was going to be, because when I'd ran a pattern-match search, I found over 700 results 😅, but a lot of those turned out to be SQL statements that were split up, CLI exceptions, and other such results that don't affect the user. |
Join i18n strings that have been split into multiple lines to have them be recognized as a single unit for translations.
anvit
force-pushed
the
dev/issue-split-translator-strings
branch
from
ca13903
to
6cb1412
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Join i18n strings that have been split into multiple lines to have them be recognized as a single unit for translations.