-
The core team does not see it as their responsibility - see angular/angular/issues/37655 and angular/angular-cli/issues/6552. There existed some tooling @ngx-i18nsupport on which the community relied on, but sadly this is unmaintained and broken (and probably too complex for "fork and repair"...).
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
The core team does not see it as their responsibility - see angular/angular/issues/37655 and angular/angular-cli/issues/6552. There existed some tooling @ngx-i18nsupport on which the community relied on, but sadly this is unmaintained and broken (and probably too complex for "fork and repair"...).
-
The core team does not see it as their responsibility - see angular/angular/issues/37655 and angular/angular-cli/issues/6552. There existed some tooling @ngx-i18nsupport on which the community relied on, but sadly this is unmaintained and broken (and probably too complex for "fork and repair"...).
-
I wrote two small tools, that solve the i18n merge problem: xliff-simple-merge and xml_normalize.
-
xml_normalize
Normalizes xml files. Options include sorting siblings based on provided attribute, remove nodes, normalize whitespace/trim and pretty print.
I wrote two small tools, that solve the i18n merge problem: xliff-simple-merge and xml_normalize.
-
If you (as the developer) do the translations yourself, you might find a more integrated solution, like angular-t9n, better.
