From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: Texexec
Date: Mon, 07 Jul 2003 19:35:52 -0400 [thread overview]
Message-ID: <5.2.0.9.1.20030707193347.02e86b68@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0307041825050.17202-200000@twain.marshallwar d.net>
At 18:39 04/07/2003 -0500, Marshall Ward wrote:
>[mdw162@twain tmp]$ texexec --pdfarrange --paper=letter*letter --print=2up
>--result=out.pdf testcert10.pdf testcert11.pdf
>
>### Output attached as out.log ###
>
>
>##### RESILT FILE INFO #####
>
>[mdw162@twain tmp]$ pdfinfo out.pdf
>Creator: TeX
>Producer: pdfTeX-0.14h
better update to pdftex 1.0 or higher !
At this point I'm not really asking for help, but trying to maybe help
>point out a bug. It's texexec version 2.6, but if there is any other
>info you need please let me know. Oh --- and I know you're probably not
>the main developer/maintainer, but there wasn't one listed. So I'm going
>through you. :-)
can you download the latest beta?
- make sure that you run the right texexec i.e. 3.2
- you need to regenerate the format
but, forst, try the texexec i sent you (which is 3.2) (check symlinks)
hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-07-07 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0307012300450.9436-100000@twain.marshallward .net>
2003-07-02 18:08 ` Texexec Hans Hagen
2003-07-04 23:39 ` Texexec Marshall Ward
[not found] ` <Pine.LNX.4.44.0307041825050.17202-200000@twain.marshallwar d.net>
2003-07-07 23:35 ` Hans Hagen [this message]
2000-02-08 10:12 Dan Seracu
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=5.2.0.9.1.20030707193347.02e86b68@localhost \
--to=pragma@wxs.nl \
--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).