New draft (#3) of SRFI 211: Scheme Macro Libraries Arthur A. Gleckler (28 Sep 2020 15:51 UTC)
Re: New draft (#3) of SRFI 211: Scheme Macro Libraries John Cowan (28 Sep 2020 16:45 UTC)
Re: New draft (#3) of SRFI 211: Scheme Macro Libraries Arthur A. Gleckler (28 Sep 2020 17:04 UTC)
Re: New draft (#3) of SRFI 211: Scheme Macro Libraries John Cowan (28 Sep 2020 17:23 UTC)
Re: New draft (#3) of SRFI 211: Scheme Macro Libraries Arthur A. Gleckler (28 Sep 2020 17:34 UTC)
Re: New draft (#3) of SRFI 211: Scheme Macro Libraries Marc Nieper-Wißkirchen (28 Sep 2020 17:42 UTC)
Re: New draft (#3) of SRFI 211: Scheme Macro Libraries Arthur A. Gleckler (28 Sep 2020 17:53 UTC)
Re: New draft (#3) of SRFI 211: Scheme Macro Libraries Marc Nieper-Wißkirchen (28 Sep 2020 17:58 UTC)

Re: New draft (#3) of SRFI 211: Scheme Macro Libraries Marc Nieper-Wißkirchen 28 Sep 2020 17:57 UTC

Am Mo., 28. Sept. 2020 um 19:53 Uhr schrieb Arthur A. Gleckler
<xxxxxx@speechcode.com>:
>
> On Mon, Sep 28, 2020 at 10:42 AM Marc Nieper-Wißkirchen <xxxxxx@gmail.com> wrote:
>
>>
>> It's a bit unfortunate that HTML is the standard for SRFI documents.
>> If it were an extensible markup language (or even LaTeX in a
>> restricted form), things would be probably easier both for authors and
>> for postprocessing.
>
>
> Yikes!  The idea of writing code to post-process documents in any TeX-derived language terrifies me.

Can't one build on Texinfo?

(Or we use TeX itself to output its document in another format...)