From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Help exporting to-do list as LaTeX/PDF
Date: Sat, 04 Oct 2014 09:01:13 -0700 [thread overview]
Message-ID: <87ppe7akom.fsf@berkeley.edu> (raw)
In-Reply-To: 8962C06C-102B-40D7-B9AE-31F0E10D8DCA@yank.to
Hi Andreas,
Andreas Yankopolus <andreas@yank.to> writes:
> ...
> kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ecbx1200
>
> kpathsea: Running mktexfmt mf.base
> mktexpk: Mismatched mode ljfour and resolution 600; ignoring mode.
> mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input ecbx1200
> This is METAFONT, Version 2.718281 (Web2C 2013)
>
> kpathsea: Running mktexfmt mf.base
> I can't find the base file `mf.base'!
> It took a while to get to this point, and I had to install a number of
> font packages from the pkgsrc tex-* collection. I do have tex-ec-1.0
> and tex-eco-1.3 installed. But it seems like the problem is more with
> metafont, which is completely beyond me.
Yeah, this looks to me like your setup is attempting to load (or build??) a
font as part of the compilation process. As far as I know, that is not
something that should be required when compiling an Org document
exported to LaTeX with the default options.
What are the values of your
org-latex-default-packages-alist
org-latex-packages-alist
org-latex-pdf-process
variables? And what does the header of the exported .tex file look
like?
I guess the way to debug this is to remove the packages that are loaded
in the exported .tex file, one at a time, until you discover the one
that is at fault here. (If it's not some particular package, but
rather TeX/LaTeX itself that's trying to use METAFONT, I think you're in
deeper waters...)
Best,
Richard
next prev parent reply other threads:[~2014-10-04 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 11:51 Help exporting to-do list as LaTeX/PDF Andreas Yankopolus
2014-10-04 16:01 ` Richard Lawrence [this message]
2014-10-08 12:22 ` Andreas Yankopolus
2014-10-09 22:09 ` Andreas Yankopolus
2014-10-04 17:36 ` Thomas S. Dye
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppe7akom.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).