Re: [NTG-context] Re: problems with embedded spaces in file paths (Win32)
On Wed, 17 Sep 2003, George White wrote: > This is starting to look like too much work. We are supposed to > move from Win98 to WinXP "real soon now". Are these problems also > present for WinXP? For myself, *n*x works, but some groups rely on > Adobe Illustrator + Photoshop and understandably are reluctant to give > up Win32. I found out about this problem over a year ago and it was even discussed on this list, but nobody came up with a really working fix. So my solution in both my old WindowsNT and in my current Windows2000 (and my homeXP) has been NOT to install TeXLive in Program Files. Instead I have installed TeXLive directly under the root, i.e. I have a directory C:\TeXLive and that works fine. On my old desktop at work with WindowsNT I actually had TeXLive on the second partition for the while, i.e. at D:\TeXLive and even that worked fine. It does not seem to bother TeXLive ConTeXt that the .tex files are in a path with couple of spaces (like c:\Documents and Settings\Mari\My Documents\ConTeXt\test.tex) as long as TeXLive itself is installed somewhere without spaces. I know this is a workaround, but at least as long TeXLive is installed individually (not from the network, it is an easy solution. Just change to root directory in the beginning of the installation and everything else will work out. I don't really have any other options than the workaround or having somebody come up with a real fix, because the other users of "my" computers would be majorly annoyed if I went *n*x... Mari (mix-and-match Windows user, although in the Emacs school) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: problems with embedded spaces in file paths (Win32)
On Mon, 15 Sep 2003, Fabrice Popineau wrote: > > 1. on Win32, kpsewhich often fails to find texexec.ini. I created a > > I have applied a couple of patches to texexec and texutil. They are > attached. The Sept. 5th rc had the patches in texexec.pl, but not in texutil.pl. I don't think my files work enough to get to that section of texutil (I added some print statements around the patch and don't see any output). Now I have a problem with texfont, which reports: processing aborted: unknown tex root c:/program I applied the same recipe as in texutil: chop($fontroot); $fontroot = "\"$fontroot\"" if ($fontroot =~ m/^[^\"].* / ? "\"" : "") ; but now I get: processing aborted: unknown tex root "c:/program files/texlive/texmf-local" This is starting to look like too much work. We are supposed to move from Win98 to WinXP "real soon now". Are these problems also present for WinXP? For myself, *n*x works, but some groups rely on Adobe Illustrator + Photoshop and understandably are reluctant to give up Win32. -- George White <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> 189 Parklea Dr., Head of St. Margarets Bay, Nova Scotia B3Z 2G6 ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: problems with embedded spaces in file paths (Win32)
On Mon, 15 Sep 2003, Fabrice Popineau wrote:
> > 1. on Win32, kpsewhich often fails to find texexec.ini. I created a
>
> I have applied a couple of patches to texexec and texutil. They are
> attached.
This morning, on Win98, texexec.exe reliably failed to find texexec.ini.
I see that the full path of texexec.exe is passed into the backticks:
my $IniPath = `$own_quote$kpsewhich$own_quote --format="other text files"
-progname=context texexec.$suffix` ;
replacing "$kpsewhich" with "kpsewhich" got things working. I wonder
if this is some Win98 command buffer length issue. Is it necessary
to pass the full path (e.g., C:\PROGRA~1\TEXLIVE\BIN\WIN32\KPSEWHICH.EXE)?
> > 2. ConTeXt texexec uses $ENV{"HOME"} to set a value in filename.tmp,
> > e.g., on unix:
>
> I tried your example and this is what I get :
>
> C:\tmp>cat try.tmp
> % try.top
> \unprotect
> \setupoutput[pdftex]
> \setupsystem[\c!gebied={C:/Documents and Settings/popineau/My Documents/}]
> \setupsystem[\c!n=2]
> \setupsystem[inputfile=try.tex]
> \protect
>
> Which seems correct, isn't it?
My guess is that when kpathsea is failing, you are supposed to get a
message in "$HOME/cont-err", but instead you end up with text on an
extra page, something like:
and Settings/popineau/My Documents//cont-err
which suggests the error is likely written to C:/Documents.
I didn't have a chance to test your patch today.
Currently, texexec.pl tries a brute force search if kpathsea fails to find
texexec.ini or texexec.rme. On the Win98 PC I'm using, this search takes
much longer than I'm willing to wait. Would it be better to exit with a
suggestion that the user investigate the problem with kpathsea?
--
George N. White III <[EMAIL PROTECTED]>
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
