[OS X TeX] TeXniscope DVI display bug?

Claus Gerhardt gerhardt at math.uni-heidelberg.de
Sat Nov 18 02:59:34 CET 2006


I typeset the document with altpdflatexc and opened the pdf file (dvi- 
 >pdf) in Acrobat which clearly showed 8.5x11 in^2.

The underlying tex is texlive 2005.

Claus


On Nov 18, 2006, at 1:43, Christopher Menzel wrote:

> Well, that's an improvement, as it centers the text on the page  
> both vertically and horizontally, which was not the case before  
> (the text was slightly offset up and to the left) but I'm still  
> getting what appears to be A4.  Here's a screenshot, showing a PDF  
> (generated by pdflatex) side by side with the DVI file generated  
> from the same LaTeX document.
>
> -chris
>
> On Nov 17, 2006, at 6:17 PM, Claus Gerhardt wrote:
>
>> Use the command
>> \special{papersize=8.5in,11in}
>>
>> or whatever are the dimensions of letter paper immediately after  
>> the documentclass command.
>>
>> Claus
>>
>>
>> On Nov 17, 2006, at 21:34, Christopher Menzel wrote:
>>
>>> This *sounds* at first like a newbie problem, but I swear it  
>>> isn't! :-)  For reasons related to a problem I've been  
>>> experiencing with the simultaneous use of pdfsync and preview- 
>>> latex, I am using "latex -src-specials" to compile my LaTeX  
>>> documents.  This, of course, creates DVI files rather than PDF  
>>> files.  I am using TeXniscope to view these files, as it  
>>> preserves source specials info so I can have inverse search.   
>>> This works just fine, but for one thing:  when I view the file  
>>> with TeXniscope the file displays on what appears to be A4  
>>> paper.  Now I am long since familiar with the usual causes of  
>>> this, and of course reran texconfig,  both from the main menu and  
>>> the DVIPS menu, just to make sure I am using lettersize.  And if  
>>> I compile my documents with pdflatex instead, TeXniscope displays  
>>> them correctly as lettersize.  Also, if I save the file as a PDF  
>>> when it's displaying A4-ishly in TeXniscope, TeXniscope displays  
>>> the resulting file correctly!  And here's the clincher:  xdvi  
>>> displays the *very same* DVI file correctly.  TeXniscope warns  
>>> that problems with DVI display are usually traceable to dvipdfmx,  
>>> which it allegedly uses for rendering DVI.  However, the  
>>> TeXniscope preferences show the dvipdfm program to be /usr/local/ 
>>> TeXLive/bin/i386-apple-darwin-current/dvipdfm, and when I run  
>>> that from the command line on the raw DVI file, the resulting PDF  
>>> file also displays correctly.  (As an aside, dvipdfmx also  
>>> creates a PDF file that displays as lettersize, but the fonts  
>>> look horrible.)
>>>
>>> Anybody have any idea what's going on here?
>>>
>>> Chris Menzel
>
> ------------------------- Info --------------------------
> Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
>          & FAQ: http://latex.yauh.de/faq/
> TeX FAQ: http://www.tex.ac.uk/faq
> List Archive: http://tug.org/pipermail/macostex-archives/
>

------------------------- Info --------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
          & FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/




More information about the macostex-archives mailing list