Re: [PyX-devel] Problems building manual.pdf

[Andre W. <wo...@us...>]

Hi,

On 06.09.05, Michael Schindler wrote:
> > >! Undefined control sequence.
> > >\filenq #1->{\py@smallsize \textsf {\let \e
> > >                                            =\textbackslash #1}}
> > >l.44 ... for the data from file \file{graph.dat}.}
> > >
> > >?
> > >! Emergency stop.
> > >\filenq #1->{\py@smallsize \textsf {\let \e
> > >                                            =\textbackslash #1}}
> > >l.44 ... for the data from file \file{graph.dat}.}
> 
> I do not understand this either, but I had the same problem.
> Strange enough, if you define \e in any way, either using \def or
> 
>   \let\e=\textbackslash
> 
> at the beginning of graph.tex, there is no error anymore, and
> everything works.

It seems to depend on the pdftex version used. At least for my old
pdftex I'm using (it's version 1.10b from an old teTeX 2.02 or
something). However, Michaels work around seems to solve the issue, so
let's keep it for the moment.

On 06.09.05, Andrea Riciputi wrote:
> manual.pdf file didn't build correctly. It turned out that the  
> problem was twofold. First the manual/Makefile has got an error and  
> here it is the patch:
> 
> >*** /Users/andrea/Installs/Python/PyX-0.8.1/manual/Makefile.orig    
> >Tue Sep  6 16:43:38 2005
> >--- /Users/andrea/Installs/Python/PyX-0.8.1/manual/Makefile     Tue  
> >Sep  6 16:46:43 2005
> >***************
> >*** 22,28 ****   
> >pdf:manual.pdf                                                         
> >                                        html:manual/manual.html
> >! manual.pdf: $(src)
> >        #for index-with-own-hyperrefs debugging, anybody interested?
> >        #./mkhowto --a4 --pdf --keep manual.tex
> >        ./mkhowto --a4 --pdf manual.tex
> >--- 22,28 ----
> >  pdf:manual.pdf
> >  html:manual/manual.html
> >
> >! manual.pdf: $(src)  
> >eps                                                                    
> >                           #for index-with-own-hyperrefs debugging,  
> >anybody  
> >interested?                                                  #./ 
> >mkhowto --a4 --pdf --keep  
> >manual.tex                                                             
> >           ./mkhowto --a4 --pdf manual.tex

Well, I don't understand that. It is correct, that the pdf version of
the manual depends on the eps target. Note, that the pdf target just
runs all python files for the figures and they create a eps and a pdf
version of that very figure at the same time.

On 07.09.05, Michael Schindler wrote:
> Update of /cvsroot/pyx/pyx/manual
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17910
> 
> Modified Files:
> 	Makefile 
> Log Message:
> make manual.pdf depend on pdf (comment by Andrea Riciputi) figures and rename the figure rules
> 
> Index: Makefile
> ===================================================================
> RCS file: /cvsroot/pyx/pyx/manual/Makefile,v
> retrieving revision 1.22
> retrieving revision 1.23
> diff -C2 -d -r1.22 -r1.23
> *** Makefile	13 Aug 2005 12:24:11 -0000	1.22
> --- Makefile	7 Sep 2005 16:32:32 -0000	1.23
> ***************
> *** 6,10 ****
>   # for details).
>   
> ! default:dvi
>   
>   clean:
> --- 6,10 ----
>   # for details).
>   
> ! default: dvi
>   
>   clean:
> ***************
> *** 19,35 ****
>   src=$(wildcard *.tex) pyxversion.tex pyxdate.tex
>   
> ! dvi:manual.dvi
> ! pdf:manual.pdf
> ! html:manual/manual.html
>   
> ! manual.pdf: $(src)
>   	#for index-with-own-hyperrefs debugging, anybody interested?
>   	#./mkhowto --a4 --pdf --keep manual.tex
>   	./mkhowto --a4 --pdf manual.tex
>   
> ! manual.dvi: $(src) eps
>   	./mkhowto --a4 --dvi manual.tex
>   
> ! manual/manual.html: $(src) eps
>   	./mkhowto --image-type png --favicon "/pyx.ico" \
>   	          --up-link "/" --up-title "PyX homepage" \
> --- 19,35 ----
>   src=$(wildcard *.tex) pyxversion.tex pyxdate.tex
>   
> ! dvi: manual.dvi
> ! pdf: manual.pdf
> ! html: manual/manual.html
>   
> ! manual.pdf: $(src) pdf_figs
>   	#for index-with-own-hyperrefs debugging, anybody interested?
>   	#./mkhowto --a4 --pdf --keep manual.tex
>   	./mkhowto --a4 --pdf manual.tex
>   
> ! manual.dvi: $(src) eps_figs
>   	./mkhowto --a4 --dvi manual.tex
>   
> ! manual/manual.html: $(src) eps_figs
>   	./mkhowto --image-type png --favicon "/pyx.ico" \
>   	          --up-link "/" --up-title "PyX homepage" \
> ***************
> *** 42,48 ****
>   	python -c "import sys;sys.path[:0]=[\"..\"];import pyx.version;print pyx.version.date+'%'" > pyxdate.tex
>   
> ! eps: $(patsubst %.py, %.eps, $(wildcard *.py))
>   
> ! pdf: $(patsubst %.py, %.pdf, $(wildcard *.py))
>   
>   %.eps: %.py
> --- 42,48 ----
>   	python -c "import sys;sys.path[:0]=[\"..\"];import pyx.version;print pyx.version.date+'%'" > pyxdate.tex
>   
> ! eps_figs: $(patsubst %.py, %.eps, $(wildcard *.py))
>   
> ! pdf_figs: $(patsubst %.py, %.pdf, $(wildcard *.py))
>   
>   %.eps: %.py
> 

... but there seems to be no rule to create the actual pdf files. It
should be identical to the "%.eps: %.py" rule. While overall the eps
and pdf generation at the same time seems a bit strange to be handled
in the Makefile, it seems to have worked very well on an unbroken
pdftex all the time ...


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/