JanneHarju

@SimonNodel-AI funny coincident. I have exactly same scenario with you. Almost every library that I have, only have template translations which can be handled by **ng xi18n** but in one...

another idea. should that feature to implement within this tool or should it be done separately. I found that this could be used https://www.npmjs.com/package/xliff . Just read two parameters in,...

Now I found your earlier discussion in another issue. There is already this https://github.com/jaroslavsvak/xlf-merge

my final solution was to use locl tool https://www.npmjs.com/package/@locl/cli . So First I generate project --localize=false then I run normal ng xi18n for html side translations. Then I run locl...

> @ocombe > You could include short migration guide: > > ``` > $localize:`meaning|description@@id:message` > ``` > > 1. Replace all occurrences with the new syntax: > > * You...

@DanielHabenicht and @ocombe I have made node script which handle most of the cases to convert every ts file in specific folder to new format. It removes I18n import It...

Code block didn't work because there is backticks in code. So sorry for bad format. And On more assumption for this is that interpolated variable has same name as variable...

Sorry there was one bug in replace part of every this.i18n part. I was missing : character. I will update it. And FYI github changed my `` in my answer...

That was new feature for me. Thanks. Here it is. It assume that you have named I18n by i18n. In my case some has used i18 for some reason. ANd...

Maybe if you but that plural syntax what @DanielHabenicht suggest to html and then build application with --localize=false I think every i18n html translations are converted to use $localize in...