\n control character is the newest purposes-xx.json and vendor-json about gdpr-transparency-and-consent-framework HOT 3 CLOSED

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.

from gdpr-transparency-and-consent-framework.

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

from gdpr-transparency-and-consent-framework.

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

from gdpr-transparency-and-consent-framework.