-
Notifications
You must be signed in to change notification settings - Fork 26.2k
fix(compiler): fix support for html-like text in translatable attributes #23053
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
Conversation
You can preview 61bec75 at https://pr23053-61bec75.ngbuilds.io/. |
Hi, since i upgraded to 5.2.10 i have an issue with my translations. Shouldn't the content of translation be escaped for attribute translation only ? and not for regular translation (i18n attribute) ? |
have you tried with |
I have an 'xliff parse errors' if i use |
i have the same thing as @antid0te since 5.2.10 :-( |
@antid0te @aviaur could you please create a new issue with a detailed description of the current behavior vs the expected behavior ? We don't monitor close PRs nor issues - I only got here because @ocombe pointed me to your question. AFAIU you are trying to add html to a translated message which is not a supported use case. |
Ok, can you point me to the right way of adding a line break to a translated message ? |
i18n translations could only be composed from tags that are present in the source message. Again difficult to help more with no concrete use case. |
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. |
<tag i18n-attr attr="<some>tags</some>">...</tag>
was not supported before.(use case: material as a tooltip that get html content from an attribute)