Skip to content

ng-xi18n should generate same IDs when using xlf or xmb format #15136

@martinroob

Description

@martinroob

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
Using the same template with some i18n markup text.
I try to extract the messages file with ng-xi18n.
I can use formats xlf or xmb with the --i18n-format xmb flag.
But in the generated messages.xlf and messages.xmb the units for the same input texts have totally different IDs.

Expected behavior
The generated IDs should only be a function of input text, description and intent, they should not depend on the output format.

Minimal reproduction of the problem with instructions

(see above)

What is the motivation / use case for changing the behavior?
I try to buld some tooling for i18n, especially something like a translation memory.

Therefore it is important, to have format independent IDs.

Please tell us about your environment:

  • Angular version: 2.0.X
  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
  • Language: [all | TypeScript X.X | ES6/7 | ES5]

  • Node (for AoT issues): node --version =

Metadata

Metadata

Assignees

No one assigned

    Labels

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

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions