René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[i18n] enable control over translation message ID ","articleBody":"**I'm submitting a ...**  (check one with \"x\")\r\n```\r\n [ ] bug report =\u003e search github for a similar issue or PR before submitting\r\n [x] feature request\r\n [ ] support request =\u003e Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question\r\n```\r\n\r\n**Current behavior**\r\nCurrently the traduction ID is created by hashing the node content and the traduction \"meaning\" value. e.g: : \r\n\r\nfor this html fragment : \r\n```html\r\n\u003cp i18n=\"vehicule|personal vehicule\"\u003ethe  car\u003c/p\u003e\r\n```\r\nthe traduction ID will be a hash of `the  car[vehicule]`\r\n\r\nFixing any typo in the html tag content (*in this example removing the two spaces between \"the\" and \"car\"*) will create a new ID for translation. So I will have to change the ID for each XLIFF | XTB files despite the fact that I don't know the ID because it's a hash.\r\n\r\n**Expected behavior**\r\nIt would be very useful to have an option to disable the message ID generation to only use the \"meaning\" value as the translation ID.\r\n\r\nFor example, we can have an option in the ng-xi18n script to disable hashing : \r\n```bash\r\n./node_modules/.bin/ng-xi18n --i18nFormat=xlf --meaningAsId\r\n```\r\nAnd add a new provider in the app : \r\n```js \r\nplatformBrowserDynamic().bootstrapModule(AppModule, {[\r\n    {provide : TRANSLATIONS, useValue : translationFile},\r\n    {provide : TRANSLATIONS_FORMAT, useValue : 'xlf'},\r\n    {provide : LOCALE_ID, useValue : 'fr'},\r\n    {provide : MESSAGE_ID, useValue : 'meaning'}\r\n]});\r\n```\r\n\r\n**What is the motivation / use case for changing the behavior?**\r\nThis feature will avoid the fact that each minimal changes in the \"original content\" (without affecting the meaning of a word or sentence) will produce a crash of the app because the message ID changes for the `HTML_parser`. In other words, if the developper adds a meaning in the i18n attribute, he must have the choice to change the translation (by changing its ID) or not.\r\n\r\nCurrently, it's impossible to change something in the original content without fixing the ID for every translation files.\r\n\r\n* **Angular version:** 2.1.0\r\n\r\n* **Browser:** all\r\n \r\n* **Language:** TypeScript 2.0.2\r\n\r\n* **Node (for AoT issues):** `node --version` =   4.4.1\r\n","author":{"url":"https://github.com/maxime-allex","@type":"Person","name":"maxime-allex"},"datePublished":"2016-11-17T14:30:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/12941/angular/issues/12941"}