On Thu, 04 Jan 2007 21:41:43 -0800, Nick Alexander <[EMAIL PROTECTED]> wrote:
Before you spend too much time fixing such problems, I started
rewriting the ref manual generation code to make it easier to avoid
such issues.
Good! The current ref manual generator that I wrote
is desparately in need of a rewrite!
I'm not done; are you interested in helping?
Iftikhar Burhanuddin wrote:
Hi,
I believe the SAGE Reference Manual is constructed by pulling docstrings
from the source code.
[1] Is there a mechanism by which files are selected for their
function definitions, docstrings to be included/excluded in the
Manual. If all files are selected, why *don't* docstrings (for instance
for the funtion height()) from
devel/sage/sage/schemes/elliptic_curves/ell_point.py
show up in the manual?
AFAICT, files are included by touch-ing just the right tex file in
doc/ref. Why a certain function does not turn up, that I cannot say.
A given file also has to be input/included into ref.tex somehow.
Touching just makes sure that the tex version of the file is generated.
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
