\n control character is the newest purposes-xx.json and vendor-json

Question

\n control character is the newest purposes-xx.json and vendor-json

mredl opened this issue a year ago · 3 comments

mredl commented a year ago

in the latest json files there are some unexpected control characters, which cause a fail of parsing the json.

an example, the \n:
{"id":2,"name":"Verwendung reduzierter Daten zur Auswahl von Werbeanzeigen\n\n","description":

Answer 1 · 2024-01-20T23:50:59.000Z

Not sure I follow. newlines '\n' in strings are correct syntax, also in JSON.

Answer 2 · 2024-01-30T10:05:50.000Z

just try this in any browser console:
JSON.parse('{"result":true, "test":"break here\n"}');

you will get this error:
VM173:1 Uncaught SyntaxError: Bad control character in string literal in JSON at position 34 (line 1 column 35) at JSON.parse (<anonymous>) at <anonymous>:1:6

Answer 3 · 2024-01-30T18:34:40.000Z

Some JSON interpreter allow that syntax others don't. There is a lot of debate on this on the web. Anyway the name strings in our JSON should not have an special characters like \n. I removed these. An update of the German translation should be available by end of this week.