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

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

From: julian.reschke at gmx.de (Julian Reschke)
Date: Tue, 16 Feb 2016 18:44:12 +0100
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <56C35BE7.6020105@alum.mit.edu>
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> <56C35BE7.6020105@alum.mit.edu>
Message-ID: <56C35FEC.3080008@gmx.de>

On 2016-02-16 18:27, Paul Kyzivat wrote:
> On 2/16/16 9:52 AM, 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.
>
> Why not just use <sourcecode> with type=example?

Mainly because an example, say an HTTP message, is *not* source code.

Best regards, Julian