I'm afraid you would need to preprocess the JSON first using some script which encapsulates the variables into a custom tags, which would be then defined as non-translatable.
And you would need to postprocess the translated files using another script which would remove these custom tags, of course.

I think you could perhaps even exploit a "var" tag for this purpose - I believe that Studio marks the "var" tag content as non-translatable already (not sure, I don't have a machine with Studio right now).

Thanks for the suggestion, Evzen. That is pretty much what I had in place atm, but I was wondering whether I was missing something already available in Studio by default, especially because the use of interpolation or other things like pipes for pluralization options, etc. is quite common in many i18n / l10n plugins these days.

Maybe something that can be implemented at some point.

Alvaro Mira

Did you try the Data protection suite?

https://appstore.sdl.com/language/app/sdl-data-protection-suite/936/

I just tested with a plain text file, but I am sure it works on every file type. You protext the specified content after the files are imported.

Daniel

Have you tested the Cleanup tasks on that? It works very well for me... However, until now I used it to hide <...> and &...;

But it should also work with {...}

I am sure it will work with Cleanup Tasks as well, I used to use that app a lot, unitl it started crashing Studio for me...Seems to work fine for most, maybe I should just reinstall...

Similar principle as the Data Protection Suite.

Daniel

Thanks, Daniel. I will give it a try, but it is not part of the batch processing it may be not be a scalable solution (and for pre and post processing I already have a script). But thanks a lot for the suggestion since I did not know about this add-on.

Thanks, Jerzy. I will give it a try because I tend to avoid using external add-ons, but this could work depending on how the task is performed. Thanks for the tip.

However, it seems like on its on Studio will not be able to do it.

Alvaro Mira

Did you try looking at the appstore json parser?  This has options for handling embedded content that might be useful for you.

Thanks, Paul. Yes I did but not the right solution because translatable attributes in the embedded HTML will not be processed. I understand that you could expand the default set of regex you get with that plugin, but I personally think coming up with a super complex regex for, lets say, images with titles and alt attributes, is not a good idea. I would rather rely on the default json filetype with the html embedded processor and use the current script I have atm.

Just to give you extra context, these are files for a Vue app using Vue i18n for localization.

Thanks for the suggestion though.

Alvaro Mira

You don't have to do this manually for every project. You can define your custom batch task and instead of running the "Prepare" task you run "Prepare my best Vue files" (or whichever name you fancy). At least with Cleanup Task that worked fine for me.

Daniel