On Wed, 7 Dec 2005 09:36:24 +0100,
Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> or just add a marker (in some for me unknown way), and postprocess
> the HTML files. I'm not sure the links does necessarily belong in e.g.
> PDF renderings of the documentation, but that's of course up to the
> documentation maintainers.
I'm just scared of hacking the LaTeX2HTML translator customizations,
and would rather do things to the LaTeX input.
> if anyone wants some data to play with, I've posted a simple seealso file
> here:
Thanks! I've written a little parser and output script; they're in
Python SVN at sandbox/trunk/seealso. (Browseable at
http://svn.python.org/view/sandbox/trunk/seealso/).
With a patch to the Makefile and the module's *.tex file, it's
possible to use these scripts to pull in examples. Modifying all the
*.tex files is tedious, but I suspect we can make it an automatic part
of the seealso environment. I'll talk to Fred about it and begin
assembling a patch.
--amk
--
http://mail.python.org/mailman/listinfo/python-list
