You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One feature I am missing is the auto-merging of trans-units with the same text into one trans-unit.
While ng extract-i18n manage to generate only one trans-unit for all occurences of the same text in templates, it is not doing the same if one occurence come from the $localize function.
However, manually merging those trans-unit in the translated .xlf files seems to work.
I guess that if no custom ID, description or meaning has been defined for both trans-units with the same source text, it should be auto-merged.
The text was updated successfully, but these errors were encountered:
Hello,
First of all thanks for your work, I started using this tool since https://github.com/martinroob/ngx-i18nsupport is no longer maintened and it works like a charm.
One feature I am missing is the auto-merging of trans-units with the same text into one trans-unit.
While
ng extract-i18n
manage to generate only one trans-unit for all occurences of the same text in templates, it is not doing the same if one occurence come from the $localize function.However, manually merging those trans-unit in the translated .xlf files seems to work.
I guess that if no custom ID, description or meaning has been defined for both trans-units with the same source text, it should be auto-merged.
The text was updated successfully, but these errors were encountered: