From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: **SPAM** ConTeXt breaks pdfcrop
Date: Wed, 20 Jun 2012 20:32:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1206202030360.2296@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4FE26437.7080401@googlemail.com>
On Thu, 21 Jun 2012, S Barmeier wrote:
> On 06/18/2012 07:47 PM, Vladimir Lomov wrote:
>> Hello,
>> ** S Barmeier [2012-06-18 15:38:20 +0900]:
>>
>>> I guess this has to do with my path variables, but having context
>>> minimals installed prevents pdfcrop from running successfully:
>>
>>> PDFCROP 1.33, 2012/02/01 - Copyright (c) 2002-2012 by Heiko Oberdiek.
>>
>>> kpathsea: Running mktexfmt pdftex.fmt
>>> /usr/local/texlive/2010/bin/x86_64-linux/mktexfmt: 395:
>>> /usr/local/texlive/2010/bin/x86_64-linux/mktexfmt:
>>> /home/user/context/tex/texmf/texconfig/tcfmgr: not found
>>> fmtutil: config file `fmtutil.cnf' not found.
>>> !!! Error: pdfTeX run failed!
>>
>>> Does anybody have a suggestion of how to deal with this issue successfully?
You can also use pdftrimwhite (requires perl) which is part of the ConText
distribution:
mtxrun pdftrimwhite filename.pdf result.pdf
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-06-21 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 6:38 S Barmeier
2012-06-18 10:47 ` Vladimir Lomov
2012-06-21 0:00 ` S Barmeier
2012-06-21 0:32 ` Aditya Mahajan [this message]
2012-06-21 0:42 ` S Barmeier
2012-06-21 0:45 ` Aditya Mahajan
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=alpine.LNX.2.02.1206202030360.2296@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/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).