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

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?

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?

Hi Philip Sundt

I am not able to answer your question without seeing structure of your JSON files. From your screenshot, slug is always a sibling of content. Does slug appear in any other structure? If not, two expressions makes no difference.

Naoko, all files are structured as the file in the screenshot. "Slug" does not appear in any other structure. However, please note that I am referring to "content" that is the parent of "slug". I know it's slightly confusing that there is also a sibling to "slug" called "content". In other words, I need to translate all the values of the parent called "content", but I need to distinguish "slug" from the other children of "content", since "slug" will be considered partly as a non-translatable.

I found this very helpful website where I could try different paths http://jsonpath.com/ . It seems that $..slug and $..content.slug does the same thing. 

And with the answer you gave me before, I could set "slug" as a LBL and thus distinguish it from the other content. 

Thank you so much!