On 03/06/2011 9:31 AM, Michal wrote:
On Wed, 1 Jun 2011 19:49:47 +0200
Enrico Forestieri<for...@lyx.org>  wrote:

[...]
The point is that if the TeX engine does not support spaces in
filenames the check is going to fail. Now, recent MikTeX versions
support spaces in filenames, but old ones do not, for example. Then,
there may be other engines not allowing spaces. As it is now, the
check would fail only if the file system does not provide for short
names *and* the TeX engine does not support spaces in file names,
giving a much lower probability of failure.
     You're right, I forgot about this case.

     But the problem still remains then. This could be a big one, because
the user has no clue about what is going on (like me while writing the
first post). I can think of no both automatic and 'elegant' solution to
this case, but the 'manual' one (done by user) would be trivial: he/she
needs to point to the path without spaces via a TEMP env. variable,
reconfigure LyX... and that's all.

     To sum this up: the situation could be easily detected (by checking
whether both the final inpname contains spaces and TeX does not support
spaces). Because it cannot be correctly fixed without the user
intervention, I'd strongly suggest to introduce some hint to the user
instead. Something along the lines of ...

     'As of now, LaTeX documents using external resources will fail to
see these and therefore will sometimes even refuse to compile. To fix
this, set the TEMP environment variable to the path without spaces in it
(via My Computer ->  Properties ->  Advanced ->  Environment Variables),
re-run LyX and select Tools ->  Reconfigure to fix the problem. [OK]'.

Regards,
MichaƂ


I didn't follow the thread but I am just wondering about your suggested user hint. Do you suggest that such a message should appear in a popup window when configure.py fails, or that it should appear as a warning in the documentation somewhere?

If in the doc, then where? It sounds like this could appear in a "Troubleshooting" section, but I don't think we have any such section in our doc.

--
Julien

Reply via email to