Slash (/) written as "\/" in the resulting file about jsonlab

[fangq]

@sjeung, / can be escaped as \/ in JSON, which has been listed in the official website/syntax at http://json.org (see this diagram) and many other places.

However, some recognized that escaping / is not required in the specification - although allowed. Because of this, about a month ago, we disabled this escaping in savejson (loadjson still parses \/).

Because @robertoostenveld updated JSONLab back in March in this PR, so, it does not contain this change. If stop escaping / is desired, we can ask @robertoostenveld to update the JSONLab with the latest version.

[sjeung]

Thanks for the fast reply, yes, I think it will be indeed nice to skip escape in this case. Although it was not problematic to put the resulting data through validator, the specification states that "not applicable" is to be written as "n/a".

[fangq]

@sjeung, it is my opinion that BIDS should allow escaping n/a as n\/a when written in the JSON sidecar file, because any JSON-compatible parser should unescape n\/a back to n/a thus they are equivalent.

nonetheless, for the default setting of JSONLab, if the unescaped version is the preference, then updating to the latest code would fix it.

[robertoostenveld]

Ok, updating jsonlab is something for me to do. Thanks for the quick response.

…

Op 24 mei 2022 om 21:17 heeft Qianqian Fang ***@***.***> het volgende geschreven:  @sjeung, it is my opinion that BIDS should allow escaping n/a as n\/a when written in the JSON sidecar file, because any JSON-compatible parser should unescape n\/a back to n/a thus they are equivalent. nonetheless, for the default setting of JSONLab, if the unescaped version is the preference, then updating to the latest code would fix it. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[sjeung]

Thank you both, I will close the issue as we found the solution for now.