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

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

From: julian.reschke at gmx.de (Julian Reschke)
Date: Tue, 16 Feb 2016 08:08:05 +0100
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <36D9BDC4-BDC3-4B8D-AAD1-6965309476FD@cisco.com>
References: <76FD8A33-4FE3-4333-8E7C-BE2E274C1D24@cisco.com> <56C236F1.7060200@gmx.de> <36D9BDC4-BDC3-4B8D-AAD1-6965309476FD@cisco.com>
Message-ID: <56C2CAD5.9010602@gmx.de>

On 2016-02-16 07:06, Joe Hildebrand (jhildebr) wrote:
> On 2/15/16, 1:37 PM, "Julian Reschke" <julian.reschke at gmx.de> wrote:
>
>
>
>>>> ...which reminds me about the fact that there are things other than
>>>> <sourcecode> that require a mono-spaced font / no formatting, but should
>>>> be indented like the surrounding text, namely examples. What do we do
>>>> with those?
>>>
>>> I think the semantic for those is pretty close to artwork.  Perhaps we could add "block-left", "block-right", and "block-center" to the artwork/@align attribute?  If that's too much (which I think it might be), we could just add "block".
>>
>> My preference would be not to overload "align". It's not "artwork", so
>> it'll be more consistent to have another element that it like
>> sourcecode, just not with the semantics of embedding "code".
>
> For a lot of examples, I wouldn't mind having them in a <sourcecode>.  Can you talk more about the semantics you're looking for, and how they differ from <sourcecode>?

Well, apart from the misleading name:

1) different styling by default

2) implications with respect to the copyright (does it imply <CODE 
BEGINS> etc...)?

Best regards, Julian