Email list hosting service & mailing list manager

(missing)
(missing)
Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Arthur A. Gleckler (06 Mar 2019 03:06 UTC)
Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Marc Nieper-Wißkirchen (06 Mar 2019 10:12 UTC)
(missing)

Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Arthur A. Gleckler 06 Mar 2019 03:06 UTC

Lassi Kortela <xxxxxx@lassi.io> writes:

| IMHO it'd be most desirable to have a solution shaped like a
funnel:
|
| * Stage 1: Lenient SRFI markup from author
| * Stage 2: Lenient SRFI markup with standard classes
| * Stage 3: Standard SRFI markup and standard classes

That sounds fine, but I would like to see stage 1 and stage 3 be
as close as possible.  In other words, the less work is required
to go from stage 1 to stage 3, the better.  That way, the author
is encouraged to do the work from the beginning because it's easy,
and we don't have any line that we cross that makes it hard for
the author to edit the document, e.g. if errata are reported.