emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: rpgoldman@sift.info
Cc: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: bug in latex export tutorial?
Date: Fri, 29 Apr 2011 14:21:10 -0400	[thread overview]
Message-ID: <5267.1304101270@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Robert Goldman <rpgoldman@sift.info> of "Fri, 29 Apr 2011 11:51:32 CDT." <4DBAEC94.3050902@sift.info>

Robert Goldman <rpgoldman@sift.info> wrote:

> On 4/29/11 Apr 29 -11:44 AM, Thomas S. Dye wrote:
> > Aloha Robert,
> > 
> > Yep.  It should be "One of these, amssymb, requires amsmath, which
> > conflicts with several LaTeX fonts."
> I don't /believe/ amssymb requires amsmath.  I have been working on a
> document where I wanted to use some of the stuff in amsmath (e.g.,
> \text, align environment).  That document did /not/ parse, even though
> amssymb *is* in the preamble of the exported file.  I looked, and the
> preamble has amssymb, but not amsmath.
> It would be *great* if someone could provide tutorial information that
> would tell us:
> 1.  How do we configure a file so that it *can* use amsmath?

amsmath conflicts with wasysym (redefines \iint), so you have to
redefine your headers to omit wasysym or include amsmath *first*: for
some reason, if you \usepackage{amsmath} *before* you
\usepackage{wasysym}, the error does not arise -- presumably, amsmath
assumes that \iint is not defined beforehand, whereas wasysym does not
make that assumption.

> 2.  What happens to the parallel HTML export if we use amsmath
> constructs in an org file?

It would depend on whether you use the dvipng mechanism or the mathjax mechanism
for math visualization. In the first case, amsmath is automatically included by
org mode (before wasysym, so no problems). In the second case, I wouldn't be able
to tell you: I've had problems with mathjax that I've wanted to investigate for ages
and never had the time - one of these centuries I'll get around to it...


  parent reply	other threads:[~2011-04-29 18:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 16:26 bug in latex export tutorial? Robert Goldman
2011-04-29 16:44 ` Thomas S. Dye
2011-04-29 16:51   ` Robert Goldman
2011-04-29 17:21     ` Thomas S. Dye
2011-04-29 18:21     ` Nick Dokos [this message]
2011-04-29 21:05       ` Robert Goldman
2011-04-30 22:14         ` Eric S Fraga
2011-05-01 16:12           ` Collaboration and settings --- was " Robert Goldman
2011-05-02 17:05             ` Thomas S. Dye

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5267.1304101270@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).