JSON files not converting tags

Question

Hello, 
 There are some similar discussions in the Community, but they haven't helped me with this issue. 
 I have a bunch of JSON files where the tags appear as regular text. This is throwing off my TM matches. I have all this text already translated, but the client needs it in JSON files now. 
 I have downloaded the latest plugin, but that didn't change anything. In their documentation I only saw Studio 2019, but I'm running Studio 2021. I wonder if that has anything to do with my problem. Here's a screenshot of what I see: 
 
 I'd appreciate any help. This is a big project, it'll be a nightmare to have to look up each segment in my TM. 
 
 M&oacute;nica

Paul · Answer

Monica de Leon 
 Have you set up the embedded content options in Trados Studio 2021 for the JSON filetype? It seem as though this is simply a configuration problem. If you can share the file, or part of it, it would be helpful as we could test and suggest a solution.

Paul · Answer

Monica de Leon Thanks for emailing me the file. The problem you are having is indeed related to not having set the embedded content. It is a little different with JSON because the settings are not made particularly easy to work with. You have to do a couple of things, first of all you have this: Because the only way to specify the use of the embedded content parser is to specify to rules to use you need to change the option to "Specify rules for extracting" and then add the rules you need. For this you then need to know a little about JSON XPath as it's different to the way XPath works in XML. A reasonable reference site is this one: https://goessner.net/articles/JsonPath/ I just created two rules, one to extract all the text from the title key and another to extract all the text from the text key. If you need more you add as needed. The syntax for my expressions being simply: $..title $..text I also gave them some structure (Document Structure Information) by setting then as "Paragraph". For example: Once I have my rules I then switch to the "Embedded Content" node of the settings and configure it like this: So I'm just telling it to apply the embedded content processor I'm selecting here to the parser rules that have the "Paragraph" document structure information. And I chose to use the HTML Embedded Content Processor because this is easy for the file you provided. This presents the file cleanly. However, there does seem to be a horrible bug with this and it does things like this in places: What's possibly worse is this even increases the wordcount by a considerable margin. Not sure if Patrik Mazanek is aware of this one? So, as a workaround I changed the embedded parser and used this one instead: And I created one simple catch all rule in the embedded parser I selected to test it like this: Opening: <[^/>]+?> Closing: ]+?> Then I get this: Which is much better and seems quite workable. Hopefully that helps?

Paul · Answer

Monica de Leon 
 Monica de Leon said: I am using my own project template, the one I use for all my projects. 
 You said earlier you had to use the single document approach, so this would not be using your project template. It will use the default template under Tools -> Options. Maybe make sure you applied this filetype there to test it? 
 Monica de Leon said: And also, I just updated it, and I again have the same problem. The program refuses to open. When I click on the Trados Studio 2021 icon, it opens the initial window for a second, but then it disappears and the program refuses to open. 
 I suggest you do the following: 
 
 upgrade to CU8 
 delete the plugins folders completely c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\ c:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\16\Plugins\ c:\ProgramData\SDL\SDL Trados Studio\16\Plugins\ 
 
 Restart. Then make sure you take the latest apps from the appstore only by downloading via the integrated appstore.

Trados Studio > 1. Trados Studio

JSON files not converting tags