From: M A <marshall-g+3rYsS+t1LR7s880joybQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to generate endnotes LaTeX->Word?
Date: Fri, 21 May 2021 14:40:34 -0700 (PDT) [thread overview]
Message-ID: <49706bc8-2016-449a-a5a2-9660a2f24fbdn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1348 bytes --]
Based on my understanding of the discussion in this github issue:
https://github.com/jgm/pandoc/issues/4041 ,
it looks like there is no general way to generate endnotes. Is this
correct? (There is an option --reference-location that does something like
this for Markdown output.)
I'm generating a Word document from LaTeX. I know how to generate endnotes
in LaTeX using the LaTeX endnote package and using the \endnote command and
\theendnotes. However, when I use this with Pandoc, the notes disappear.
Here is an example of the kind of pandoc command line I use:
pandoc -N --filter pandoc-crossref --citeproc --bibliography mybib.bib
--csl .chicago-author-date.csl mydoc.tex -o mydoc.docx
Is there a workaround of some kind? (I'm converting a book, and there are
many notes, so converting the notes to text at the end of the document by
hand while preserving the numbering is something I'd like to avoid.)
Thanks!
--
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/49706bc8-2016-449a-a5a2-9660a2f24fbdn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1809 bytes --]
next reply other threads:[~2021-05-21 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 21:40 M A [this message]
[not found] ` <49706bc8-2016-449a-a5a2-9660a2f24fbdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-22 7:11 ` Bastien DUMONT
2021-05-22 20:56 ` M A
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=49706bc8-2016-449a-a5a2-9660a2f24fbdn@googlegroups.com \
--to=marshall-g+3ryss+t1lr7s880joybq@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).