-
Notifications
You must be signed in to change notification settings - Fork 26.2k
Allow linebreaks in i18n translations #27809
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
Comments
@AndrewKushnir do you know if it's possible in ivy with runtime i18n to add a line break to a translation with something like |
@ocombe One can just apply |
yes, I just wanted to make sure that they weren't striped or anything |
Yep, they're also stripped by default as if being the original source code, so |
As @trotyl mentioned, the combination of ngPreserveWhitespaces and white-space CSS rule should help achieve the necessary result. Thank you. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🚀 feature request
Description
This problem already was discussed here: #25242
But it was closed without resolving it. Also, @vicb in #23053 wrote:
so, I have to open new ticket for this.
Translations for different languages could have different length.
In some cases original english phrase nicely fits in one line, but german translation could be much longer, so for site design it will be better to break it to 2 lines after specific word. But it is not possible :(
If I add "
<ph name="LINE_BREAK"><ex><br></ex></ph>
" - build will throw "parse errors: Unexpected tag"If I add "
<br>
" or "<br>
" - it will add escaped version of tag.Describe the solution you'd like
Allow
<br>
tags in translations. Maybe also<b>
and<i>
tags.<i>
tag - because in some translations we should italicize foreign words and phrases https://intelligentediting.com/blog/how-to-decide-if-you-should-italicize-foreign-words-and-phrases/The text was updated successfully, but these errors were encountered: