control characters in JSON

[markvanderloo]

In JSON, strings cannot contain control characters such as newline (ASCII 12). So we should replace them with their escape sequences, e.g.

NEWLINE -> \n
CARRIAGE RETURN -> (remove?)
TAB -> (replace with 2 or 4 spaces?)

this is important because we want to keep formatting of rule descriptions and indentations of rule definitions. Could be added to section 7 of the standard.

[olavtenbosch]

Jazeker, dat is precies waar ik een keuze moest maken bij het processen in het dashboard. Je voorstel lijkt me prima voor de NEWLINE en CR TAB: misschien inderdaad nuttig, maar er zijn oorlogen gevoerd over 2 of 4 spaces. Consequent met \n zou dan zijn \t nietwaar? Olav

…

On Fri, Sep 22, 2017 at 3:27 PM, Mark van der Loo ***@***.***> wrote: In JSON, strings cannot contain control characters such as newline (ASCII 12). So we should replace them with their escape sequences, e.g. NEWLINE -> \n CARRIAGE RETURN -> (remove?) TAB -> (replace with 2 or 4 spaces?) this is important because we want to keep formatting of rule descriptions and indentations of rule definitions. Could be added to section 7 of the standard. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABinxRqztJ8xxOrSpXVfAaDqmT8Y_OSIks5sk7WlgaJpZM4PgtHw> .