Angus Leeming wrote:
> I've just updated the list of bugs in LyX 1.3.6 that I know about. See
> http://wiki.lyx.org/Windows/LyX136pre#known_bugs
>
> Am I missing anything?
Yes. LyXWin 1.3.6 version 21 doesn't install. I get the error message:
LyXTextClassList::Read: unable to find textclass file `'. Exiting.
To reproduce this, delete the folder "lyx" in the Win folder "Documents
and settings" before you install LyX. (As if you have never installed
Lyx before).
> My feeling is that we should at least try and address the first two of
> these. I've been asked to put together a minimal test case for the
> YAP problem and to submit it to the MiKTeX bug tracker. I'm hoping
> that this does the trick but need to try it out on a Windows machine.
> \documentclass{article}
> \usepackage{graphicx}
> \begin{document}
> \insertgraphics{a_file_name_containing_more_than_220_chars.eps}
> \end{document}
> Maybe one of our Windows users can do this for me?
> http://sourceforge.net/tracker/?group_id=10783&atid=110783
I would do this but the Problem with Yap is not a bug in LyX.
Windows has a character limit for filenames. If you use a filename with
220 chars, export the LyX document to .tex, run then LaTeX, and open the
created file with yap no crash occurs. If you view the DVI from within
LyX yap crashes because the dvi file uses then the path
PSfile="F:/lyxdokumente/lyx/tmp/lyx_tmpdir1060a00924/lyx_tmpbuf0/_lyxdokumente_FILENAME.eps
(where FILENAME has 220 chars) and this is too long for ghostscript and
Windows. (Yap uses ghostscript libraries to show eps-files in dvi.)
You can also see this when you use the maximal char number for the
filename in Lyx. Then convert.exe fails to convert the image to ppm as
convert also uses ghostscript.
But anyway, who uses such long filenames? Should we take care about
this? If yes, we could limit the filename length allowed for LyX to 100
chars or so, but I don't think this solves the problem in general.
regards Uwe
