dvipsone and PSTricks (fwd)

Mon Jun 13 10:47:35 CEST 2005

C.P. Kwong writes:
>
> Dear Christina,
>
> Thanks for your prompt response.

Well, it's easy to send a prompt response when all you want is for the
person to do more work first ;-)

Notice that I've cc'd this reply to yandytex -- I hadn't noticed that
my initial reply to you didn't get copied to yandytex, and we want all
these discussions to go there, so that not only other can help ... but
they can correct anything I may say ;-)

And all e-mail to yandytex is archived, so when (let's be positive,
and not say `if' ;-) ) your query's been answered, anyone else with
the same or similar problem can benefit from this ... and we won't
have to do it from scratch again ;-))

> The followings are two log files.  However, I am not sure which ini
> file you were referring to.

The dviwindo.ini file is _outside_ the c:\yandy tree on your computer
-- try looking for it in c:\winnt or c:\windows -- or just use your
machine's search utility for the file. Be aware that it's easy to
overlook if your screen is full of subfolders -- they get listed
before files when you look at the contents to any folder.

But that's the file we're talking about. When you install Y&YTeX, all
the answers to those dialog box queries get recorded in the .ini
file. When you make subsequent changes to some of those initial
settings, via DVIWindo itself, those updates get recorded to the .ini
file. So it keeps track of the paths, parameters, and so on.

And on occasion, it hold the key as to why something's not being
found, esp. if you _know_ that the file(s) is/are on the machine.

So that's why we often ask for it.

I've not got a lot of time right now, so I'll quickly look through
your .log files to see if I spot anything. And perhaps other yandytex
readers will have some ideas as well. You thought it was a
PSTricks-related issue, so I'm going to look for `pstricks' stuff
specifically.

> Thanks again.

Well ... let's see if we can help ... before you thank us ;-))

Oh, one more thing. Sometimes the order of loading packages can be
significant. Normally, one likes to get graphics-related stuff
(graphics, color, pstricks, etc.) out of the way first, then load
things which are perhaps more `local' in nature -- I suspect there's a
proper TeXnical explanation for separating packages into broad
categories ... again, maybe someone on yandytex can give us some
pointers.

But for now, let's see what's being loaded.

> CP
>
> Here is the log file of LaTeX:
> *****************************************************************
> ...
> This is TeX, Version 3.14159 (Y&Y TeX 2.2.4) (format=latex 2000.9.5)
> 2005 JUN 13 11:02

OK. So you have version 2.2.4.

> **+latex ExampleAzure.tex
> (C:/yandy/YANDYTEX/FMT/latex.fmt)
> (ExampleAzure.tex
> LaTeX2e <2000/06/01>

And now here are all the packages you're loading -- jeez! That's a lot
of packages!

> (c:/yandy/tex/latex/contrib/other/prosper/prosper.cls
> Document Class: prosper 2001/01/23, v. 1.1
> (c) 2000 Frederic Goualard, CWI, The Netherlands
> CVSId: $Id: prosper.cls,v 1.5 2001/01/31 10:20:44 exupery Exp $
>
> (c:/yandy/tex/latex/contrib/other/seminar/seminar.cls
> Document Class: seminar 1997/10/13, 1.4
> Document Style: `seminar' v1.4 <1997/10/13> (tvz)
> ...
> (c:/yandy/tex/latex/unpacked/article.cls
> Document Class: article 2000/05/19 v1.4b Standard LaTeX document class
> (c:/yandy/tex/latex/unpacked/leqno.clo
> File: leqno.clo 1998/08/17 v1.1c Standard LaTeX option (left equation numbers)
> ) (c:/yandy/tex/latex/unpacked/size10.clo
> File: size10.clo 2000/05/19 v1.4b Standard LaTeX file (size option)
> )
> ...
> ) (c:/yandy/tex/latex/contrib/other/seminar/sem-page.sty)
> ...
> (c:/yandy/tex/latex/contrib/other/seminar/semcolor.sty
> Style Option: `semcolor' for doc style `seminar' 1.0 <93/04/01> (tvz)
> (c:/yandy/tex/latex/contrib/other/pstricks/generic/pstricks.tex
> `PSTricks' v1.07  <2005/05/06> (tvz)

OK. So here's the updated pstricks.tex file ...

> ...
> (C:/YANDY/TEXINPUT/pstricks.con)
> ...
>  (C:/YANDY/TEXINPUT/pstricks.con)))

And pstricks.con is being loaded twice ... hmmm ... I don't think such
things are normally a problem -- it's just a curiosity I'm noting.

> (c:/yandy/tex/latex/contrib/other/seminar/semlayer.sty
> ...
> (c:/yandy/tex/latex/required/graphics/graphicx.sty
> Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR)
>
> (c:/yandy/tex/latex/required/graphics/keyval.sty
> Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
> ..
> (c:/yandy/tex/latex/required/graphics/graphics.sty
> Package: graphics 1999/02/16 v1.0l Standard LaTeX Graphics (DPC,SPQR)
>
> (c:/yandy/tex/latex/required/graphics/trig.sty
> Package: trig 1999/03/16 v1.09 sin cos tan (DPC)
> )
> (c:/yandy/tex/latex/required/graphics/graphics.cfg)
> Package graphics Info: Driver file: dvipsone.def on input line 80.
>
> (c:/yandy/tex/latex/required/graphics/dvipsone.def
> File: dvipsone.def 1999/02/16 v3.0i Driver-dependant file (DPC,SPQR)
> ))
> ...
> (c:/yandy/tex/latex/contrib/supported/hyperref/hyperref.sty
> Package: hyperref 2001/04/05 v6.71e Hypertext links for LaTeX
> ...
> (c:/yandy/tex/latex/contrib/supported/hyperref/pd1enc.def
> File: pd1enc.def 2001/04/05 v6.71e Hyperref: PDFDocEncoding definition (HO)
> )
> Package hyperref Info: Option `bookmarks' set `true' on input line 1603.
> Package hyperref Info: Option `pdffitwindow' set `true' on input line 1603.
> Package hyperref Info: Option `pdfcenterwindow' set `true' on input line 1603.
> Package hyperref Info: Bookmarks ON on input line 1661.
> Package hyperref Info: Hyper figures OFF on input line 1680.
> Package hyperref Info: Link nesting OFF on input line 1685.
> Package hyperref Info: Hyper index ON on input line 1688.
> Package hyperref Info: Plain pages ON on input line 1693.
> Package hyperref Info: Backreferencing OFF on input line 1700.
>
> Implicit mode ON; LaTeX internals redefined
> (c:/yandy/tex/latex/contrib/other/misc/url.sty
> Package: url 1999/03/02  ver 1.4  Verb mode for urls, email addresses, and file
>  names
> )
> LaTeX Info: Redefining \url on input line 1905.
> ...
> Package hyperref Info: Hyper figures OFF on input line 2351.
> Package hyperref Info: Link nesting OFF on input line 2356.
> Package hyperref Info: Hyper index ON on input line 2359.
> Package hyperref Info: backreferencing OFF on input line 2366.
> Package hyperref Info: Link coloring OFF on input line 2371.
> ...
> *hyperref using driver hdvips*
> (c:/yandy/tex/latex/contrib/supported/hyperref/hdvips.def
> File: hdvips.def 2001/04/05 v6.71e Hyperref driver for dvips
>
> (c:/yandy/tex/latex/contrib/supported/hyperref/pdfmark.def
> File: pdfmark.def 2001/04/05 v6.71e Hyperref definitions for pdfmark specials
> ...
> (c:/yandy/tex/latex/unpacked/ifthen.sty
> Package: ifthen 1999/09/10 v1.1b Standard LaTeX ifthen package (DPC)
> )
> ..
> (c:/yandy/tex/latex/contrib/other/prosper/PPRazure.sty
> Package: PPRazure 2000/04/18
>
> Azure style for Prosper ---
> (c) 2000 Frederic Goualard, IRIN, France
> CVSId: $Id: PPRazure.sty,v 1.1.1.1 2000/11/28 11:15:11 exupery Exp $
>
> (c:/yandy/tex/latex/contrib/other/pstricks/latex/pst-grad.sty
> (c:/yandy/tex/latex/contrib/other/pstricks/latex/pstricks.sty
> Package: pstricks 2004/05/12 v0.2l LaTeX wrapper for `PSTricks' (RN,HV)

Ok. So pstricks.sty is being loaded as well, but not the same version
number or date as pstricks.tex, loaded earlier. Does anyone have any
comments on this age difference? Is it significant, or are the two
files in fact the latest versions?

> (c:/yandy/tex/latex/required/graphics/color.sty
> Package: color 1999/02/16 v1.0i Standard LaTeX Color (DPC)
>
> (c:/yandy/tex/latex/required/graphics/color.cfg)
> Package color Info: Driver file: dvipsone.def on input line 125.
> ))
> Package: pst-grad 2004/07/15 package wrapper for pst-grad.tex
>
> (c:/yandy/tex/latex/contrib/other/pstricks/generic/pst-grad.tex
>  v1.04, 2004/06/24
> ...
> File: pst-grad.tex 2004/06/24 1.04 `pst-grad' (tvz)
> ) (c:/yandy/tex/base/amstex/amssymb.sty
> Package: amssymb 1996/11/03 v2.2b
>
> (c:/yandy/tex/base/amstex/amsfonts.sty
> Package: amsfonts 1996/11/03 v2.2c
> ...
> (c:/yandy/tex/latex/required/psnfss/times.sty
> Package: times 2000/01/12 PSNFSS-v8.1 Times font as default roman (SPQR)
> ))
> ...
> (c:/yandy/tex/latex/required/amslatex/math/amsmath.sty
> Package: amsmath 2000/07/18 v2.13 AMS math features
> ...
> For additional information on amsmath, use the `?' option.
> (c:/yandy/tex/latex/required/amslatex/math/amstext.sty
> Package: amstext 2000/06/29 v2.01
>
> (c:/yandy/tex/latex/required/amslatex/math/amsgen.sty
> File: amsgen.sty 1999/11/30 v2.0
> ...
> (c:/yandy/tex/latex/required/amslatex/math/amsbsy.sty
> Package: amsbsy 1999/11/29 v1.2d
> ...
> (c:/yandy/tex/latex/required/amslatex/math/amsopn.sty
> Package: amsopn 1999/12/14 v2.01 operator names
> )
> ...
> ) (ExampleAzure.aux)
> ...
> (c:/yandy/tex/latex/required/psnfss/yyadd/ot1ptm.fd
> Fontdef file produced from: `yandytex.dtx' 1.4 (97/10/01) (SPQR)
> LaTeX Font Info:    File OT1ptm.fd loading Adobe TimesRoman on input line 24.
> )
> Package hyperref Info: Link coloring OFF on input line 20.
>
> (c:/yandy/tex/latex/contrib/supported/hyperref/nameref.sty
> Package: nameref 2001/01/27 v2.19 Cross-referencing by name of section
> ...
> ) (ExampleAzure.out)
> (ExampleAzure.out)
> ...
>  (c:/yandy/tex/latex/required/psnfss/yyadd/t1ptm.fd
> Fontdef file produced from: `yandytex.dtx' 1.4 (97/10/01) (SPQR)
> ...
> (c:/yandy/tex/latex/amsfonts/umsa.fd
> File: umsa.fd 1995/01/05 v2.2e AMS font definitions
> ...
>  (c:/yandy/tex/latex/amsfonts/umsb.fd
> File: umsb.fd 1995/01/05 v2.2e AMS font definitions
> )
> [1
>
>
> ] (ExampleAzure.aux) )

And it bombs out at the very first page ... ok. Well, that might argue
for the packages being the problem, rather than any specific code --
TeX's hardly had a chance to read your file ;-)

> ...
>
> Output written on C:/yandy/TEX/LATEX/CONTRIB/OTHER/prosper/doc/doc-examples/Exa
> mpleAzure.dvi (1 page, 8752 bytes).

And that one page of output, does it print at all? The GSView is for
previewing, which apparently isn't successful, so I'd guess the
printer isn't have much more luck, right?

As for the next log file, I don't know anything GSView messages at
all, so let's pass that one on to the others. On the other hand, it
looks like GSView can't find files because perhaps it/DVIWindo don't
know where to look?

Or, more simply, if the .dvi file can't be properly created, GSView
isn't going to have anything useful to work with, so its complaint are
all related to the .ps not being properly formed either.

There seem to be two types of error messages: about things being
`Unkown in Comments section ...', and about font files.

> *****************************************************************
>
> Here is the log file of GSView:
> *****************************************************************
> GSview 4.3 2002-04-30
> Unknown in Comments section at line 9:
>   %%DocumentSuppliedResources:
> ...
> Can't find (or can't open) font file /Resource/Font/cmr12.
> Can't find (or can't open) font file cmr12.
> Substituting font Courier for cmr12.
> ...