New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i18n xlf alt-trans tag is used instead of target #33161
Labels
Milestone
Comments
crtl
changed the title
xlf alt-trans tag is used instead of target
i18n xlf alt-trans tag is used instead of target
Oct 15, 2019
@crtl can you confirm that this is with ivy disabled? |
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Oct 28, 2019
The parser was accidentally reading the `target` tag below the `alt-trans` target and overriding the correct `target` tag. (This already worked in `$localize` but a test has been added to confirm.) Fixes angular#33161
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Oct 28, 2019
The parser was accidentally reading the `target` tag below the `alt-trans` target and overriding the correct `target` tag. (This already worked in `$localize` but a test has been added to confirm.) Fixes angular#33161
#33450 will fix this. |
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Oct 29, 2019
The parser was accidentally reading the `target` tag below the `alt-trans` target and overriding the correct `target` tag. (This already worked in `$localize` but a test has been added to confirm.) Fixes angular#33161
petebacondarwin
added a commit
to petebacondarwin/angular
that referenced
this issue
Oct 29, 2019
The parser was accidentally reading the `target` tag below the `alt-trans` target and overriding the correct `target` tag. Fixes angular#33161
matsko
pushed a commit
to matsko/angular
that referenced
this issue
Oct 30, 2019
…3450) The parser was accidentally reading the `target` tag below the `alt-trans` target and overriding the correct `target` tag. (This already worked in `$localize` but a test has been added to confirm.) Fixes angular#33161 PR Close angular#33450
mohaxspb
pushed a commit
to mohaxspb/angular
that referenced
this issue
Nov 7, 2019
…3450) The parser was accidentally reading the `target` tag below the `alt-trans` target and overriding the correct `target` tag. (This already worked in `$localize` but a test has been added to confirm.) Fixes angular#33161 PR Close angular#33450
mohaxspb
pushed a commit
to mohaxspb/angular
that referenced
this issue
Nov 7, 2019
…3450) The parser was accidentally reading the `target` tag below the `alt-trans` target and overriding the correct `target` tag. (This already worked in `$localize` but a test has been added to confirm.) Fixes angular#33161 PR Close angular#33450
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🐞 bug report
Affected Package
@angular/i18n
Description
After extracting the translations as xlf files and editing them in my translation tool angular cannot use the translations correctly anymore. The translation tool adds tags inside the document which angular then reads instead of the actual translation.
In the following example angular displays
Content
(trans-unit > alt-trans > target) instead ofWeiter
(trans-unit > target)🔬 Minimal Reproduction
🌍 Your Environment
Angular Version:
Anything else relevant?
Swordfish III used for translations.
The text was updated successfully, but these errors were encountered: