If you are using Studio 2019, load the Supertext json file type from the appstore and import the rules in there. Then decide, which you need. This is the easiest way to deal with your problem.

Jerzy, thank you.

I am using Studio 2021. I am using the Trados native JSON parser and I have never tried an app for this. I will download the app and see.

I'm not sure, however, that I understand what you mean by "import the rules in there". How would I go about this? "$..content.*" is not an expression that I created, so I am not exactly fluent in the language "Parse". Do you have an idea of how these rules would look?

Unfortunately, the native json file type does not support this feature.

If you still have S2019, install the file type File Type Definition for JSON - Language Solutions | SDL there, then use "Extract" to extract the rules from your file(s), remove unwanted ones and prepare the project there. You can afterwards translate in S2021, but will need to create target in S2019.

The process is very easy and self-explaining.

I never had S2019 as I bought the program recently.
Does this mean I won't be able to do this?

Autsch, unfortunately for the time being not. The Supertext file type is not (yet) available for S2021. In that very case you will be forced to writhe the paths on your own, unless someone here in the forum is able to give you the paths (I am not). Other solution would be having someone with Studio 2019 preparing the files for you. This is something I could imagine to be able to do. So if you wish, write an e-mail to info at tts-td dot com and give me exact information which elements need translation. I would then prepare a dummy package (with an empty TM—to be replaced by proper TM at your end) for you.

Hi Philip Sundt

Actually, you can achieve this starting with Studio 2021 SR1 CU3. So be sure you are upgraded at least to CU3.

 As a new feature of CU3, Translatable checkbox was added in the Add JSON Path dialog.

Below, you can see each JSONPath with Translatable attribute set, and it works.

Adding to my original post here, also you can make sure DSI is set something specific to slug so that you can filter for slug entries in Editor or add color to DSI column so it's easily recognizable without filtering. DSI viewer from AppStore is also great.

I hope this helps.

Thanks,

Naoko

Thank you so much, Naoko!

I tried to create one path "$..content.*" and one "$..slug". I set the DSI of the slug to Label, and I can now successfully see all slugs as "LBL" in the editor! Absolutely amazing! Thank you!

I would like to set a specific color to the DSI "LBL". If possible, how would I go about this? I looked under Options -> Colors but cannot find anything there.

A side-question: To me, it doesn't exactly make sense that "$..slug" would match anything indented one level under "content". If "content" is found with "$..content", wouldn't then the reasonable path for the slug be "$...slug" (3 dots instead of 2) since it's one "level" below content?

Jerzy, I got a good answer from Naoko which allows me to solve this issue directly in S2021. Again, thank you for your great help!

Hi Philip Sundt

Sorry about the color for the DSI, In terms of JSON parser, you are stuck with what they have and colors are not customizable. The colors of DSI columns are customizable in other parsers such as XML. I have yellow/custard color for LBL. 

In terms of .. (two dots), this is equivalent to // in XPath. You can find a mapping between XPath and JSONPath here. It is helpful when you know one of those to understand the other.

goessner.net/.../

Thank you for explaining and for that link. So with the information from that link in mind, I wonder if the better option to reach the slug is "$..content.slug" or "$..slug". Would you recommend any over the other or would I get the same result?