Re: [MiKTeX] yap rendering bugs?

[George N. W. I. <gn...@gm...>]

On Fri, Apr 4, 2008 at 6:13 AM, Ulrike Fischer <li...@ni...> wrote:

> am Donnerstag, 3. April 2008 um 18:47 schrieb andrea lamorgese:
>
>
>  > Ok, sorry. Here the minimum failing example.
>  > Where failing stands for YAP is failing to render: it was the
>  > subject, correct? In other words, I wrote in my first thread that
>  > compiling intopdf wasn't a problem. Still, using a dvi viewer gives
>  > the opportunityto use the inverse search which is a feature I appreciate very much.
>
>  > Thanks. Andrea
>
>  > \documentclass[11pt]{article}
>  > \usepackage{epsfig,a4wide,harvard,latexsym,amsfonts,booktabs,verbatim,amssymb,amsmath}
>  > \begin{document}
>  > \section{Papers ended - 2007}
>  > pippo
>  > \subsection{Bla bla bla?}
>  > pluto
>  > \section{Work in progress 2007}
>  > \noindent \large{\textbf{\underline{NYC}}}
>  > \subsection{Barf barf barf}
>  > paperino
>  > \section{Papers in  2008}
>  > \end{document}
>
>  It compiles fine on my PC and Yap has no problems to render it but I
>  have miktex 2.7.
>
>  I can see only two reasons why you should get ghostscript errors: a
>  problem with the graphics driver or a problem with a font. What
>  happens if you use e.g. \usepackage{lmodern} or \usepackage{mathptmx}
>  or \usepackage[T1]{fontenc} instead?
>
>  What drivers is epsfig loading? (look in the log).
>
>  If you run your document with pdflatex what fonts are listed at the
>  end of the log?
>
>  Do you have a gsview/ghostscript installed? Do you get errors if you
>  use the route latex->dvips->gsview? (look in gsview in the ghostscript
>  messages!). If yes you could put the ps somewhere on the net together
>  with logs of the pdflatex run and the latex run.
>
>  Also try to shorten the list of packages a bit more but make sure that
>  during all tests in YAP the render modus is set to dvips (that's
>  important).

All sound advice.  I can only add:

This looks like some configuration problem with mgs (MiKTeX's own
version of ghostscript).  Do you have anything installed in c:\gs?
This is the default location for ghostscript and is compiled into
miktex's mgs.  Open a cmd window and type "set".  Do you see any
variables that contain GS?  Some 3rd party apps that use ghostscript
may set environment variables that conflict with the use of ghostscript
in MiKTeX.

Probably your best bet is to upgrade MiKTeX to 2.7, but this may not
work if the problem is caused by conflicts with some other ghostscript
install.  If you wish to resolve the problem with ghostscript, there are
facilities for debugging that are explained in the ghostscript manual,
but most require running mgs from the command line, which in turn
requires that you do some additional configuration, see:

<http://dojo.miktex.org/blogs/christian_schenk/archive/2005/04/07/3.aspx>

(old, so may need some changes for the current version).

-- 
George N. White III <aa...@ch...>
Head of St. Margarets Bay, Nova Scotia