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

julian.reschke at gmx.de (Julian Reschke) Wed, 17 February 2016 06:46 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Wed, 17 Feb 2016 07:46:28 +0100
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <56C3EFA0.9010208@gmail.com>
References: <76FD8A33-4FE3-4333-8E7C-BE2E274C1D24@cisco.com> <970A412E-B227-420F-8EE7-611A228D93E1@vpnc.org> <56C3EFA0.9010208@gmail.com>
Message-ID: <56C41744.9030405@gmx.de>

On 2016-02-17 04:57, Brian E Carpenter wrote:
> On 17/02/2016 16:27, Paul Hoffman wrote:
>> In re-reading this thread, I am now of the belief that we don't need <example> or even <sourcecode type="example">. The various
>> RFCs that discuss code in RFCs don't make any differentiation between code and examples, so there is no need for us to in the v3
>> format.
>>
>> If this changes in the future based on some (prolonged) discussion about IPR, we can make a change to the format then. Trying to
>> predict what might be desired is a really bad idea.
>
> To be clear, are you assuming that tags like <CODE BEGINS> and <CODE ENDS>
> will continue to be inserted manually by individual authors, as part of the
> <sourcecode> text?
>
> I have no problem with that, but it needs to be explicit.

I have a big problem with that, as it (a) defeats styling and (b) breaks 
the code semantics. That's why I suggested a separate attribute for that 
(see 
<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext-rfc2629.artwork).

Best regards, Julian