[cc'ing the list in case others might benefit as well...]
>>>>> "RM" == Ross Moore <[EMAIL PROTECTED]> writes:
RM> Ahh. It is a file called 1 that is aberrant.
RM>
RM> That '1' on the command-line was probably meant as a value for an
RM> option. Probably you got the syntax wrong, or...
This is stuff that has worked before and hasn't been changed...
RM> ...if you are using a Makefile, then the shell it uses isn't
RM> behaving in the way you were expecting.
...again, nothing here has changed. The makefile and shell are the
same as they've been for a while.
OK, so I bit the bullet and narrowed this thing down. It's something
in the parsing of \input. I noticed that the other stuff I translated
used no \input of style files (the comment below sort of explains why
I do this... is it no longer relevant?).
Consider the following...
\documentclass{report}
\usepackage{html}
% Personal packages. Have to use \input rather than usepackage so
% LaTeX2HTML will recognize them.
\input{/users/turner/BlueSky/manual/bug/bluesky}
\begin{document}
Blorp.
\end{document}
Simply doing (no makefile):
oneida% latex manual
oneida% latex2html manual
this bombs with the now-familiar:
*** processing declarations ***
OPENING /rndDISKS/oneida1/users/restricted/BlueSky/manual/bug/manual.tex
Cannot create directory manual: File exists
Reusing directory manual:
texexpand: Cannot open 1
texexpand failed: No such file or directory
If I change the input line from the absolute path to:
\input{bluesky}
and the file is either in the local dir or found by TEXINPUTS, it
works fine.
Does this help?
--
John A. Turner mailto:[EMAIL PROTECTED]
Senior Research Associate http://www.blueskystudios.com
Blue Sky | VIFX http://www.vifx.com
One South Road, Harrison, NY 10528 http://www.lanl.gov/home/turner
Phone: 914-381-8400 Fax: 914-381-9790/1
