[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Marking lisp expressions
|
From: |
Gavin Smith |
|
Subject: |
Re: Marking lisp expressions |
|
Date: |
Sun, 26 Jan 2020 17:03:01 +0000 |
|
User-agent: |
Mutt/1.9.4 (2018-02-28) |
On Mon, Jan 27, 2020 at 01:47:52AM +0900, Jean-Christophe Helary wrote:
>
>
> > On Jan 27, 2020, at 0:15, Gavin Smith <address@hidden> wrote:
> >
> > On Sun, Jan 26, 2020 at 10:58:45PM +0900, Jean-Christophe Helary wrote:
> >> I have no idea what I am talking about, mind you, but maybe having
> >> makeinfo call the appropriate mode, export the code block region to html
> >> based on that mode and insert that html into the "general" makeinfo HTML
> >> output would be the way to go ? Maybe not all the styles, etc., but just
> >> the HTML structure (anything within <body> </body>) so that texinfo
> >> specific styles can later be applied.
> >>
> >> That would require to be aware of what structure each mode gives to such
> >> output so that proper CSS selectors are used (which is inconvenient).
> >> There are probably more elegant ways to achieve that, though.
> >
> > This is not possible as makeinfo is not part of emacs.
>
> Then, I don't think we should have any qualms about adding semantic tags to
> the code. TeX has plenty of things for math formulas, why not simply add
> things in texinfo for the few core languages of the GNU project ?
It makes the code samples in the Texinfo source unreadable and therefore
prone to error. If there is syntax highlighting it should be able to be
done automatically.
- Marking lisp expressions, Jean-Christophe Helary, 2020/01/25
- Re: Marking lisp expressions, Gavin Smith, 2020/01/26
- Re: Marking lisp expressions, Jean-Christophe Helary, 2020/01/27
- Re: Marking lisp expressions, Karl Berry, 2020/01/27
- Re: Marking lisp expressions, Jean-Christophe Helary, 2020/01/28
- Re: Marking lisp expressions, Gavin Smith, 2020/01/28