#9128: Sphinx should be aware of all.py to find its links
-----------------------------------------------------+----------------------
Reporter: hivert | Owner: hivert
Type: enhancement | Status:
needs_work
Priority: major | Milestone:
sage-5.0
Component: documentation | Keywords: Sphinx
links
Work_issues: | Upstream: N/A
Reviewer: Andrey Novoseltsev, Nicolas M. Thiéry | Author: Florent
Hivert
Merged: | Dependencies: #11251,
#12490
-----------------------------------------------------+----------------------
Comment(by hivert):
Hi,
Replying to [comment:51 jdemeyer]:
> Let me clarify that this happened on sage.math, where the memory size is
set
> to 1500000. On a different system with 3000000 as limit, it compiled.
The
> end of that pdflatex log file shows:
'''`\begin{GROUMPH}`'''
First of all, I need to express my feelings: Fucking Sphinx, Fucking
Latex. None of these two software where seriously designed to scale to a
project of Sage size. That's a shame.
While I'm at it, fucking Sagemath distro. It worked without any problem on
my
laptop.
'''`\end{GROUMPH}`'''
Sorry for this non useful comment.
I'm quite angry and frustrated because what my patch does is only to fix a
huge bunch of missing links in Sage doc way before they are sent to the
docutil writer for HTML or TeX. My patch is working at the level of
docutil
abstract syntax tree, but I could have fixed those link by editing Sage
source
as well. This means that '''if''' the doc of Sage was correct, it
'''won't''' compile
either ! And now because I tried to fix the doc, I'm asked to fix LaTeX. I
don't think it is really fair.
> I don't really see a solution besides requiring people to change their
LaTeX
> installs, or splitting up the reference manual (would #6495 fix this?)
This also means that, whether or not we apply this patch, we '''will'''
hit the
same problem again, as the doc of Sage is expected to grow.
-------
Let's try to be more constructive. I see several solution:
- add a comment in Sage installation instructions saying that TeX
limitation
should be enhanced to compile the PDF doc (by the way, are there any
people
really using the PDF doc out there ?)
- is it really a hard limitation. Couldn't this be fixed by a shell
variable ?
I had the following script in my {{{~/bin}}} when I was using {{{XY-
pic}}}:
{{{
popcorn-*binat/doc/common $ cat ~/bin/hugetex
#!/bin/sh
#####################################
# Boosted TeX to compile withc XY-pic
export extra_mem_bot=8000000; tex $*
}}}
Jeroen: will you be so kind to try if this works ?
- I can maybe disable my link fixing code when we are compiling to PDF,
but I
think this is really a temporary bugware solution. Considering the time I
already lost on this ticket and the fact that this doesn't solve the
problem
but barely hide it, I don't think this is an acceptable solution.
Florent
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9128#comment:53>
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.
