From: Rich & Sue Hock <hockcalendar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: preserving internal HTML link identifiers for github markdown
Date: Mon, 7 Sep 2020 08:22:02 -0700 (PDT) [thread overview]
Message-ID: <d7533e1d-7619-4aa2-ad98-5bd0afcad905n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1443 bytes --]
I am using pandoc to convert HTML to Markdown to populate a github wiki.
The only pandoc option I am using is
-t gfm
I would like to keep internal link identifiers from the HTML to arbitrary
places on the wiki page (as opposed to relying on automatically generated
heading identifiers).
When I encounter a document anchor like this in the source HTML:
<a id="fred">fred</a>
Pandoc converts it to this in the output:
<span id="fred">fred</span>
However, github wiki does not render this as a valid target, so my URL
https://github.com/name/repo/wiki#fred
does not jump to the proper point on the wiki page. However, if it was left
as an anchor instead of a span, i.e.
<a id="fred">fred</a>
Then github would render it properly and the URL would jump to the correct
position in the document.
The internal link would also work if coded in a "div" tag:
<div id="fred">fred</div>
Is there a way in pandoc to keep "a" tags with an id, or perhaps convert
them to "div", rather than converting them to "span"?
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d7533e1d-7619-4aa2-ad98-5bd0afcad905n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1902 bytes --]
reply other threads:[~2020-09-07 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d7533e1d-7619-4aa2-ad98-5bd0afcad905n@googlegroups.com \
--to=hockcalendar-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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).