emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Christian Wittern <cwittern@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Switch language on heading lines in Latex export (was Re: Re: org-beamer: How to get items appear sequentially rather than all at once)
Date: Thu, 25 Mar 2010 12:02:24 +0100	[thread overview]
Message-ID: <4bab42bc.0e67f10a.1185.46e0@mx.google.com> (raw)
In-Reply-To: <5268d87d1003242050u48b1a3c6h2b7ee739e59227b3@mail.gmail.com>


I think this behavior in org-mode is correct.
For instance, suppose we have the heading below
,----
| * Some heading
|   - \textbf{lalala}
|   - {\textbf lelele}
|   - \alert{lilili}
`----

In the first item org will recognize this is a Latex command and the
brackets will be passed to Latex without any escaping. However, in the
second item there is nothing before the first bracket and org will
correctly escape the bracket. Therefore only the first letter in "lelele"
will be in bold. That is, org recognizes Latex syntax and not the old TeX
syntax in the second item. Any command recognized in Beamer will work as
the alert command in the third item.

Summarizing, define your macros as Latex macros instead of TeX ones and
they should work. That is, something like \J{XXX}.

 - Darlan

At Thu, 25 Mar 2010 12:50:23 +0900,
Christian Wittern <cwittern@gmail.com> wrote:
> 
> Dear Darlan,
> 
> Thanks for your detailed explanation.  I now got it working and am
> really happy with it.
> 
> Now there is one remaining problem with my presentation (which is
> different, which is why I changed the header line):  I do have some
> words on some heading line that are in a different language and need
> to be set in a different font.  To achieve that, I have customized the
> beamer section in org-export-latex-classes to set up a new font etc,
> this can now be switched on with {\J XX } to put XX into the desired
> Japanese Font.   However, when I do this, I get the {} brackets
> escaped so they appear in the output (I do get the right font).  So I
> wonder how I can pass this literal LaTeX through in the export.
> 
> I looked at the manual, where it talks about literal LaTeX,  but the
> use cases there seem to work only on lines by themselves, not in the
> middle of a header line.  But since this is org-mode, I am sure there
> must be a (obvious) solution which I am just failing to see....
> 
> As always, any help appreciated
> 
> Christian
> 
> 
> -- 
> Christian Wittern, Kyoto

  reply	other threads:[~2010-03-25 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  3:50 Switch language on heading lines in Latex export (was Re: Re: org-beamer: How to get items appear sequentially rather than all at once) Christian Wittern
2010-03-25 11:02 ` Darlan Cavalcante Moreira [this message]
2010-03-25 12:48   ` Christian Wittern
2010-03-26 13:51     ` Darlan Cavalcante Moreira

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=4bab42bc.0e67f10a.1185.46e0@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=cwittern@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).