So this
Generates a JSON that automatically escapes the backslash in \n
Which we obviously don’t want. But this
generates an error, which I’m assuming is because I set the project to treat proper escapes as errors since not escaping a " in a JSON tends to break the JSON. What’s the best practices for \n in JSON
Hello,
I am Antonis from the Transifex Support team.
Please take a look at this section of our documentation regarding escaped character behavior in JSON files. These are considered the most common practices for localization. The way it is set up in your example with the translation check error you won’t be able to save your translation.
If you want to still use this string as in your example you could set the translation check to give a warning instead of an error. This way you can save your string but you will be warned in each case.
Please let me know if you have any further questions and I will be happy to assist you.
Kind regards,
Antonis
Hello, I want to add something more, if you want)
where is my post??? tell me pls
Hello @Miters_Frigers,
I apologize for the late reply.
Please let me know how we can assist you if you still need it, and I will get back to you as soon as possible.
Kind regards,
Antonis