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)

Standard version of HTML Tidy for SRFI documents Lassi Kortela 11 Sep 2020 05:41 UTC

HTML Tidy the best-known program for auto-formatting HTML markup (i.e.
the HTML source code itself, not the displayed page). It has been used
to format many SRFI documents as well.

The trouble with Tidy is that there are different versions floating
around. Some of them produce subtly different formatting; some don't
support HTML5 which we use for new SRFIs.

The canonical, up-to-date version with HTML5 support seems to be this one:

- https://github.com/htacg/tidy-html5
- http://www.html-tidy.org

Could we standardize on using the latest release of this tool for all
SRFIs? This wouldn't mean that SRFI authors need to use it for every
commit, but that editors and contributors would be free to use it, and
finalized SRFIs would be run through it.

I've found that auto-formatting code/markup saves a lot of time manually
figuring out where line breaks should go and fixing whitespace problems.
In a group effort, it saves debates and back-and-forth edits about which
style is the best (everyone uses whatever style the formatter uses).