Repository navigation
Open
Labels
P4A relatively minor issue that is not relevant to core functionsA relatively minor issue that is not relevant to core functionsarea: docsRelated to the documentationRelated to the documentationarea: i18nIssues related to localization and internationalizationIssues related to localization and internationalizationfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under considerationfreq2: mediumhotlist: error messages
Milestone
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Feature request
[x] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
When I try to use ICU syntax in a translated attribute (like placeholder) I get an error:
Template parse errors: Unexpected translation for attribute "placeholder" (id="...
Expected behavior
Either a) nothing fails, everything works! or b) Fail more gracefully telling me this is not supported and make a note of this in the documentation.
Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/angular-xafhzk?file=app/autocomplete-overview-example.html
https://angular-xafhzk.stackblitz.io
<input placeholder="{foo, select, bar{a} baz{b} other{c}}" i18n-placeholder>What is the motivation / use case for changing the behavior?
i'm forced to do this in different ways, like goog.getMsg. I'd like not to do this and have a consistent way of doing stuff.
Environment
Angular version: 5.2.1
Reacted by Julian Ruhe, Aleksei Lebedev, Dave, Kyle Li, Trotyl Yu, n00dl3, Sergey Fetiskin, Martin Parenteau, David Wheeler, Alexander and 19 more
Metadata
Metadata
Assignees
Labels
P4A relatively minor issue that is not relevant to core functionsA relatively minor issue that is not relevant to core functionsarea: docsRelated to the documentationRelated to the documentationarea: i18nIssues related to localization and internationalizationIssues related to localization and internationalizationfeatureLabel used to distinguish feature request from other issuesLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under considerationFeature request for which voting has completed and the request is now under considerationfreq2: mediumhotlist: error messages
Activity
vicb commentedon Jan 18, 2018
@Goodwine This feature is not supported in the current i18n implementation. Leaving this open so that we:
JalmariO commentedon Jul 3, 2019
I'm using dynamic components for form and placeholders vary.
Is this feature coming in a near future. I mean ICU for properties?
Or is there alternative way of localizing properties?
@ocombe
ocombe commentedon Jul 3, 2019
We have a ticket tracking this, but it hasn't been prioritized, so no it's not coming in the near future...
You can localize properties, but you can't use ICU expressions
1 remaining item
angular-robot commentedon Jun 4, 2021
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.
wartab commentedon Sep 16, 2025
Would PRs addressing this (ICU not working, not addressing the parse error) be welcome or would you rather want to fix this yourselves? :)