percious schrieb:
Thanks George,
Is the code at googlecode most update with what is in the python svn?
I just want to make sure I am updating the correct thing before I go
making a branch of an older version.
I don't know -- the Google repo isn't managed by me. But from the commit
date it
On Mon, Oct 27, 2008 at 12:34 PM, Georg Brandl [EMAIL PROTECTED] wrote:
Andrew schrieb:
Hi,
I was hoping to use the ifconfig to build slightly different versions
of my documentation (for different platforms).
I put the following code in my .rst file:
.. ifconfig:: livecd
Some
I have some generic information I would like to include in a preface
for a manual I'm converting to PDF (stuff like Intended Audience,
etc.).
If I format my index.rst file like:
###
Book Title
###
==
Intended Audience
==
Describe people who
Hello,
Since I recently joined this list, I thought I'd introduce myself. I'm
a technical writer at Enthought, where we're now using Sphinx for
documentation of our open-source libraries, as Gael and Chris C have
recently posted. (Hi Gael! Hi Chris! waves)
I'm very interested in the problem of
Nice! Thanks.
On Wed, Oct 29, 2008 at 2:55 AM, Georg Brandl [EMAIL PROTECTED] wrote:
I fully agree with you. I've already fixed this on trunk. Color is now only
applied if $COLORTERM is set, or $TERM contains xterm or color. Most
terminals supporting color I've looked at work with this spec.
On that subject, it seems like the markup
###
Section Title
###
is declared in the sphinx docs as a section, but the result in the table
of contents looks like just another chapter. Is there a way to have it stand
out as a section?
Thanks.
On Wed, Oct 29, 2008 at 8:05 AM, Doug
On Tue, Oct 28, 2008 at 5:47 PM, Gael Varoquaux
[EMAIL PROTECTED] wrote:
Hi sphinx-devs (Hi Georg),
As our documentation is gorwing, we are starting to have a fairly deep
tree of sections:
http://code.enthought.com/projects/mayavi/docs/development/html/mayavi/
As a result the table of
