ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <aa056@chebucto.ns.ca>
Subject: Re: TeX Live 2003 miseries.
Date: Tue, 14 Oct 2003 20:11:55 -0300 (ADT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0310141954530.2121@cerberus.cwmannwn.nowhere> (raw)

On Mon, 13 Oct 2003, John Culleton wrote:

> I installed the latest version of TeXLive 2003 (the so-called demo
> version) and did the fmtutil and texhash bit.  When I ran a job for a
> customer, texexec hung up at the point where a graphic was being
> loaded. So I went back to last year's texlive in a terrible hurry.
> That worked fine.

What platform?  I tried to install various rc's on Win98 and ran into
numerous problems:

1.  the perl scripts were confused by the embedded spaces in the default
"c:\Program Files\.." install path.  In general, ConTeXt does not play
well for paths that have embedded spaces.

2.  the perl scripts search the PATH directories and supply a the full
pathname of programs (e.g., /texLive/bin/Win32/kpsewhich.exe) to perl's
backtick.  This failed when running texexec.exe in a command.com window,
Replaceing the "/" with "\" helps, but there were too many places to fix
in the time available, and meanwhile the disk on the system I was
borrowing died (due, I am quite sure, to overextertion caused by the
direct searching of the texmf trees for texexec.ini when kpsewhich failed
to run).

On Mandrake linux 9.0 and SGI Irix 6.5 TeXLive 2003 (full install) works
fine (using the current cont-tmf.zip which is a few days newer than the
version in TeXLive 2003).  The perl scripts have not changed.

> Earlier, when TeXLive 2003 was still in beta they left out texexec
> altogether.

On unix they just forgot to make some symlinks, the perl scripts were
there.  On Win32, I used Active State perl.exe to run the scripts.

> Has anyone else tried Context using graphics on TeXLive 2003? I hate
> to report a bug to Tug if my experience is unique. OTOH if the iso
> image is defective in some way I do need to let someone know pronto.

I'm not sure about the demo image.  If you are using Win32, does
texexec.exe find texexec.ini using kpsewhich?

-- 
George N. White III  <aa056@chebucto.ns.ca>

             reply	other threads:[~2003-10-14 23:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 23:11 George N. White III [this message]
2003-10-15 22:53 ` John Culleton
2003-10-16  0:43   ` Hans Hagen
     [not found] ` <Pine.LNX.4.58.0310141954530.2121@cerberus.cwmannwn.nowhere >
2003-10-16  0:38   ` Hans Hagen
2003-10-16 11:31     ` George N. White III
  -- strict thread matches above, loose matches on Subject: below --
2003-10-13 20:59 John Culleton
2003-10-14 19:04 ` Hans Hagen

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=Pine.LNX.4.58.0310141954530.2121@cerberus.cwmannwn.nowhere \
    --to=aa056@chebucto.ns.ca \
    --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).