Re: [Tools-discuss] Why do we even have text formats any more?

Toerless Eckert <> Wed, 28 July 2021 14:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7F7763A12C5 for <>; Wed, 28 Jul 2021 07:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WTcc0DrnTDbx for <>; Wed, 28 Jul 2021 07:31:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D41D73A12C3 for <>; Wed, 28 Jul 2021 07:31:57 -0700 (PDT)
Received: from ( [IPv6:2001:638:a000:4134::ffff:51]) by (Postfix) with ESMTP id 4D222548053; Wed, 28 Jul 2021 16:31:52 +0200 (CEST)
Received: by (Postfix, from userid 10463) id 40A4E4E7B8B; Wed, 28 Jul 2021 16:31:52 +0200 (CEST)
Date: Wed, 28 Jul 2021 16:31:52 +0200
From: Toerless Eckert <>
To: Martin Thomson <>
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <>
Subject: Re: [Tools-discuss] Why do we even have text formats any more?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Jul 2021 14:32:03 -0000

a) As mentioned in before, i would love for datatracker to offer
   the option for users to choose or even upload an html style sheet
   which would then be used for rendering of datatracker drafta/RFC
   for them. This IMHO would be the most easy and useful starting point 
   to leverage the flexibility of HTML.

b) I can not see any way to move away from a pure text editor
   for all core work - writing drafts and commenting on them.
   I can see that this can be done with either a txt or
   a markdown version of drafts/RFCs, not with HTML/XML.

c) RFCdiff is a big thing for me, i guess that can evolve to use other
   imputs than just txt over time.


On Wed, Jul 28, 2021 at 11:53:49AM +1000, Martin Thomson wrote:
> I realize that this might be a little inflammatory as far as subjects go, but bear with me.
> There are probably a few narrow cases where rendering plain text is better than HTML.  But what we've been doing for years (thanks to Henrik's great tool) is take text and turn it into HTML using the power of regular expressions.  That's been good, but it's not always reliable (how many errata mention that "Section X of [FOO]" links to Section X of this document?).  It's also been lagging as the text format changed (case in point: lack of a table of contents).
> Here's an alternative: style the HTML so that it looks like the text.  I tried this and it worked shockingly well.
> Repo:
> Demo:
> This isn't perfect, but it seems pretty good to me.  Keep in mind that this took only a little bit of time to sketch out. No doubt it can be improved.  The readme has a bunch of things I found, all minor.
> I don't think that this is the end of text, but a possible way to limit our use of the htmlizer[1].  People who need to automate access to content might still use text, though I will argue that XML is superior in that regard.   The other thing that comes to mind is diffs: HTML-native diff tools are somewhat less than ideal.  Either way, serving HTML is just better.
> Enjoy,
> Martin
> [1] Though I still see a shocking number of people authoring in XML (or XML-capable input formats) and submitting in text.  But I think we have plans to limit that.
> ___________________________________________________________
> Tools-discuss mailing list -
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to:
> * Report bugs to:
> * Report all other bugs or issues to:
> List info (including how to Unsubscribe):