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

jhildebr at cisco.com (Joe Hildebrand (jhildebr)) Tue, 16 February 2016 18:48 UTC

From: jhildebr at cisco.com (Joe Hildebrand (jhildebr))
Date: Tue, 16 Feb 2016 18:48:46 +0000
Subject: [rfc-i] tabs [was: sourcecode indentation]
In-Reply-To: <37D1BAB2-05AE-46CF-9D9C-C4439B01BF6C@att.com>
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> <37D1BAB2-05AE-46CF-9D9C-C4439B01BF6C@att.com>
Message-ID: <5B6BB515-EAF0-49DA-B5A8-7B06225BD0E1@cisco.com>

On 2/16/16, 11:34 AM, "rfc-interest on behalf of HANSEN, TONY L" <rfc-interest-bounces at rfc-editor.org on behalf of tony at att.com> wrote:



>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.

The preptool can handle that.  It will already be getting the URL, inserting the text, and removing the src attribute.  It can either error or try to untabify if it finds tabs.  If it's going to untabify, it would probably have to look for both the emacs and vi tab width hints, which sounds like a PITA, but would be possible.  

I'd vote for just throwing an error.  If you don't control the source, have your build tool use curl to pull it down locally, untabify using whatever means you want, and point @src to the local file.

Note: I'm going to start a new thread on sourcecode/@originalSrc

-- 
Joe Hildebrand