discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Aman Verma <amanraoverma+vim@gmail.com>
To: discuss@mandoc.bsd.lv
Cc: schwarze@usta.de
Subject: Not all section headers have id in HTML output
Date: Wed, 28 Oct 2020 18:40:45 -0400	[thread overview]
Message-ID: <CA+c7JOB8Qk-wWzcytLqQf4FuopBfRnLF16DtmXftPnkE7C3obQ@mail.gmail.com> (raw)

Hi Ingo,

Thanks for the fix for the `pre` bug. I have another (possible)
bug to report:

In the HTML output for mdoc(7)[1] the first two section headers don't
have an id attribute. In fact, it seems that two other elements down the
page have taken the ids ("NAME" and "DESCRIPTION") that the first two
headers were supposed to have. This makes it impossible to link to those
headers and also breaks the table of contents generated with the `-O toc`
option to mandoc.

[1]: https://mandoc.bsd.lv/man/mdoc.7.html

Best regards,
Aman
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


             reply	other threads:[~2020-10-28 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 22:40 Aman Verma [this message]
2020-10-30 13:35 ` Ingo Schwarze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+c7JOB8Qk-wWzcytLqQf4FuopBfRnLF16DtmXftPnkE7C3obQ@mail.gmail.com \
    --to=amanraoverma+vim@gmail.com \
    --cc=discuss@mandoc.bsd.lv \
    --cc=schwarze@usta.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).