From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc selectively transfers glyphs from LuaLaTeX to DOCX
Date: Tue, 25 Jul 2017 18:46:49 +0200 [thread overview]
Message-ID: <20170725164648.GA7277@Johns-MBP.home> (raw)
In-Reply-To: <6ac7783a-acbb-4d7f-8ed4-0fcf150d3422-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
+++ Sean Winslow [Jul 25 17 09:30 ]:
> [warning] Could not load include file 'fontspec.sty' at line 6 column
> 22
> [warning] Could not load include file 'etoolbox.sty' at line 7 column
> 22
> These warnings do not come if I use the non-nightly version, and I
> believe that both of these packages are still needed? Am I
> misunderstanding how to use the nightly build?
The same thing is happening; it's just that the nightly
actually tells you that it's not loading these sty files.
If you put them in the working directory, pandoc would
try to load them, but it wouldn't be able to make much
of either, since they use plain tex macros.
next prev parent reply other threads:[~2017-07-25 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 16:37 Sean Winslow
[not found] ` <b4abf81b-74e7-490a-8cb9-f6a313c651e0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-23 7:47 ` John MacFarlane
2017-07-23 23:20 ` Sean Winslow
[not found] ` <94be1e1e-c49f-4fe6-92fe-4aaf13c083f3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-24 8:58 ` John MacFarlane
[not found] ` <20170724085825.GA4877-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2017-07-24 9:17 ` John MacFarlane
2017-07-24 11:34 ` Melroch
2017-07-24 15:01 ` Sean Winslow
[not found] ` <261e84b1-9891-465a-a21e-80a61b9e98c0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-24 17:25 ` John MacFarlane
[not found] ` <20170724172502.GA26245-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2017-07-25 16:30 ` Sean Winslow
[not found] ` <6ac7783a-acbb-4d7f-8ed4-0fcf150d3422-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-25 16:46 ` John MacFarlane [this message]
2017-07-24 19:27 ` BP Jonsson
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=20170725164648.GA7277@Johns-MBP.home \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).