Email list hosting service & mailing list manager

Standard version of HTML Tidy for SRFI documents Lassi Kortela (11 Sep 2020 05:41 UTC)
Re: Standard version of HTML Tidy for SRFI documents Arthur A. Gleckler (11 Sep 2020 15:52 UTC)
Re: Standard version of HTML Tidy for SRFI documents Marc Nieper-Wißkirchen (11 Sep 2020 16:00 UTC)
Re: Standard version of HTML Tidy for SRFI documents Arthur A. Gleckler (11 Sep 2020 18:45 UTC)
Re: Standard version of HTML Tidy for SRFI documents Arthur A. Gleckler (12 Sep 2020 02:00 UTC)
Re: Standard version of HTML Tidy for SRFI documents Marc Nieper-Wißkirchen (12 Sep 2020 07:45 UTC)
Re: Standard version of HTML Tidy for SRFI documents Arthur A. Gleckler (12 Sep 2020 13:45 UTC)
Re: Standard version of HTML Tidy for SRFI documents Lassi Kortela (12 Sep 2020 13:47 UTC)
Re: Standard version of HTML Tidy for SRFI documents Arthur A. Gleckler (12 Sep 2020 15:21 UTC)
Re: Standard version of HTML Tidy for SRFI documents Marc Nieper-Wißkirchen (12 Sep 2020 16:45 UTC)
Re: Standard version of HTML Tidy for SRFI documents Arthur A. Gleckler (12 Sep 2020 18:36 UTC)
Re: Standard version of HTML Tidy for SRFI documents Marc Nieper-Wißkirchen (12 Sep 2020 19:12 UTC)
Re: Standard version of HTML Tidy for SRFI documents Marc Nieper-Wißkirchen (12 Sep 2020 19:47 UTC)

Re: Standard version of HTML Tidy for SRFI documents Marc Nieper-Wißkirchen 11 Sep 2020 15:59 UTC

Am Fr., 11. Sept. 2020 um 17:52 Uhr schrieb Arthur A. Gleckler
<xxxxxx@speechcode.com>:

> Even if HTML Tidy produced nice output, I'm not sure I would want to use it.  One of my mantras is that the SRFI process should have as little friction as possible.  Many authors use other tools to produce the HTML they submit, which is fine.  The formatting of that HTML is typically not great, but if I passed the document through a formatter, the diffs would be full of inessential changes whenever a new draft was submitted.

As whitespace sometimes counts in HTML files, I find it hard to
universally format HTML files so that they look nice in the editor.

As for validation errors: Does anyone know of a simple Emacs tool that
does the validation for me?

PS Instead of some fancy HTML template, I am probably more interested
in standardizing how to write org-mode versions of SRFIs, which can
then be output to HTML using a (customized) exporter. :)