From: James Harkins <jamshark70@gmail.com>
To: "Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Re: Beamer export ignoring org-beamer-environments-extra?
Date: Sat, 20 Apr 2013 14:14:22 +0800 [thread overview]
Message-ID: <CAFniQ7Uh3s_E121+ggt-KtGAQ0YTdM_6yjCOp1r+fnxMCVT9Sg@mail.gmail.com> (raw)
In-Reply-To: <CAFniQ7WPsx+yNnk12HMo82tU+n-7iRgjGB7DGHGxJY1i7bKF5Q@mail.gmail.com>
On Sat, Apr 20, 2013 at 12:25 PM, James Harkins <jamshark70@gmail.com> wrote:
> The problem may be a general one concerning org-beamer-environments-extra.
>
> Any portion of the document containing Chinese characters should be
> enclosed within a CJK environment. Reading ox-beamer.el, I see that I
> can customize Org Beamer Environments Extra. After customizing, C-h v
> org-beamer-environments-extra shows me:
>
> (("CJK" "Z" "\\begin{CJK}%a%h" "\\end{CJK}"))
... snip
> Whoa, wait a minute... it has completely omitted the CJK environment!
OK, after a bite for lunch, I see what the problem is.
The CJK environment, in the LaTeX code, must be specified with all
capital letters. (I tried changing the simple test file to say
"\begin{cjk}" and LaTeX failed, complaining of an unknown environment.
The test file does include "\usepackage{CJK}" and it works with
"\begin{CJK}" so the lowercase definitely means "misspelled" here.)
The Beamer exporter assumes that environment names will be all lowercase:
;; Use specified environment.
(t (downcase env)))))
I added my entry into org-beamer-environments-extra with the name
"CJK" -- so, when org-beamer-- format-block looks up the environment's
formatting spec according to the down-cased name "cjk," it finds
nothing and then does not render the environment. But, if I were to
name the environment-extra as "cjk," then the exporter would write
"\begin{cjk}" which I've already found will break.
I will temporarily work around the problem by removing "downcase."
That should get me going for the slides I need to prepare today and
tomorrow. But there must be a more elegant solution. I'm not sure what
that is, but I am certain that it is not safe to assume environments
will always be named using only lowercase letters.
One more reason to fix: There is one out-of-the-box environment,
noteNH, which includes capital letters in the name. This one is also
broken -- does not appear in the output. I.e., you can encounter the
bug without customizing anything.
hjh
next prev parent reply other threads:[~2013-04-20 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 4:25 Beamer export ignoring org-beamer-environments-extra? James Harkins
2013-04-20 6:14 ` James Harkins [this message]
2013-04-20 6:33 ` Nicolas Goaziou
2013-04-20 11:02 ` James Harkins
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=CAFniQ7Uh3s_E121+ggt-KtGAQ0YTdM_6yjCOp1r+fnxMCVT9Sg@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
/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).