Curly brackets inside JSON value throw an error about json-autotranslate HOT 4 CLOSED

Hey @petrchutny,

thanks for your bug report! Could you tell me which i18n library or syntax you're using your JSON files for?

Colons are not supported by ICU, the default syntax that json-autotranslate uses for matching those variables. That's the reason you're getting the error message.

The matching is necessary for json-autotranslate to replace those fields with placeholders that don't get translated by Google or DeepL.

from json-autotranslate.

Hi,

thanks for replying. We don't use any particular I18N syntax, it's our own.
As I look at the code now, I see this record: "LABEL_SEQUENCE_STEP": "Step value: {step}",, which makes me wonder why there was a colon in the middle of curly brackets before. Maybe I have somehow generated that string wrong, or it's not meant to be like this. I will verify if it works OK when my VPN works, and then update you here.

from json-autotranslate.

Alright, tell me if that solves the problem :)

If you absolutely need colons or other special characters in your translation, you can easily write your own matcher. See the i18next matcher for a simple example.

from json-autotranslate.

from json-autotranslate.