On Wed, 26 Oct 2005, Andre Berger wrote:
Glad you solved it.
Andre,
Thanks! I am, too. Now I'm trying to learn why the error occurred in the
first place. I suspect it's the way xdvi was packaged.
Rich
--
Dr. Richard B. Shepard, President | Author of "Quantifying Environmental
Applie
* Rich Shepard <[EMAIL PROTECTED]>, 2005-10-26 21:20 +0200:
> On Wed, 26 Oct 2005, Andre Berger wrote:
>
> >You have to define a viewer like
> >\format "dvi" "dvi" "DVI" "D" "xdvi" ""
>
> No, that's not it. It turns out that apparently xdvi is behind the t1
> libraries. The application is l
On Wed, 26 Oct 2005, Andre Berger wrote:
You have to define a viewer like
\format "dvi" "dvi" "DVI" "D" "xdvi" ""
No, that's not it. It turns out that apparently xdvi is behind the t1
libraries. The application is looking for libt1.so.1, and the current version
of the library is libt1.so
* Rich Shepard <[EMAIL PROTECTED]>, 2005-10-26 18:40 +0200:
> I just upgraded all the systems here to Slackware-10.2. I've been busy
> developing beamer presentations (another one to be done in the next couple
> of
> weeks), so I've been viewing compiled output with pdflatex. Yesterday,
> howeve
On Wed, 26 Oct 2005, Paul A. Rubin wrote:
To rule out the first, try exporting the doc as a DVI and then running xdvi
against it manually.
Paul,
Sigh. Why didn't I think of this? (That's a rhetorical question, by the
way.) For some reason, the t1lib was not upgraded. No library, no display.
Rich Shepard wrote:
I just upgraded all the systems here to Slackware-10.2. I've been busy
developing beamer presentations (another one to be done in the next
couple of
weeks), so I've been viewing compiled output with pdflatex. Yesterday,
however, I wrote a short article and tried to view th
