ARB Serializer -> missing "meaning" on extracted translation files

[meriturva]

🐞 bug report

Is this a regression?

No, ARB file format is new on Angular 11.1

Description

We would like to support ARB format for our component translations files (to avoid the use of XML parser library to handle xliff files: xml2js or cheerio). After update our solution to Angular 11.1 we are now testing ARB extraction format but what we have noted is that there is no more meaning information extracted:

"71788121164220023": "no tags found",
  "@71788121164220023": {
    "description": "No tags found placeholder",
    "x-locations": [
      {
        "file": "projects\\xxxxx\\hardware-editors\\src\\lib\\elements\\channelEditor.component.html",
        "start": { "line": "70", "column": "25" },
        "end": { "line": "70", "column": "38" }
      }
    ]
  },

Why not to use Customized Attribute on ARB format (as ready did with x-location) and add an x-meaning property?

For example:

"71788121164220023": "no tags found",
  "@71788121164220023": {
    "description": "No tags found placeholder",
    "x-meaning": "My meaning",
    "x-locations": [
      {
        "file": "projects\\xxxxx\\hardware-editors\\src\\lib\\elements\\channelEditor.component.html",
        "start": { "line": "70", "column": "25" },
        "end": { "line": "70", "column": "38" }
      }
    ]
  },

[petebacondarwin]

That is a reasonable request. Would you be interested in providing a PR to add this?

[meriturva]

So thanks @petebacondarwin for that opportunity! We use now the meaning to split translations and place them in the correct library resource folder (we are also waiting for new APF format based on Ivy). Due to the missing meaning information on ARB format, we are testing now to run extraction tool on all single library and see performance on CI.

So if we really need x-meaning property I guess we could arrange a PR.
Keep in touch and thanks again!

[meriturva]

So thanks @crisbeto !

[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.}