[rfc-i] How to indent artwork with surrounding block

julian.reschke at gmx.de (Julian Reschke) Tue, 16 February 2016 15:39 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Tue, 16 Feb 2016 16:39:05 +0100
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <7584199C-1AB7-40B2-9671-C0CE0FC36676@vpnc.org>
References: <76FD8A33-4FE3-4333-8E7C-BE2E274C1D24@cisco.com> <56C236F1.7060200@gmx.de> <36D9BDC4-BDC3-4B8D-AAD1-6965309476FD@cisco.com> <56C2CAD5.9010602@gmx.de> <7584199C-1AB7-40B2-9671-C0CE0FC36676@vpnc.org>
Message-ID: <56C34299.4010109@gmx.de>

On 2016-02-16 15:52, Paul Hoffman wrote:
> ...
> I am in general in favor of <example> because of his #2 reason. Because
> the IETF went down the twisty road of having special rules for code in
> RFCs, it would be good to be able to say "this bit of monospace text
> that is set out on its own is, in fact, not source code". FWIW, I'm
> strongly opposed to "different styling by default" because doing so will
> just confuse the reader.
> ...

Here's an example to illustrate my point: 
<http://greenbytes.de/tech/webdav/rfc7235.html#header.www-authenticate>.

It contains

- "source code" (ABNF), which just happens to use a mono-spaced font

- an example (a header field), which also has a border

I don't think this is confusing at all, but then, as always, feedback 
appreciated...

Best regards, Julian