Andi Albrecht wrote:
Hi Rafael,
I changed a few things in the Makefile to make PDF generation work.
The previous method for generating the PDF depends on passivetex which
isn't included in recent Debian releases and maybe in other
distributions too.
So I've changed the tut-pdf target (and the one for the spanish
version as well) to use dblatex. dblatex seems to be actively
maintained and very stable. I only had a problem about two missing TeX
declarations on my system at home, but this results from a un-clean
install of dblatex. Obviously something went wrong when upgrading from
Dapper Drake to Feisty Fawn, so that dblatex has found some wrong TeX
styles. On a clean system everything's ok and after installing native
dblatex on my computer at home the problems where gone.
The resulting PDF is about 4 MB large with ~340 pages, you can find it
here: http://andialbrecht.de/pygtk2-tut.pdf
dblatex has three built-in styles and i have choosen the most readable
one, in my opinion. You can change dblatex's "-T" switch in the
tut-pdf target to "native" or "simple" to have a look at the other two
styles. "native" is somewhat "nervous" and maybe intended as the usual
give-a-way for your customers and the margins in "simple" are too
large, so that the PDF isn't as readable as with the "db2latex" style
I've choosen.
The DocBook extensions used in the tutorial are covered in
pdf-dblatex.xsl, which replaces the other two pdf*.xsl's. Not all
extensions are coverd, but I think it's enough for a good looking
printable version. dblatex is even able to render some syntax
highlighting, but this requires a 'language="python"' attribute in
every programlisting that should be highlighted.
In addition to this I've made another modification on the Makefile:
There are some references to the obsolete CVS directories in the
pygtk2tutorial/* targets. I removed them.
A patch for all the changes is attached to this mail.
Let me know, what you think about this way to create the PDF.
Thanks a lot for doing this work!.
I have already applied the patch (I hope John Finlay is ok with it) to
the svn version.
Probably the pygtk reference and pygobject references could benefit from
a similar update (they're in the pygtk module), but they still need some
tweaks to the Makefile as some images that need to be included are
missing (these were left behind with the move from the pygtk-docs module
to the pygtk one). If you feel like giving it a try we'd be glad to
accept those changes.
Regards, and thanks a lot, again,
Rafael Villar Burke
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
