Neil and Richard, hello.

<parenthesis>

On 26 Aug 2018, at 9:48, Neil Van Dyke wrote:

You could do all structural markup this way, or combine markup with inferred bits.

Incidentally, your example is a good fit for how SGML (and then HTML) was intended to be used, for text markup using elements and attributes (but it does involve more typing, and SGML&HTML don't have TeX-like blank line paragraph separation):

"Spoke to the client by telephone.  Confirmed I would <TODO DEADLINE="2018-08-28">send out the court form</TODO> on Tuesday."

Just as a parenthesis, SGML was originally conceived as something that (trained) people would type without editor support, and the document type definition has facilities for heavily tuning the lexer to support abbreviation. Thus with a few declarations, you could set up an SGML document in which a standard/unmodified SGML processor would parse

    We must [todo 2018-08-28/send out the court forms].

in the same way that it would parse, say,

<para>We must <todo deadline="2018-08-28">send out the court forms</todo>.</para>

(if I recall correctly -- it's been a while). It could quite possibly handle newlines as paragraph breaks, too. The facilities to do this were what amongst the things which were removed from SGML to get XML (and made creating an XML parser merely a manageable headache).

This does not constitute a suggestion for immediate further work!

I mention this in part for sentimental reasons, because I was at one point enjoying processing SGML documents using a language called DSSSL, and decided to explore this language 'scheme' that it was reportedly an implementation of, and I printed out R5RS. So DSSSL Good.

Best wishes,

Norman

</parenthesis>

--
Norman Gray  :  https://nxg.me.uk

--
You received this message because you are subscribed to the Google Groups "Racket 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to