From: "George N. White III" <aa056@chebucto.ns.ca>
Subject: Re: TeX Live 2003 miseries.
Date: Thu, 16 Oct 2003 08:31:25 -0300 [thread overview]
Message-ID: <Pine.SGI.4.58.0310160812460.39503@montigo.bio.dfo.ca> (raw)
In-Reply-To: <6.0.0.22.2.20031016023533.02a85bf0@server-1>
On Thu, 16 Oct 2003, Hans Hagen wrote:
> At 01:11 15/10/2003, you wrote:
>
> >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.
>
> http://www.pragma-ade.com/context/mswintex (just runsetuptex,bat in the
> path where it is)
> http://www.pragma-ade.com/context/linuxtex (run setuptex and generate formats)
>
> is the minimum that you need for context. For windows the trick is in using
> irun in the right way, i.e. either use a full path spec or something
> relative like ../../whatever (which is what i've done there); i didn't test
> it for "program files"
The other place where spaces cause problems is in the user's "HOME"
directory. TeXLive looks in %HOME%/texmf, and texexec creates a
texfilename.tmp with a reference to %HOME%. On my brief foray into WinXP
the default HOME location had a space. We are expecting a bunch of
Win9x users (currently with 4allTeX) to be converted to WinXP using
a departmental standard configuration, and I need a full TeX that will
play nicely with that (I did suggest that our users would be better
off running linux in vmware).
--
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia, Canada
next prev parent reply other threads:[~2003-10-16 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 23:11 George N. White III
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 [this message]
-- 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.SGI.4.58.0310160812460.39503@montigo.bio.dfo.ca \
--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).