Re: Finding the Reason xdvi Output Disappeared

2005-10-26 Thread Rich Shepard

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
Applied Ecosystem Services, Inc. (TM) |  Impact Assessments Using Fuzzy Logic"
 Voice: 503-667-4517 Fax: 503-667-8863


Re: Finding the Reason xdvi Output Disappeared

2005-10-26 Thread Andre Berger
* 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 looking for libt1.so.1, and the current 
> version
> of the library is libt1.so.5.1.0. The upgrade made the proper soft link so
> that libt1.so.5 points to the executable's node, but xdvi can't use that. I
> made an additional soft link and now xdvi is happy. So am I.

Glad you solved it.

-Andre


Re: Finding the Reason xdvi Output Disappeared

2005-10-26 Thread Rich Shepard

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.5.1.0. The upgrade made the proper soft link so
that libt1.so.5 points to the executable's node, but xdvi can't use that. I
made an additional soft link and now xdvi is happy. So am I.

Rich

--
Dr. Richard B. Shepard, President |   Author of "Quantifying Environmental
Applied Ecosystem Services, Inc. (TM) |  Impact Assessments Using Fuzzy Logic"
 Voice: 503-667-4517 Fax: 503-667-8863


Re: Finding the Reason xdvi Output Disappeared

2005-10-26 Thread Andre Berger
* 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,
> however, I wrote a short article and tried to view the output by pressing
> ctrl-d. The status line shows the compiler at work, but there is no display.
> 
>   Here's the log file:
> 
> This is TeX, Version 3.14159 (Web2C 7.4.5) (format=latex 2003.3.8)  26 OCT 
> 2005 09:27
> **st-andrews-prize.phase-1.tex
[...]
> Output written on st-andrews-prize.phase-1.dvi (2 pages, 4388 bytes).
> 
>   So, why don't I see anything?

You have to define a viewer like 

\format "dvi" "dvi" "DVI" "D" "xdvi" ""

in ~/.lyx/preferences

-Andre


Re: Finding the Reason xdvi Output Disappeared

2005-10-26 Thread Rich Shepard

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.


This is what you get for upgrading.  Whatever happened to "if it ain't
broke, don't fix it"? :-)


  Well, one of the major benefits of Slackware -- for me -- is that it's far
back from the bleeding edge. I upgrade only when Patrick releases a new suite
of packages; otherwise, only security patches are applied. Unlike others, I
don't run daily or weekly upgrades for apt-get, up2date, or yum.

  There's another way of looking at that old wives' tale: "if it ain't broke,
break it." :-) That's how we progress.

Many thanks,

Rich

--
Dr. Richard B. Shepard, President |   Author of "Quantifying Environmental
Applied Ecosystem Services, Inc. (TM) |  Impact Assessments Using Fuzzy Logic"
 Voice: 503-667-4517 Fax: 503-667-8863


Re: Finding the Reason xdvi Output Disappeared

2005-10-26 Thread Paul A. Rubin

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 the output by pressing
ctrl-d. The status line shows the compiler at work, but there is no 
display.


  Here's the log file:

This is TeX, Version 3.14159 (Web2C 7.4.5) (format=latex 2003.3.8)  26 
OCT 2005 09:27

**st-andrews-prize.phase-1.tex
(./st-andrews-prize.phase-1.tex
LaTeX2e <2001/06/01>
Babel  and hyphenation patterns for american, french, german, 
ngerman, n

ohyphenation, loaded.

(/usr/share/texmf/tex/latex/base/article.cls
Document Class: article 2001/04/21 v1.4e Standard LaTeX document class
(/usr/share/texmf/tex/latex/base/size10.clo
File: size10.clo 2001/04/21 v1.4e Standard LaTeX file (size option)
)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/share/texmf/tex/latex/psnfss/palatino.sty
Package: palatino 2002/09/08 PSNFSS-v9.0a (SPQR) ) 
(/usr/share/texmf/tex/latex/base/fontenc.sty

Package: fontenc 2001/06/05 v1.94 Standard LaTeX package
(/usr/share/texmf/tex/latex/base/t1enc.def
File: t1enc.def 2001/06/05 v1.94 Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 38.
)) (/usr/share/texmf/tex/latex/base/inputenc.sty
Package: inputenc 2001/07/10 v0.99a Input encoding file 
(/usr/share/texmf/tex/latex/base/latin1.def
File: latin1.def 2001/07/10 v0.99a Input encoding file )) 
(/usr/share/texmf/tex/latex/fancyhdr/fancyhdr.sty

\headwidth=\dimen103
) (/usr/share/texmf/tex/generic/babel/babel.sty
Package: babel 2001/03/01 v3.7h The Babel package
(/usr/share/texmf/tex/generic/babel/english.ldf
Language: english 2001/04/15 v3.3l English support from the babel system
(/usr/share/texmf/tex/generic/babel/babel.def
File: babel.def 2001/03/01 v3.7h Babel common definitions
[EMAIL PROTECTED]
[EMAIL PROTECTED]
)
[EMAIL PROTECTED] = a dialect from [EMAIL PROTECTED] ))
No file st-andrews-prize.phase-1.aux.
\openout1 = `st-andrews-prize.phase-1.aux'.

LaTeX Font Info:Checking defaults for OML/cmm/m/it on input line 18.
LaTeX Font Info:... okay on input line 18.
LaTeX Font Info:Checking defaults for T1/cmr/m/n on input line 18.
LaTeX Font Info:... okay on input line 18.
LaTeX Font Info:Checking defaults for OT1/cmr/m/n on input line 18.
LaTeX Font Info:... okay on input line 18.
LaTeX Font Info:Checking defaults for OMS/cmsy/m/n on input line 18.
LaTeX Font Info:... okay on input line 18.
LaTeX Font Info:Checking defaults for OMX/cmex/m/n on input line 18.
LaTeX Font Info:... okay on input line 18.
LaTeX Font Info:Checking defaults for U/cmr/m/n on input line 18.
LaTeX Font Info:... okay on input line 18.
LaTeX Font Info:Try loading font information for T1+ppl on input 
line 18.

(/usr/share/texmf/tex/latex/psnfss/t1ppl.fd
File: t1ppl.fd 2001/06/04 font definitions for T1/ppl.
)
LaTeX Font Info:External font `cmex10' loaded for size
(Font)  <12> on input line 22.
LaTeX Font Info:External font `cmex10' loaded for size
(Font)  <8> on input line 22.
LaTeX Font Info:External font `cmex10' loaded for size
(Font)  <6> on input line 22.

LaTeX Warning: No \author given.

[1

] [2] (./st-andrews-prize.phase-1.aux) ) Here is how much of TeX's 
memory you used:

 899 strings out of 95847
 9400 string characters out of 1195949
 59003 words of memory out of 101
 3872 multiletter control sequences out of 1+5
 10896 words of font info for 28 fonts, out of 50 for 1000
 14 hyphenation exceptions out of 1000
 30i,10n,43p,185b,333s stack positions out of 
1500i,500n,5000p,20b,5000s


Output written on st-andrews-prize.phase-1.dvi (2 pages, 4388 bytes).

  So, why don't I see anything?

Rich

Best guess(es): either the upgrade munged xdvi, or the path to xdvi that 
LyX is using is wrong.  To rule out the first, try exporting the doc as 
a DVI and then running xdvi against it manually.


This is what you get for upgrading.  Whatever happened to "if it ain't 
broke, don't fix it"?  :-)


Paul