From: Richard Grace <rchrdgrace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Markdown+internal HTML links to Word format breaks links
Date: Wed, 12 Jan 2022 10:22:03 -0800 (PST) [thread overview]
Message-ID: <52d5b2be-ed5e-4854-9fb8-4bd4789fdd6an@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1141 bytes --]
I make heavy use of <A NAME> html links to create links to internal
sections within documents in Markdown. Unfortunately, Pandoc doesn't
handle these well at all, despite the links being implemented correctly
with the same methodology across the board. (HTML links to external
destinations work fine.) Links can be very time-consuming to correct, since
all my work will be wiped out if I run another conversion after edits and
feedback. This isn't acceptable, of course.
This shouldn't be that hard. Otherwise, Pandoc does do a good job. But this
relatively simple task is seemingly beyond its powers. Is there a solution?
This is the kind of thing that makes Markdown a consistently unwelcome
format in my workflow.
--
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/52d5b2be-ed5e-4854-9fb8-4bd4789fdd6an%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1451 bytes --]
reply other threads:[~2022-01-12 18: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=52d5b2be-ed5e-4854-9fb8-4bd4789fdd6an@googlegroups.com \
--to=rchrdgrace-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).