From: Nick Dokos <nicholas.dokos@hp.com>
To: Jeff Kowalczyk <jtk@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Export bug: _ { chars in enough headlines, pdflatex export fails
Date: Fri, 25 Sep 2009 11:02:09 -0400 [thread overview]
Message-ID: <10809.1253890929@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Jeff Kowalczyk <jtk@yahoo.com> of "Thu, 24 Sep 2009 21:42:23 PDT." <256566.72456.qm@web63406.mail.re1.yahoo.com>
Jeff Kowalczyk <jtk@yahoo.com> wrote:
> Export to pdflatex fails if underscore or unclosed bracket characters are in enough headlines.
>
> Thanks,
> Jeff
>
Open braces without the corresponding closing brace on the same line
caused errors before: Carsten fixed one (in an ATTR_LaTeX header iirc),
but I have run into at least one more. In my case, the open braces were
part of LaTeX constructs, so I could work around the problem by fooling
the org latex exporter like so:
#+BEGIN_LaTeX
\someconstruct{ %} dummy closing brace in comment
#+END_LaTeX
foo bar
#+BEGIN_LaTeX
} % the real closing brace
#+END_LaTeX
(One could also use \begin{env}/\end{end} in most cases, but there are
still some cases where that option is not available, afaik).
That will not work as well for you. But I don't understand why you need
open braces in your headlines at all - can't you just get rid of them?
Thanks,
Nick
next prev parent reply other threads:[~2009-09-25 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 4:42 Export bug: _ { chars in enough headlines, pdflatex export fails Jeff Kowalczyk
2009-09-25 6:35 ` Carsten Dominik
2009-09-25 12:08 ` Jeff Kowalczyk
2009-09-25 15:02 ` Nick Dokos [this message]
2009-09-25 15:41 ` Export bug: _{ " Jeff Kowalczyk
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=10809.1253890929@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=jtk@yahoo.com \
/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).