[rfc-i] tabs [was: sourcecode indentation]

tony at att.com (HANSEN, TONY L) Tue, 16 February 2016 18:34 UTC

From: tony at att.com (HANSEN, TONY L)
Date: Tue, 16 Feb 2016 18:34:05 +0000
Subject: [rfc-i] tabs [was: sourcecode indentation]
In-Reply-To: <9604CBFC-46A8-46B8-8E4F-E6CBB3B0BE22@vpnc.org>
References: <B7E2CCFD-F56B-4749-B8D2-C3F4CFF3EF5F@cisco.com> <56C2B0E8.7070900@it.aoyama.ac.jp> <F5B55E50-D7AA-427A-932C-37D4872F9BD4@cisco.com> <4998B3A5-750C-4095-8FDD-3168FE6CABCA@gmail.com> <9604CBFC-46A8-46B8-8E4F-E6CBB3B0BE22@vpnc.org>
Message-ID: <37D1BAB2-05AE-46CF-9D9C-C4439B01BF6C@att.com>

On 2/16/16, 10:36 AM, "Paul Hoffman" <paul.hoffman at vpnc.org> wrote:


>On 16 Feb 2016, at 6:30, Tony Hansen wrote:
>
>>> On Feb 16, 2016, at 1:14 AM, Joe Hildebrand (jhildebr) 
>>> <jhildebr at cisco.com> wrote:
>>>
>>> I think the current situation is pretty close to 2119's "SHOULD NOT". 
>>>  You SHOULD NOT put a tab character in <sourcecode>, unless it is 
>>> absolutely required in the target language.  To deal with this, we 
>>> could add a tabs="true" attribute to <sourcecode>, and give an error 
>>> if there's an unintended tab character.
>>
>> A light tweak would be tabs="8" if tabs are present and to be allowed, 
>> and error if tabs is not defined.
>>
>+1 to "no tabs allowed at all", given that the only example given so far 
>is makefiles and we have now seen why they are not needed.

The other example is

<source src="http://some/path/to/code">

where the author may not be able to control whether tabs are used there or not.

	Tony