John Hunter wrote:
> On Thu, Jun 12, 2008 at 7:47 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
>
>
>> Barring that, I suppose we'll have to a) drop the symbol table or b) use
>> mathtext to generate the math for LaTeX (there's something very patricidal
>> about that... ;). b) may be a litt
right, I agree : I tried because I did not know for sure whether it
would work or not, and because that was post-lunch time :) Looks
like bleeding edge sphinx is not required seemingly!
Johann
John Hunter wrote:
> On Thu, Jun 12, 2008 at 9:52 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote
On Thu, Jun 12, 2008 at 7:47 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Barring that, I suppose we'll have to a) drop the symbol table or b) use
> mathtext to generate the math for LaTeX (there's something very patricidal
> about that... ;). b) may be a little bit of work to do well, sin
On Thu, Jun 12, 2008 at 9:52 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Eventually, we'll have to track down and document which versions of sphinx,
> docutils and pygments work to build the matplotlib documentation. There's a
> lot of moving parts here...
Documenting is good, and I don'
Johann Cohen-Tanugi wrote:
> Personnally I get:
> build/latex/Matplotlib.tex:$\Cap$ \code{\textbackslash{}Cap}
That's a usage, not a definition. The problem is related to duplicate
definitions of \Cap.
> but I have sphinx 0.3 which is the version easy_installed on my FC8
> box. Actually I wonder
On Thu, Jun 12, 2008 at 9:25 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Interestingly, sphinx *doesn't* define it for me. One of the first things I
> did was "grep Cap" on the latex build directory.
> I updated sphinx from SVN pretty recently... I wonder if that has anything
> to do with
It appears to be Pygments (source code highlighter) that produces these
lines. I have Pygments 0.10 which "works for me" (TM).
pygments/formatters/latex.py
158:cmndef = r'\textcolor[rgb]{%s}{%s}' % (
Cheers,
Mike
Michael Droettboom wrote:
> Interestingly, sphinx *doesn't* defin
Personnally I get:
build/latex/Matplotlib.tex:$\Cap$ \code{\textbackslash{}Cap}
but I have sphinx 0.3 which is the version easy_installed on my FC8 box.
Actually I wonder how much trouble this 0.3 version is a promise of.
Johann
Michael Droettboom wrote:
> Interestingly, sphinx *doesn't* def
Interestingly, sphinx *doesn't* define it for me. One of the first
things I did was "grep Cap" on the latex build directory.
I updated sphinx from SVN pretty recently... I wonder if that has
anything to do with it. If that doesn't fix it, yes, that sounds like
something to report.
Cheers,
M
On Wed, Jun 11, 2008 at 4:00 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> ! LaTeX Error: Command \Cap already defined.
> Or name \end... illegal, see p.192 of the manual.
This may have been obvious to all of you,but I am just discovering it.
The problem is that *sphinx* is defining
That's my bad -- I added even more symbols to the symbol table without
updating the preamble. I should have a fix shortly.
Cheers,
Mike
Johann Cohen-Tanugi wrote:
> thanks Darren,
> I just tried and it completed to a readable pdf files, though after a
> couple of error message of this type :
>
thanks Darren,
I just tried and it completed to a readable pdf files, though after a
couple of error message of this type :
! Undefined control sequence.
\Equiv
l.2379 \end{tabulary}
? x
escaping with 'x' everythime lead to completion
best,
Johann
This message looks interesting. It suggests that combining non-Computer
Modern fonts with ams* packages can be troublesome. Perhaps this has
been fixed in recent LaTeX distributions, which is why it works for me.
http://osdir.com/ml/tex.latex.beamer.general/2006-01/msg00026.html
I wonder if r
John Hunter wrote:
> On Thu, Jun 12, 2008 at 7:01 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
>
>> Hmm. Isn't broken for me. I suspect we have some sort of version mismatch.
>>
>> One thing to try -- in conf.py remove the line
>>
>> \usepackage{amsfonts}
>>
>> It actually doesn't seem to
On Thu, Jun 12, 2008 at 7:01 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Hmm. Isn't broken for me. I suspect we have some sort of version mismatch.
>
> One thing to try -- in conf.py remove the line
>
> \usepackage{amsfonts}
>
> It actually doesn't seem to be necessary (but the other two
On Thursday 12 June 2008 08:08:41 am Michael Droettboom wrote:
> It looks as if the docs can't be built if text.usetex is "True", first
> because of needing Unicode (which also requires setting
> text.latex.unicode to True), and second because the dollar_ticks.py demo
> doesn't escape '$'.
>
> I su
It looks as if the docs can't be built if text.usetex is "True", first
because of needing Unicode (which also requires setting
text.latex.unicode to True), and second because the dollar_ticks.py demo
doesn't escape '$'.
I suppose we should hardcode text.usetex to "False" when building the
docu
Hmm. Isn't broken for me. I suspect we have some sort of version mismatch.
One thing to try -- in conf.py remove the line
\usepackage{amsfonts}
It actually doesn't seem to be necessary (but the other two are). This
error message happens during package loading, before any of the core of
our
I did not manage to build it either, but with another error, the output
is actually huge, and ipython (how come it is called?) crashes, but
after CTRL-C I get:
Original exception was:
Traceback (most recent call last):
File "make.py", line 54, in
all()
File "make.py", line 39, in all
On Wed, Jun 11, 2008 at 12:35 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 11, 2008 at 12:25 PM, Michael Droettboom <[EMAIL PROTECTED]>
> wrote:
>> Ok. I think I have that worked out -- would you mind testing on docutils
>> 0.4? (I don't think I broke anything that wasn't already bro
On Wed, Jun 11, 2008 at 02:01:59PM -0400, Michael Droettboom wrote:
There does seem to be a recent convergence around Sphinx in the Scipy
> world, and matplotlib seems to be forging ahead a little bit (maybe
> that's just my impression from being in the middle of matplotlib more so
> than other
John Hunter wrote:
> On Wed, Jun 11, 2008 at 12:25 PM, Michael Droettboom <[EMAIL PROTECTED]>
> wrote:
>
>> Ok. I think I have that worked out -- would you mind testing on docutils
>> 0.4? (I don't think I broke anything that wasn't already broken...)
>>
>
> OK, sorry I've been causing s
On Wed, Jun 11, 2008 at 12:25 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Ok. I think I have that worked out -- would you mind testing on docutils
> 0.4? (I don't think I broke anything that wasn't already broken...)
OK, sorry I've been causing so much trouble, but I guess it is good
tha
Ok. I think I have that worked out -- would you mind testing on
docutils 0.4? (I don't think I broke anything that wasn't already
broken...)
Cheers,
Mike
Michael Droettboom wrote:
> Ah. I've got 0.5. I was hoping I wouldn't have to do that crazy
> backward compatibility stuff that mathpng.
Ah. I've got 0.5. I was hoping I wouldn't have to do that crazy
backward compatibility stuff that mathpng.py does, but it looks like
I'll have to to support 0.4. I'll look into this.
Cheers,
Mike
John Hunter wrote:
> On Wed, Jun 11, 2008 at 12:05 PM, Michael Droettboom <[EMAIL PROTECTED]>
>
On Wed, Jun 11, 2008 at 12:05 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> It's related to my recently updating pyparsing.py... It seems that it isn't
> Python 2.4 compatible anymore.
>
> I'd like to workaround the definiciences in the new pyparsing.py if I can
> (rather than simply revert)
It's related to my recently updating pyparsing.py... It seems that it
isn't Python 2.4 compatible anymore.
I'd like to workaround the definiciences in the new pyparsing.py if I
can (rather than simply revert) as the error messages are much more
specific with the new version.
I have submitted
On Wed, Jun 11, 2008 at 11:53 AM, John Hunter <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 11, 2008 at 11:24 AM, Michael Droettboom <[EMAIL PROTECTED]>
> wrote:
>> Thanks. Done.
>
> I wonder is there is some python 2.5 is creeping in somewhere.
I also notice you upgraded pyparsing in that revision,
On Wed, Jun 11, 2008 at 11:24 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Thanks. Done.
I wonder is there is some python 2.5 is creeping in somewhere. I am
experiencing the same mathtext problem I pointed out earlier: This
isn't related to your recent commit, but was introduced in r5380
Thanks. Done.
John Hunter wrote:
> On Wed, Jun 11, 2008 at 10:52 AM, Michael Droettboom <[EMAIL PROTECTED]>
> wrote:
>
>> I finished moving all of the PNG reading/writing to its own module. A
>> full rebuild is probably required after this change to ensure everything
>> is working correctly.
On Wed, Jun 11, 2008 at 10:52 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> I finished moving all of the PNG reading/writing to its own module. A
> full rebuild is probably required after this change to ensure everything
> is working correctly.
src/_png.cpp: No such file or directory
Look
I finished moving all of the PNG reading/writing to its own module. A
full rebuild is probably required after this change to ensure everything
is working correctly.
Cheers,
Mike
--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
32 matches
Mail list logo
