From: "Anthony J. Bentley" <anthony@anjbe.name>
To: discuss@mdocml.bsd.lv
Subject: Re: Mandoc HTML Output - Recognizing Sections
Date: Fri, 06 May 2016 14:54:21 -0600 [thread overview]
Message-ID: <86449.1462568061@CATHET.us> (raw)
In-Reply-To: <CAHwRYJnj9ywJAO1QO2LH5Di6ck4Uz7etfq9bCgaEt3+ghpbuFA@mail.gmail.com>
Hi Abhinav,
Abhinav Upadhyay writes:
> Thanks, I didn't know of that. I tried it, and it works for my
> purposes. However, the ids of the h1 tags seems to be some kind of
> encoding or hash (I didn't see the code to see how is it generated).
> As long as that id is consistent, I guess the solution you suggested
> will work for me.
The version of mandoc in CVS just uses the name of the section directly.
Older releases used hex ASCII values (for compliance with HTML4, which
is no longer necessary).
--
Anthony J. Bentley
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2016-05-06 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 17:58 Abhinav Upadhyay
2016-05-06 19:18 ` Anthony J. Bentley
2016-05-06 20:45 ` Abhinav Upadhyay
2016-05-06 20:54 ` Anthony J. Bentley [this message]
2016-05-06 21:05 ` Abhinav Upadhyay
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=86449.1462568061@CATHET.us \
--to=anthony@anjbe.name \
--cc=discuss@mdocml.bsd.lv \
/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).