[Json] Fixing the U+2028 and U+2029 problem

John Cowan <cowan@mercury.ccil.org> Fri, 01 August 2014 21:10 UTC

Date: Fri, 01 Aug 2014 17:10:23 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: json@ietf.org
Message-ID: <20140801211023.GI13476@mercury.ccil.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/json/yYj57cI7GFsETUlmCa0jBl9m-vo
Subject: [Json] Fixing the U+2028 and U+2029 problem
Precedence: list

The unescaped characters U+2028 (LINE SEPARATOR) and U+2029 (PARAGRAPH
SEPARATOR) are valid in JSON strings, but illegal in JavaScript strings.
It's too late to warn about this in RFC 7159, but can we get a requirement
to escape these two characters into the definition of I-JSON, please?
It's a minor gotcha, but still a gotcha.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
Knowledge studies others / Wisdom is self-known;
Muscle masters brothers / Self-mastery is bone;
Content need never borrow / Ambition wanders blind;
Vitality cleaves to the marrow / Leaving death behind.    --Tao 33 (Bynner)

[Json] Fixing the U+2028 and U+2029 problem John Cowan
Re: [Json] Fixing the U+2028 and U+2029 problem Carsten Bormann