[PYTHON DOC-SIG] Bill Janssen suggested...

[Bill Janssen]

The missing part is a generalization of the specific tools we've written
for ILU.  Right now, a Perl script translates our ILU-specific markup
into the texinfo generic markup, with the translations hard-wired into
the script.  This should be re-written as a Python program which takes
arbitrary macro definitions of the form

	@macro		<string1>		<string2>

which means ``translate the markup @<string1>{foobar} into
@<string2>{foobar}'', and simply replaces them.  So the documentation
writer would write

	...and so we can see that the function @Python{@fn{foobar}} will cause
effects which...

and what the already existing texinfo processors will see is

	...and so we can see that the function @code{@code{foobar}} will cause
effects which...

Bill

=================
DOC-SIG  - SIG for the Python Documentation Project

send messages to: doc-sig@python.org
administrivia to: doc-sig-request@python.org
=================