Em Ter 07 Mar 2006 10:11, Georg Baum escreveu:
> Angus Leeming wrote:
> > Having "dvi2 as an extension" might be a problem on Windows because
> > Windows uses the extension to determine the file type. Ie, clicking on
> > foo.dvi will open up the .dvi file inside of YAP but clicking on foo.dvi2
> > wouldn't. There's no such concept as magic numbers in Windows IIUC. Dunno
> > if this is actually a problem of course...
>
> I don't think that it is a problem: These files are only generated in the
> temp dir, and the appropriate viewer is invoked with the full name. The
> dvi2 format is never used for exporting in my patch.

It would only be a problem if the dvi-reading aplication refuses to load the 
file based on the extension. Unfortunately this is the case with yap (version 
2.4.1398), I just tested it in wine. Trying to load test.dvi2 makes it look 
for test.dvi2.dvi. Maybe the solution for this could be create a "composite 
extensions" ss.dvi (ss for source specials), so that the generated dvi file 
would be test.ss.dvi?

I will research on this today.

> Georg

João.

Reply via email to