From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Richard Grace
<rchrdgrace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc fails to convert internal HTML links to Word format
Date: Wed, 12 Jan 2022 16:09:15 -0800 [thread overview]
Message-ID: <yh480k5yqolcno.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <687e6e74-c9f7-45e4-b8aa-3d85436a8f82n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
It works for me. For example, if I do
pandoc MANUAL.txt -o m.docx
where MANUAL.txt is the source of the user manual,
and open m.docx in Word, I see an internal link to
'Creating a PDF' on the first page. I click on this,
and Word takes me right to the appropriate section.
What version of pandoc are you using, and what
version of Word?
Richard Grace <rchrdgrace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> I have to use Markdown as my primary tool, and I also use a lot of HTML
> since MD is such a limited doc platform. (Definitely prefer writing in it.)
> I make heavy use of internal HTML links to subsections. Pandoc cannot
> handle these, every single such link is broken, including a TOC linked
> list. Is there a way to get this to work? Thank you
>
> --
> 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/687e6e74-c9f7-45e4-b8aa-3d85436a8f82n%40googlegroups.com.
prev parent reply other threads:[~2022-01-13 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 18:29 Richard Grace
[not found] ` <687e6e74-c9f7-45e4-b8aa-3d85436a8f82n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-12 18:30 ` Richard Grace
2022-01-13 0:09 ` John MacFarlane [this message]
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=yh480k5yqolcno.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=rchrdgrace-Re5JQEeQqe8AvxtiuMwx3w@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).