On Wed, Mar 6, 2019 at 1:19 PM Lassi Kortela <xxxxxx@lassi.io> wrote:

1) It doesn't add all that much markup when we already have all the
other markup in the file. Yes, the argument lists become messy, but they
are only a fairly small part of the SRFI.

Yes, but they are far and away the most irritating part to construct by hand.

Even in Markdown I have to write things like

`(foo `*dst src* ...`)`

to get what I want, and note that "dst" and "src" end up in the same tag!

That's one of the main reasons why I copy SRFIs rather than

writing new ones whenever possible. In addition, when a SRFI is

based closely on an existing system, the markup comes from the

documentation from that implementation and I don't worry that

it doesn't look like the rest.

Making this process significantly more difficult is going to be a

huge gumption trap for me. <https://en.wikipedia.org/wiki/Gumption_trap>

2) Any 'class=' attributes in the markup should be designed so that they
can be ignored when rendering the document. Especially if we use
semantic HTML tags in a uniform manner as suggested by you and Arthur,
e.g. <var> for arguments. We should design things so that it renders in
a reasonable manner even without the classes.

Since classes are a major hook for CSS and CSS is the preferred style

of formatting of all but the simplest kind today, I think that's unreasonable.

*Some* classes may have no formatting implications.

John Cowan http://vrici.lojban.org/~cowan xxxxxx@ccil.org

"Why yes, I'm ten percent Jewish on my manager's side."

--Connie Francis