Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> But _when_ is it set? In the preamble? We have code to differentiate >> dvi from pdf, do we want to allow people to shoot themselves in the >> foot by such means? > > In the testcases, people entered the command themselves. I think it does not > happen with our builtin hyperref support, since we care for the correct > driver. > > We could certainly say that this is a user problem, however, the extension > does not harm. And it has the extra bonus that png output is now also > supported if dvipng is not installed.
But why do we try to have latex flavors and all this stuff then? I think that the real problem is that, when we try to do the preview, we do no know whether the user intends to use PDF or DVI as an output format. If we did, we could use the right code path for previews. Indeed, it does not make sense to use dvi previews when all the user wants to do is use pdflatex all the time. This is one more reason for being able to declare the preferred output format in prefs. Then we could also have a meaningful 'Typeset' action that would output dvi or pdf according to this. And preview would be able to use this info. JMarc
