You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 15, 2023. It is now read-only.
The newlines within the json vary among literal "\\n", "\/n" and "\n". Both 1 and 2 are essentially wrong following ECMA 404. Number 1 is where this issue appears, number 2 is "fixed" by the weird string-replace stuff happening here.
Gson (correctly) interprets the "\\n" in the json as literal "\n", "\/n" as "/n", and "\n" as an actual newline character. While number 1 probably occurs because of a single escaping backslash too many (in the json source), I don't really see why number 2 would happen, even though it seems to be the most frequent by far.
Other json elements are also affected (like "infos").