You signed in with another tab or window.Reloadto refresh your session.You signed out in another tab or window.Reloadto refresh your session.You switched accounts on another tab or window.Reloadto refresh your session.Dismiss alert
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
In the XLF file generated by extract-i18n, there are sometimes incorrect values inside the "equiv-text" attributes of the interpolation elements. In these cases, "equiv-text" does contain parts of the surrounding text (sometimes including other HTML elements). It seems that the issue occurs when the interpolation element is located directly at the beginning of the translation unit (so a linebreak inside the HTML element fixes the output, see example below).
I am also experiencing this behaviour. in both, an angular v18 project.
As well as an angular v15 project (which is scheduled for upgrade later this year)
Command
extract-i18n
Is this a regression?
The previous version in which this bug was not present was
No response
Description
In the XLF file generated by extract-i18n, there are sometimes incorrect values inside the "equiv-text" attributes of the interpolation elements. In these cases, "equiv-text" does contain parts of the surrounding text (sometimes including other HTML elements). It seems that the issue occurs when the interpolation element is located directly at the beginning of the translation unit (so a linebreak inside the HTML element fixes the output, see example below).
Minimal Reproduction
This example leads to the expected output:
HTML template:
XLF generated by extract-i18n (using builder @angular-devkit/build-angular:extract-i18n):
This example produces incorrect content in "equiv-text":
HTML template:
XLF generated by extract-i18n (using builder @angular-devkit/build-angular:extract-i18n):
Exception or Error
No response
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: