[rfc-i] sourcecode indentation

cabo at tzi.org (Carsten Bormann) Sun, 14 February 2016 22:23 UTC

From: cabo at tzi.org (Carsten Bormann)
Date: Sun, 14 Feb 2016 23:23:54 +0100
Subject: [rfc-i] sourcecode indentation
In-Reply-To: <56C0C7E5.9040905@alum.mit.edu>
References: <666F9FC6-BF2D-4827-B24A-20A8CCCC9F00@att.com> <F0D416DA-2C0F-4E11-B62C-7B9788796102@vpnc.org> <56BFA2E7.8070400@gmail.com> <56BFA781.10709@alum.mit.edu> <56C02EBB.1050904@tzi.org> <56C0C7E5.9040905@alum.mit.edu>
Message-ID: <56C0FE7A.6020608@tzi.org>

Paul Kyzivat wrote:
>> Not sure you are talking about these, but ASCII HT characters MUST NOT
>> be allowed in RFC source.
>>
>> RFC 7386/7396 should be enough warning here.
> 
> Then sourcecode languages that require (such as Makefiles) them cannot
> appear in ietf documents.

That is correct.  I agree that it is not a big loss, because a simple
tabify (or however it's called in your editor) will convert a spacy
Makefile into a tabby one.  (Weirder languages may need to be
base64-encoded, as was done for the compressed tar file in RFC 6716.)

(While I understand most people on this list already have gray hair, for
those who weren't around when the tab-vs-spaces discussion was resolved:
https://www.jwz.org/doc/tabs-vs-spaces.html
)

Gr??e, Carsten