[rfc-i] How to indent artwork with surrounding block
Joe Hildebrand (jhildebr)
jhildebr at cisco.com
Tue Feb 16 10:15:39 PST 2016
I'm ok with <example>. Does it take most of the <sourcecode> attributes? If so, what does example/@type mean?
What happens when it's in a <figure>? Do the figures get named "Example 1"?
We'll probably need a couple of prep steps.
I'll need to add a section to the HTML draft, saying that it goes in a <pre> with class "example", and I'll need to add it to the list of elements that the pretty-printer doesn't whitespace fold.
Did I miss anything? I'll prototype this tomorrow, probably.
On 2/16/16, 10:44 AM, "rfc-interest on behalf of Julian Reschke" <rfc-interest-bounces at rfc-editor.org on behalf of julian.reschke at gmx.de> wrote:
>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
>rfc-interest mailing list
>rfc-interest at rfc-editor.org
More information about the rfc-interest