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

loa at pi.nu (Loa Andersson) Wed, 17 February 2016 04:04 UTC

From: loa at pi.nu (Loa Andersson)
Date: Wed, 17 Feb 2016 12:04:42 +0800
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: <56C3F15A.5090006@pi.nu>

Brian,

I've nt inserted much code in IDs, the time I did it the RFC Editor
re-did the entire xml around it - I used artwork (blush).

However, you were hinting that there are two cases
   - manual
   - "automatic"

Are there an automated way of doing it, what editing tool do I need?
On the other hand, couldn't we just post an output from the automated
process, and just let that guide us if we do it manually?

/Loa

On 2016-02-17 11: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.
>
>     Brian
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>