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
Support ICU message for xliff #12636
Comments
ping @vicb |
This is good point no doubt. My concern is overall state of i18n. It has to be carefully designed to work nicely with rich template syntax as well as AOT compilation and localization formats. |
I've been looking into that, the biggest challenge is to find a format to serialize ICU messages into XLIFF, knowing that this format should be compatible with translation tools. I did some research which is documented here: https://docs.google.com/document/d/1FS02wIBSEbysCoxEqbEmJg3_LyfJ566DZLhhbOUheoA/edit?usp=sharing Feedback is more than welcome :) |
@panuruj Based on your work on XLIFF 2.0 support, I can imagine that you are a heavy XLIFF user and we could use your expertise to solve this issue :) Would you use ICU messages if they were available for XLIFF? Would you recommend one of the format I've documented above? If you don't mind, it would be also interesting to understand how you handle plural cases in your applications. |
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. |
I'm submitting a ... (check one with "x")
Current behavior
Using something like
<div i18n id="i18n-7">{count, plural, =0 {zero} =1 {one} =2 {two} other {<b>many</b>}}</div>
in the case ofother
it printsmany
.Expected behavior
it should print
<b>many</b>
. It is omitting the html part.Minimal reproduction of the problem with instructions
http://plnkr.co/edit/ucuVZuhU67Ul64ViUSa8?p=preview
What is the motivation / use case for changing the behavior?
It is a bug :)
Chrome
Language: Typescript
Node (for AoT issues):
node --version
=The text was updated successfully, but these errors were encountered: