Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> 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. > > We cannot always guess this. It's not unlikely that some class or package > loads hyperref with the pdftex driver, or something similar, and neither the > user nor we are informed about that.
Are there really classes/packages that force the driver? > Anyway, my patch would also be needed if we would use the flavor, because it > implements general handling of pdftex preview. OK then. But we should be careful to avoid adding to much code to catter for whatever stupid thing people put in preamble. Would it be a good idea to add 'dvips' or 'pdftex' as global option of the document class depending on the flavour? This would mean that reasonable preamble users could load hyperref in preamble without caring for driver. >> This is one more reason for being able to declare the preferred output >> format in prefs. > > Why in prefs? I think this is highly document-dependent. Really in practice? I would be surprised that so many people switch between dvi and pdf all the time... JMarc
