[i18n] future 2.x plan

Features planned for 2.0:

fix issues:

xmb/xtb support [Feature][i18n] .xmb/.xtb support #9067
do not extract empty msgs [i18n] do not extract message when there is not child nodes #8802
allow escaping ICU messages - [i18n] escaping in ICU message #9286
fix markup for plural/gender [i18n] {messages.length, plural, ...} should not be expanded to a list #9072 (PR feat(I18N Expander): do not add extra <ul> & <li> around ICU mess… #9283)
improve the extractor [i18n]: add support for implicit translation #9071 (PR feat(I18nExtractor): Add file paths to error messages #9177)
fix ICU format [i18n] ICU format for plural #9094 (fixed in 5267115)

fix post 2.0:

Template Parser: Error when passing object literal as pipe parameter. False-Positive: Parser Error: Missing expected } at the end of the expression #9571
Improve Html Parser Html Parser improvements #9340
Opt out of translation I18n: Opting out of translation #7814
Provide NgLocalization implementation per locale
ICU plural format [i18n] ICU plural format - support # and offset #9117
allow ICU messages in attributes
implement ICU ordinal messages
use translation strings outside of a template i18n: Able to use translation strings outside a template #11405

@vicb

@vicb I have seen a few postings about i18n in the angular repo. How does this relate to https://github.com/angular/i18n? Is this a new initiative?

@thelgevold

@thelgevold like most things in ng2, the standalone repos existed for early prototyping. major work is typically done inside of this one.

Hi, there's any document about how it will work?
I'm wondering if I can write keys in markup and normal text in translation files like I'm using with angular-translate.

{{ 'HOMEPAGE__ACTION__SIGNUP' | translate }}

Coding like this, one external person can edit all supported languages (since they reside in JSON/po file, one file per language). If the main language is in the markup, it blocks all revisions until a developer can change the string in the markup code.

Thanks!

@marcalj

@marcalj The (outdated) spec is https://docs.google.com/document/d/1mwyOFsAD-bPoXTk3Hthq0CAcGXCUw-BtTJMR4nGTY-0/edit.

Your use case is supported.

Thanks Victor! Any plans to include number abbreviations? It's something i18n context aware.

@marcalj

@marcalj could you please create a separate issue with more details ? Thanks (but probably not for 2.0 anyways)

Is or will there be support for dynamic translations (loaded from a server)?
Any plans to document i18n in the near future?
Thanks!

The current plan is to generate a binary per locale.

We will work on the doc as the features become available. We should definitely have a minimal doc for the 2.0 release.

What do you mean by "binary per locale". Is the deployed resource file going to be binary little bit like PO/MO where MO is used insted of PO to improve performance. There are also bad examples in binary deployment such as XAML/BAML.

I am not very happy to the current Anguar localization methods. These are the reasons:

Several different APIs and methods.
You have to modify your templates so much from original that templates become hard to read and maintain.
You have to manually update the original resource file and make sure it is in sync with the IDs used in the template

What we really need is

One single official localization method with solid resource format (XML or JSON based)
Minimal affect to templates. For example only add "localize" attribute into root element and possible "noloc" attributes into those elements that are not localized.
Ability to add localization comments to the strings in the templates.
A tool that scans source code extracting orignal strings and comments into resource file. Use as permanent ids as possible. For example use id attributes or if such is not provided use combination of location and original string value.
This resource file should be able to store plain strings, strings with patterns ({{...}}), pluralized strings and gender strings little bit like Android's value files.
Easy way to package localized resources and to download them as needed
Ability to change language without reload.

I am ready to help if you guys need some help.

@jaska45

@jaska45 most your wishes should come true. One exception: "Ability to change language without reload.". Changing a language will imply bootstrapping a new app.

Thanks. Sound very good. Language change is something that occurs seldom and in that case it is acceptable that some state is lost. Definetely lowest priority in my list and not worth spending too much efforts.

@vicb

@vicb I'm not sure if I understand this "binary per locale" correctly, but would that mean, that it's not possible to add translations at runtime? We are currently building SAAS with tenant support, where each tenant can extend our system by providing their own set of Form-Definitions and their own set of translations, so in our case it would be really important to be able to add translations at runtime.

circle.yml

Create .cla%3A%20yes

@Thomas-Kuipers

@Thomas-Kuipers @thelgevold I'm working on it, and it will be available in 4.1 or 4.2 (most likely)

@ocombe

@ocombe
how to deal with static text in interpolation, which can't use select translation.

<div i18n>{{exercise._desc ? exercise._desc : 'empty'}}</div>

string 'empty' can't be translate

@rayer4u

@rayer4u this is not the subject of this issue, for support questions you should use stackoverflow or gitter.
I'll answer this one anyway, but don't ask further questions here that are unrelated to i18n future plans please.

The answer is: you can't do it, dynamic translations are not supported by Angular i18n since it works at compile or build time, and not at runtime.

@rayer4u

Off Topic: I Apologize
@rayer4u The solution is to use static translations:

<div *ngIf="exercise?._desc">{{ exercise?._desc }}</div>
<div *ngIf="!exercise?._desc" i18n>empty</div>

@ocombe

@ocombe I Apologize for off Topic, no need to reply. I just have this need and can't find any quick way to discuss it. I think this may be concerned by angular i18n plan. As Angular i18n plan don't deal with interpolation, a extra mark/find/replace is better build time i18n solution for me right now.
@martinmcwhorter Thanks for your reply. We write a lot mixed if/else logic to output diffrent i18n text in template, this is the easiest one. Maybe put runtime text logic in template is a bad choice.

maybe this is bad idea but can't angular add automatically @@id in our i18n attributes when we extract first time ?

No because we would have to maintain this when you edit the code.
Let's say that you have two blocks of i18n code that are the same, we add the ids, and then you change one of them, the ids don't match which means that the next extraction will skip on of those...

@ocombe

I confirm it's bad idea, can you explain how angular know to attribut same id to string when we extract again and again, how they keep same ID on string. so powerful but I don't undersand :s

@ocombe

This is what we use: https://github.com/angular/angular/blob/master/packages/compiler/src/i18n/digest.ts#L13-L15

We are now at v4 so I'm closing this issue, please follow up in #16477 for our plans for v4 and beyond.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

Navigation Menu

Repository navigation

[i18n] future 2.x plan #9104

101 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[i18n] future 2.x plan #9104

Description

Activity

thelgevold commented on Jun 9, 2016

robwormald commented on Jun 9, 2016

marcalj commented on Jun 10, 2016

vicb commented on Jun 10, 2016

marcalj commented on Jun 11, 2016

vicb commented on Jun 16, 2016

dagerber commented on Jun 24, 2016

vicb commented on Jun 24, 2016

jaska45 commented on Jul 1, 2016

vicb commented on Jul 1, 2016

jaska45 commented on Jul 1, 2016

choeller commented on Jul 4, 2016

101 remaining items

ocombe commented on Mar 16, 2017

rayer4u commented on Mar 21, 2017

ocombe commented on Mar 21, 2017

martinmcwhorter commented on Mar 21, 2017

rayer4u commented on Mar 22, 2017

elvisbegovic commented on Mar 29, 2017

ocombe commented on Mar 29, 2017

elvisbegovic commented on Mar 29, 2017

ocombe commented on Mar 29, 2017

ocombe commented on May 2, 2017

angular-automatic-lock-bot commented on Sep 11, 2019

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions