leif writes: >> ... [HP] W. C. Huffman, V. Pless, Fundamentals of Error-Correcting >> Codes, Cambridge Univ. Press, 2003. > > Well, first of all it is stupid to use such a short abbreviation, even > without a year. Presumably it was introduced when references were > local, so we may create a (meta-)ticket to change all of such occurrences.
Agreed. The inspiration for new developers in the Sage Development manual uses the citation label "[SC]": http://doc.sagemath.org/html/en/developer/coding_basics.html#documentation-strings >> Is this sort of mess the reason Sphinx is so terribly slow, I wonder... > > Well, not that long ago, docbuilding in parallel wasn't even possible > (h/t mostly John Palmieri IIRC, with a few others); before, the whole > reference manual had been one monolithic block. > > Of course the documentation keeps growing (and hence also Sphinx' memory > footprint and runtime), but it was IMHO always double dog-slow. But > especially building plot* gets slower and slower because people keep > adding more and more "nice" things I guess. > > To me the most annoying thing is that "make doc" (which ptestlong for > example for no reason depends on) meanwhile even takes ages when Sphinx > does nothing, or almost nothing, because nothing changed. (My recent > impression is though that some files accidentally get touched somehow, > such that they to Sphinx look modified. I can't give any concrete > example, just noticed.) Yes, doing `make doc` goes through every chapter of the manual, very carefully determining that nothing changed. I often use "./sage -docbuild reference/<chapter> html" instead, but that seems even more fragile than regular doc-building. Jeroen Demeyer writes: > General comment to all people complaining about Sphinx: reviewing > existing Sphinx-related tickets such as #20577 will show that you > actually care and will encourage other Sage developers to continue > working on Sphinx. Thanks for your work! Are there tickets (or upstream-not-merged-changes) which would make Sphinx faster or have better, less fragile incremental building? Best, Johan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
