Skip to content

[i18n] ICU plural format - support # and offset #9117

Closed

Description

@vicb

We currently do not support offset nor #

ICU:

    "{num_guests, plural, offset:1 "
      "=0 {{host} does not give a party.}"
      "=1 {{host} invites {guest} to her party.}"
      "=2 {{host} invites {guest} and one other person to her party.}"
      "other {{host} invites {guest} and # other people to her party.}}}"

While this is not strictly required because we can use angular expression, it would be nicer for translators.

For # we need:

Activity

  1. added
    featureLabel used to distinguish feature request from other issues
    area: i18nIssues related to localization and internationalization
    on Jun 9, 2016
  2. changed the title [-][i18n] ICU plural format[/-] [+][i18n] ICU plural format - support `#` and `offset`[/+] on Aug 4, 2016
  3. added this to the Backlog milestone on Jan 23, 2018
  4. timofei-iatsenko commented on Feb 4, 2019

    @timofei-iatsenko

    Moreover current interpolation syntax in ICU breaks support of ICU in most of the translation tools.

    For example ICU from docs:

    {VAR_PLURAL, plural, =0 {just now} =1 {one minute ago} other {<x id="INTERPOLATION" equiv-text="{{minutes}}"/> minutes ago} }
    

    Put it to commonly used ICU validator: https://format-message.github.io/icu-message-format-for-translators/editor.html

    ICU supprot tools usually don't understand < symbol inside ICU, and if understand they become completele broken when they rich }} inside interpolation tag.

    This forces users to search for tool wich is Angular-aware which greatly reduces the choice (i actually didn't find any) or just give up to full ICU syntax and edit it as simple string.

  5. ValentinFunk commented on Oct 20, 2019

    @ValentinFunk

    This would be incredibly nice to have, currently translation tool support for angular is not very good and this would help a lot. It's also a lot nicer to write and read in templates.

    Additionally when you look at ICU guides they very often mention the # shortcut and it was a bit suprising to me that this didn't work in Angular.

  6. added a commit that references this issue on Nov 2, 2020
  7. angular-robot commented on May 21, 2021

    @angular-robot
    Contributor

    Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

    Find more details about Angular's feature request process in our documentation.

  8. angular-robot commented on Jun 10, 2021

    @angular-robot
    Contributor

    Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

    We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

    You can find more details about the feature request process in our documentation.

  9. angular-automatic-lock-bot commented on Jul 11, 2021

    @angular-automatic-lock-bot

    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.

  10. locked and limited conversation to collaborators on Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: i18nIssues related to localization and internationalizationeffort1: hoursfeatureLabel used to distinguish feature request from other issues

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions