On Mon, 5 Oct 2020 18:48:27 +0200
Jan Stary wrote:
> In the mdoc source, it's .Sh DESCRIPTION; that's it.
> if Sh sections get turned into h1's (which is a decision in itself),
> all this does is it gives these h1's a class="Sh" and an id.
>
> That is the simplest and most obvious thing to do;
>
On Oct 07 14:58:31, jklow...@schemamania.org wrote:
> On Mon, 5 Oct 2020 18:48:27 +0200
> Jan Stary wrote:
>
> > In the mdoc source, it's .Sh DESCRIPTION; that's it.
> > if Sh sections get turned into h1's (which is a decision in itself),
> > all this does is it gives these h1's a class="Sh" and
> > We're starting from an mdoc document, right?
>
> In my example, yes.
>
> > Therefore every h1 is generated from Sh,
>
> I'm not sure where the mapping from mdoc macros
> to html elements is described (beside the code),
> but Ingo surely will know.
>
> > so every h1 is . What, then, is the
On Wed, 7 Oct 2020 22:52:03 +0200
Jan Stary wrote:
> > > That is the simplest and most obvious thing to do;
> > > it is up to the presentation author to prescribe a style
> > > to h1's of class Sh (or refer to a specific one by its id).
> >
> > What tool does that, btw?
>
> http://mandoc.bsd.
Hi James,
James K. Lowden wrote on Wed, Oct 07, 2020 at 06:58:33PM -0400:
> I shouldn't criticize mandoc, especially its HTML output, without
> having used it.
>
> mdoc doesn't have levels of section headings the way -ms has.
Mostly true; mdoc has .Sh and .Ss, and i map these to and .
Since
