Properties getting removed from source file when requested via content api

1

Hi in one of our projects we are using the chrome i18n format file.

But for some properties we enhance it with some additional data like

"BookmarkBrowserPriceRange": {
    "message": "from $MINPRICE$",
    "description": "Label when min and max price differs",
    "placeholders": {
      "minprice": {
        "content": "$1"
      }
    }
  }

When I try to later pull the source file via the content api /resource/${resourceSlug}/content these additional properties are removed. Is there a way to retain what we upload to transifex?

2

It would be great if someone from the transifex team answered this

3

Hi @blessanm86,

Thank you for your question.

This is an issue that is related to an old version of our parser (version #1). In October, we released a new version of the Chrome i18n parser where the issue you described is no longer present.

This means that:
–> any newly created resources will be parsed by the new parser by default ensuring that i18n placeholders are preserved upon export.
–> any existing TX resources are not being affected and that’s why the issue still exists. We highly recommend migrating from the old to the new version taking full advantage of this new enhancement. In order to do that, you need to re-create the resource (re-upload the source file as a new resource in Transifex allowing TM to automatically translate any previously submitted translations).

More information about the way this new handler parses and compiles your content can be found in our documentation guide here.

Please let me know if you need any additional information.

1 Like