emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: rpgoldman@sift.info
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: bug in latex export tutorial?
Date: Fri, 29 Apr 2011 07:21:52 -1000	[thread overview]
Message-ID: <F4A4158C-3FFE-48C8-BB8C-044C349046AC@tsdye.com> (raw)
In-Reply-To: <4DBAEC94.3050902@sift.info>

[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]

Aloha Robert,

You're right again.  Sorry for the noise.  The amssymb package is the  
source of the font conflicts.

Thanks for pointing this out.

I don't use amsmath, so can't help with your queries.  When you've  
sorted them out, please consider adding the solution to the LaTeX  
export tutorial.

All the best,
Tom

On Apr 29, 2011, at 6:51 AM, Robert Goldman 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?
> 2.  What happens to the parallel HTML export if we use amsmath
> constructs in an org file?
>
> thanks!
> r
>
>>
>> Thanks for pointing this out.
>>
>> All the best,
>> Tom
>>
>> On Apr 29, 2011, at 6:26 AM, Robert Goldman wrote:
>>
>>> The document http://orgmode.org/worg/org-tutorials/org-latex-export.html
>>> claims
>>>
>>> "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
>>> .emacs:"
>>>
>>> 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?
>>>
>>>
>>
>


[-- Attachment #2: Type: text/html, Size: 5631 bytes --]

  reply	other threads:[~2011-04-29 17:22 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 [this message]
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

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=F4A4158C-3FFE-48C8-BB8C-044C349046AC@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).