#6495: Build the reference manual incrementally
-----------------------------+----------------------------------------------
Reporter: mpatel | Owner: tba
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-4.7.2
Component: documentation | Keywords:
Work_issues: | Upstream: N/A
Reviewer: Volker Braun | Author: Mitesh Patel
Merged: | Dependencies:
-----------------------------+----------------------------------------------
Changes (by vbraun):
* reviewer: => Volker Braun
* milestone: => sage-4.7.2
Comment:
In an ideal world sphinx would be multithreaded, but we probably shouldn't
wait for that ;-) The remaining issues about disk space, bibliographic
references, and needing two runs seem to be unavoidable. Building parallel
gets more and more important, so I think the benefits outweigh the
disadvantages.
I tried the patch on Sage-4.7.1.alpha4 without any other patches applied:
* Only the main page has proper css. For example,
`html/en/reference/cmd/index.html` refers to `_static/sage.css` but the
correct path would be `../_static/sage.css`.
* patch conflicts with #11251 (todo extension). Given that the latter is
already positively reviewed, maybe this ticket could be rebased on top of
it?
* During the sage build, I think we should then run the docbuilder twice
for the reference manual. Perhaps this should always be done for `sage
-docbuild all`.
* Can we make output less verbose? The whole intersphinx output scrolled
forever off my screen. Ideally, an interspinx failure to find an inventory
file would only add one extra line at the end of the build along the lines
of "You should re-run docbuild to get references right."
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6495#comment:13>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
