(See #38711 (comment) for original report)
Extraction of i18n messages from the following template HTML:
<ng-container i18n="Update @@update"> <b>{{value1}}:</b> current {{value2}} to new {{value3}} </ng-container>Without ivy: (ctype attributes removed for clarity)
<source>
<x id="START_BOLD_TEXT" equiv-text="<b>"/>
<x id="INTERPOLATION" equiv-text="{{value1}}"/>:
<x id="CLOSE_BOLD_TEXT" equiv-text="</b>"/> current
<x id="INTERPOLATION_1" equiv-text="{{value2}}"/> to new
<x id="INTERPOLATION_2" equiv-text="{{value3}}"/>
</source>With ivy:
<source>
<x id="START_BOLD_TEXT" equiv-text="<b>{{value1}}"/>
<x id="INTERPOLATION" equiv-text="{{value1}}"/>:
<x id="CLOSE_BOLD_TEXT" equiv-text="</b> "/> current
<x id="INTERPOLATION_1" equiv-text="{value2}} "/> to new
<x id="INTERPOLATION_2" equiv-text="{value3}} "/>
</source>It seems that there is some offsetting going on, which is making the start and end points in the equiv-text appear in the wrong place. I'll need to debug into this but since these equiv-text attributes are primarily to aid the translator's job, it will not be high on my priority list. Hopefully I can take a look at it later next week or the week after.
(See #38711 (comment) for original report)
Extraction of i18n messages from the following template HTML:
Without ivy: (ctype attributes removed for clarity)
With ivy:
It seems that there is some offsetting going on, which is making the start and end points in the equiv-text appear in the wrong place. I'll need to debug into this but since these equiv-text attributes are primarily to aid the translator's job, it will not be high on my priority list. Hopefully I can take a look at it later next week or the week after.