[rfc-i] Unicode characters for ASCII control characters

Phillip Hallam-Baker phill at hallambaker.com
Wed Jun 3 09:33:33 PDT 2015


On Wed, Jun 3, 2015 at 12:17 PM, Heather Flanagan (RFC Series Editor) <
rse at rfc-editor.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 6/3/15 9:02 AM, Phillip Hallam-Baker wrote:
> > After extensive discussion, it seems that by far the best way to
> > combine JSON documents in a sequence is to use a non-printable
> > ASCII character as a separator. The character RS (record separator)
> > being the chosen one for JSON Sequences.
> >
> > It occurs to me that when we write specs based on this we are going
> > to want to represent said character in a visible fashion in text.
> >
> > Does anyone know if there is a defined unicode character for
> > 'printable non-printable' ? I had a look and could not see
> > anything.
> >
>
> Would using the U+ notation for the character work here?
>

Found it! U+241E
␞

In the 'Control Pictures' section.

I think this should allow a lot more useful examples when writing specs
with significant CRLF sequences.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20150603/a1d70baf/attachment.html>


More information about the rfc-interest mailing list