ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gmx.de>
Cc: "Dirk F. Raetzel" <raetzel@Mathematik.Uni-Marburg.de>,
	ntg-context@ntg.nl
Subject: Re: Problems with texexec
Date: Mon, 27 Mar 2000 10:15:01 +0200	[thread overview]
Message-ID: <38DF1885.B3FB46AA@gmx.de> (raw)
In-Reply-To: <3.0.6.32.20000326202855.0147e960@pop.wxs.nl>

Hallo Dirk, hallo Hans, hi all,

>I am using the latest tetex distribution under Solaris UNIX.
Which teTeX version?
a) teTeX 1.0.6
b) teTeX 1.0.7
c) teTeX beta 12 February 2000
a and b contain an rather old pdftex, c contains the newest pdftex
b and c conatin both a rather new context (as of begining of february,
whereas in a is a rather old (and buggy \frac) context.

> Texexec should run ok.
Indeed, what does $PATH_TO_TETEX_BINARIES/texexec --version produce?

> The main thing left to do is to uncomment the
> context format lines in the tetex config file.
fmtutil --edit
fmtutill --all

> >Using a document like pdftex-a.pdf I get in addition an error message
> >
> >   Error (1024) PDF version 1.3 -- xpdf supports version 1.2 (continuing
> >   anyway
> This means that there is a pdf 1.3 option used (probably the resource in
> the mirrored page is not recognized). Normally this does not hurt, and some
> day the xpdf libraries will catch up.
Well I use xpdf version 0.90, and in help (`?') I have the line:
Supports PDF 1.3, so you might update.
(Can one force PDF 1.2? Using ps2pdf of Ghostscript 6.01 one can choose
ps2pdf13 and ps2pdf12)

Tobias


  reply	other threads:[~2000-03-27  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.21.0003231706560.6881-100000@algol>
2000-03-26 18:28 ` Hans Hagen
2000-03-27  8:15   ` Tobias Burnus [this message]
2000-03-27 12:01     ` Hans Hagen
     [not found] <199909150659.CAA23484@godske.mi.uib.no>
1999-09-15 12:51 ` Berend de Boer

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=38DF1885.B3FB46AA@gmx.de \
    --to=burnus@gmx.de \
    --cc=ntg-context@ntg.nl \
    --cc=raetzel@Mathematik.Uni-Marburg.de \
    /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).