[i18n] Current state & pain points · Issue #20193 · angular/angular · GitHub
Skip to content

[i18n] Current state & pain points #20193

Description

@ocombe

Hello everyone, I'd like to start a discussion on the current state of i18n in Angular.
Our goal is to make it as easy to use as possible, but we are aware that we still have some work to do on that.
I think that the main two issues right now are:

  • having one bundle for all locales instead of one bundle/locale
  • being able to use translations in your code (not just templates)

The first point is being addressed right now with what we call "runtime translations". And it's actually the first step for the second point which will be our main focus once runtime translations are done.

What we'd like to know if what else we can do to make it easier to use? Any feedback is appreciated.

You can find the list of things that we're working on or that we have planed here: #16477

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: i18nIssues related to localization and internationalization

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions