[rfc-i] sourcecode indentation

paul.hoffman at vpnc.org (Paul Hoffman) Sat, 13 February 2016 20:56 UTC

From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Sat, 13 Feb 2016 12:56:10 -0800
Subject: [rfc-i] sourcecode indentation
In-Reply-To: <666F9FC6-BF2D-4827-B24A-20A8CCCC9F00@att.com>
References: <666F9FC6-BF2D-4827-B24A-20A8CCCC9F00@att.com>
Message-ID: <F0D416DA-2C0F-4E11-B62C-7B9788796102@vpnc.org>

On 12 Feb 2016, at 15:52, HANSEN, TONY L wrote:

> A better example of outdent would be
>
> <sourcecode indent="-4">
>  foo
>    bar
>      baz
> </sourcecode>
>
> which would generate:
>
> <pre class="sourcecode">
> foo
> bar
>  baz
> </pre>
>
> in the HTML format.
>
> A more common variation might be where the input is coming from 
> elsewhere and you have no control over the indentation used there:
>
> <sourcecode indent="-4" src="http://URL to the source code"/>
>  or
>
> <sourcecode indent="16" src="http://URL to the source code"/>
>
> The use case for this is very specific, but probably not something 
> that would get used often.
>
> If you think you would find it useful, please speak up.

I will speak up against this idea. For sourcecode where indentation is 
important, seeing an example at the left margin might cause the reader 
to think that the code is in fact not indented. Your example above is a 
classic one: someone seeing that text would assume that "foo" and "bar" 
are at the same level when they are not. I would prefer not to have the 
RFC format have a display hinting mechanism that could be used to make 
examples harder to interpret.

--Paul Hoffman