Uwe Stöhr wrote:
> Georg Baum schrieb:
>
>> It would probably not be difficult to fix that, the code is simple. In
>> fact, it will probbaly be less work to do that than to rip out all
>> appareances of clean_dvi from LyX and the installer.
>
> That means you will fix directly the programs dt2dv and dv2dt?
I did not mean it like that. Anybody could do that with a decent set of test
files (one file per problematic construct), but if you prepare such a set
of test files then I can have a look (but not very quickly).
>> They should not, since the created DVI without clean_dvi is not valid
>> DVI. clean_dvi tries to correct some problems of the TeX engine with
>> filenames with spaces.
>
> MiKTeX 2.5 fully supports filenames with spaces because it is installed
> by default under ~:\Program Files
> All cases I tested with MiKteX 2.5 work fine.
The installation directory does not mean anything in this case. What
clean_dvi fixes are included graphics with spaces in the name, e.g. from
the command
\includegraphics{"test file"}
>> It has nothing windows specific. It is used as default under windows
>> because windows users tend to use filenames with spaces more than others.
>
> It shouldn't be the default when now files with spaces are supported
> directly by the LaTeX-distributions.
I still doubt that we are talking about the same files with spaces problems.
> For example I remember the Ghostscript "very long path" bug. I reported
> it to the Ghostscript developers after it was reported here and in the
> next release they fixed it. We could have introduced in this case also a
> script that afterwards changes the Postscript output.
The difference is that the postscript file was 100% standard conformant, but
the DVI file that is not run through clean_dvi is not. Therefore it was
clearly a ghostscript bug, but in this case it is not a bug of yap and
colleagues.
> I was never a fan of clean_dvi.
Me neither, but it does a useful job. The problem is that if you "fix" DVI
viewers to interpret ps filenames reading "test file" to strip the quotes,
then that is a nonstandard extension to the DVI file format. If you send
such a file to somebody else you cannot be sure whether it works on his
machine.
Georg
