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 removing the \usepackage{times} from sphinx.sty fixes things for you. Then we have the Computer Modern fonts, of course... Mike Michael Droettboom wrote: > 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 be necessary (but the other two are). This >>> error message happens during package loading, before any of the core of our >>> document is parsed. Is suspect its a bug in your LaTeX distribution that is >>> causing package conflicts. >>> >>> >> No luck on commenting out amsfonts. I've seen this bug on two >> platforms, solaris x86 and a recent ubuntu linux distro, so I suspect >> this mispackaging may be fairly common. >> > Ubuntu 8.4 works for me, but RHEL4 has unrelated errors and has never > built Sphinx docs for me. > >> If I comment out *all* of the >> ams* usepackages packages, I get past the duplicate Cap error I posted >> but then get some undefined symbol error (eg digamma) unsurprisingly. >> >> I've tried a few tests, and it looks like including only amssymb and >> nothing else gives the duplicate cap error, but excluding it gives the >> digamma and friends error even if the others are included. So it >> looks like I'm stuck, since no combination of these packages works. >> >> [EMAIL PROTECTED]:doc> uname -a >> Linux bic128.bic.berkeley.edu 2.6.25.4-10.fc8 #1 SMP Thu May 22 >> 22:58:37 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux >> [EMAIL PROTECTED]:doc> latex --version >> pdfeTeX 3.141592-1.21a-2.2 (Web2C 7.5.4) >> kpathsea version 3.5.4 >> >> >> > One way I've fixed these errors (manually) in the past is to change the > ordering of the \usepackage{} statements. I wonder if you move the > "ams" ones above everything else if that fixes things. If so hopefully > we can submit a patch to sphinx to allow putting the custom preamble > earlier. > > 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, > since we don't currently have a way to get a nice tightly-bound PDF of a > math expression, and embedding PNGs will look bad. > > Cheers, > Mike > > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
