Can't stop Escaping of Slashes

Crowdin Issues
1

We currently face the problem, that every export from crowdin escapes slashes, like <b>test</b> will be exported to <b>test<\/b>.

This happens via build & download via UI and CLI. Someone has a clue how to stop that?

2

Hi marcelbrode,

Can you please tell us what file format you are using?

Looking forward to your reply,

3

Ah, well. Forgot to mention that.

We are working with JSON Files :slight_smile:

4

Hi @marcelbrode,

Now we have a plan to change it, so newly uploaded JSON files won’t get escaped slashes + we will probably add an extra export setting for JSON parser that will allow users to enable/disable escaping of slash.

For now, we can offer this solution:

Please set an export rule for \/ and replace it with / on output

1 Like
5

Nice to know!
Works like a charm! Thank you!

6

Hi @marcelbrode,

Hope you are doing great : )

Happy to inform you that our developers made improvements to the JSON file format and now if the file does not contain the escape slashes the slashes won’t be escaped on export either.

To see those changes it would be needed to re-upload the file to the project.

You can easily migrate all the translations from the old file to the newly uploaded one with preserving translation +approvals + authority in this way:

  • rename your file in Crowdin from for example from example.json to example_old.json(or any other name that you like);
  • upload the example.json again to the project (so you will have 2 files in Crowdin - old and new);
  • set the duplicates option “Hide (strict detection)” - due to it, the translations from the old file will migrate to the hidden duplicates in the newly uploaded example.json;
  • after that, you can delete the example_old.json and keep working only on the example.json file
1 Like