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

tony at att.com (HANSEN, TONY L) Wed, 17 February 2016 13:55 UTC

From: tony at att.com (HANSEN, TONY L)
Date: Wed, 17 Feb 2016 13:55:46 +0000
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: <A2D5E0B4-9BE7-4166-BC17-EA078C938C97@att.com>

On 2/16/16, 10:57 PM, "rfc-interest on behalf of Brian E Carpenter" <rfc-interest-bounces at rfc-editor.org on behalf of brian.e.carpenter at gmail.com> 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.

Hopefully there will be absolutely no need for <CODE BEGINS> or <CODE ENDS> to ever be seen again. Why bother when tools can be made available to easily extract the code blocks? I'm really curious.

	Tony Hansen