From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: E Lin <exl022-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: converting from .tex to docx, preserving references with cleverref package
Date: Sat, 07 Mar 2020 10:42:34 -0800 [thread overview]
Message-ID: <m27dzw3t2d.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <d46c4e35-5680-4c5a-b001-52809df0c2bc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
A relatively recent change in master (still not in a released
version) adds table numbering.
cleverref is another story. Pandoc can't try to support
all of the thousands of latex packages.
E Lin <exl022-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> I have been searching for good pandoc workflow to include filters to get
> from .tex to .docx. I came across pandoc-crossref, but after a lot of
> experimentation and reference searching, it seems that this converts only
> from markdown to docx. I compose in LaTex, and I'm looking for a good
> converting workflow. Using pandoc, I have figured out how to get text over
> and preserve bib references/cites. However, Tables are not numbered, and
> the reference numbers in the text (esp. using the cleverref package) do not
> convert over to .docx.
>
> Is there any workflow and filter packages that can get me there?
>
> --
> 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/d46c4e35-5680-4c5a-b001-52809df0c2bc%40googlegroups.com.
prev parent reply other threads:[~2020-03-07 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 4:01 E Lin
[not found] ` <d46c4e35-5680-4c5a-b001-52809df0c2bc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-03-07 18:42 ` 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=m27dzw3t2d.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=exl022-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).