From: Robert Goldman <email@example.com>
To: "Thomas S. Dye" <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>
Subject: Re: bug in latex export tutorial?
Date: Fri, 29 Apr 2011 11:51:32 -0500 [thread overview]
Message-ID: <4DBAEC94.firstname.lastname@example.org> (raw)
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?
2. What happens to the parallel HTML export if we use amsmath
constructs in an org file?
> Thanks for pointing this out.
> All the best,
> On Apr 29, 2011, at 6:26 AM, Robert Goldman wrote:
>> The document http://orgmode.org/worg/org-tutorials/org-latex-export.html
>> "The Org-mode LaTeX exporter uses several packages to support special
>> characters used by org-entities. One of these, amsmath, conflicts with
>> several LaTeX fonts. If you want finer control over which packages are
>> loaded, then it makes sense to define an export class like this in
>> But I just checked the results of exporting one of my org files, and it
>> does /not/ use amsmath.
>> Is this a bug in the tutorial?
next prev parent reply other threads:[~2011-04-29 16:51 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 [this message]
2011-04-29 17:21 ` Thomas S. Dye
2011-04-29 18:21 ` Nick Dokos
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
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 \
* 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).