Bernadette Haury 

We actually don't have the updated version as Supertext have not provided it to us.  So we cannot test or suggest how you might be able to handle this.

Hi Paul ,

I've downloaded the latest version from their blog article https://blog.supertext.ch/en/2016/05/json-file-type-for-trados/. I didn't know it either, but as the plugin I was using in 2021 wasn't working anymore in 2022, I downloaded it again from the site and I got the updated version: https://blog.supertext.ch/wp-content/uploads/sdltradosplugins/json/2.0/Supertext.Sdl.Trados.FileType.JsonFile.sdlplugin

Thank you

Bernadette Haury 

First of all, thank you for pointing this all out to me.  I have missed this filetype... it's a lot better than the out of the box filetype in Studio for anyone who doesn't need to work in the cloud as well with complete alignment between the tools.  I'm happy to say it's now back on the appstore so available to all users again and also via the integrated appstore in Trados Studio.

Now, on your problem.  The first thing to note is that you need to make sure that the rule for the <br/> tag is correctly set up to exclude.  So this rule should be set up like this, after enabling the embedded content processor:

Then, based on a monolingual file like this:

{
  "politics": {
    "state": "The current state of politics is highly volatile.",
    "state": "Numerous issues such as <br/> economic instability, <br/> social unrest, and geopolitical tensions dominate the discourse."
  }
}

Will open in Studio like this:

However, if you have a bilingual file it will not:

{
  "politics": {
    "state": {
      "en": "The current state of politics is highly volatile.",
      "fr": "L'état actuel de la politique est très volatile."
    },
    "state": {
      "en": "Numerous issues such as <br/> economic instability, <br/> social unrest, and geopolitical tensions dominate the discourse.",
      "fr": "De nombreuses questions telles que <br/> l'instabilité économique, <br/> l'agitation sociale et les tensions géopolitiques dominent le discours."
    }
  }
}

In this case the file will open like this:

This is most likely because the developer cannot second guess the user that there are equal number of breaks in the source and target, so to manage this each JSON property will always be a single segment.

Hope that helps?

Bernadette Haury 

First of all, thank you for pointing this all out to me.  I have missed this filetype... it's a lot better than the out of the box filetype in Studio for anyone who doesn't need to work in the cloud as well with complete alignment between the tools.  I'm happy to say it's now back on the appstore so available to all users again and also via the integrated appstore in Trados Studio.

Now, on your problem.  The first thing to note is that you need to make sure that the rule for the <br/> tag is correctly set up to exclude.  So this rule should be set up like this, after enabling the embedded content processor:

Then, based on a monolingual file like this:

{
  "politics": {
    "state": "The current state of politics is highly volatile.",
    "state": "Numerous issues such as <br/> economic instability, <br/> social unrest, and geopolitical tensions dominate the discourse."
  }
}

Will open in Studio like this:

However, if you have a bilingual file it will not:

{
  "politics": {
    "state": {
      "en": "The current state of politics is highly volatile.",
      "fr": "L'état actuel de la politique est très volatile."
    },
    "state": {
      "en": "Numerous issues such as <br/> economic instability, <br/> social unrest, and geopolitical tensions dominate the discourse.",
      "fr": "De nombreuses questions telles que <br/> l'instabilité économique, <br/> l'agitation sociale et les tensions géopolitiques dominent le discours."
    }
  }
}

In this case the file will open like this:

This is most likely because the developer cannot second guess the user that there are equal number of breaks in the source and target, so to manage this each JSON property will always be a single segment.

Hope that helps?

Hi Paul,

First of all thanks a lot for your reply and help.

I could finally correct the br tag settings and Trados 2022 displays the correct segmentation as it did in 2021.

Excellent... thanks for confirming Bernadette Haury 

Hi Paul  One more question, as Trados 2024 has been released, will this File Type Definition for JSON by Supertext AG also be compatible with Trados 2024? Currently, it seems I cannot install it in 2024, it's not available when I'm searching for it in 2024, and on the app store website, it says it's for 2022 only.

Many thanks again!

Bernadette Haury 

Bernadette Haury said:

Currently, it seems I cannot install it in 2024, it's not available when I'm searching for it in 2024, and on the app store website, it says it's for 2022 only.

Only when the developer updates it to support 2024.