emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
Cc: Christian Wittern <cwittern@gmail.com>,
	Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: "{" in Latex fragments
Date: Wed, 25 Aug 2010 09:39:16 +0100	[thread overview]
Message-ID: <87aaobulvv.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <831v9nayqw.fsf@yahoo.it>

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

On Wed, 25 Aug 2010 10:21:43 +0200, Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> wrote:
> 
> Christian Wittern <cwittern@gmail.com> writes:
> 
> > In my org-mode document, I have a special sequence to switch to a Japanese
> > font defined as \J.  When using this, I have to do something like {\J
> > (Japanese characters here}.  However, when I run the org-mode export, the
> > braces "{" and "}" are escaped as \{ and \} and thus loosing their
> > function.
> 
> yes.
> 
> but why don't you change the sequence? I mean:
> 
> from:
> 
> hello {\J ウ}
> 
> to 
> 
> hello  [\J ウ ] or: (\J ウ)
> 
> [] and () are not escaped
> 
> cheers,
> Giovanni

I think because the {}'s define a scope in latex and so the \J only
affects text surrounded by the {}.


For Christian, what about "\J{ text }" instead as org is careful to
let this type of construct go through unchanged, if I understand
correctly.  This does depend on how you have defined J but possibly a
slight redefinition would work (\newcommand{\J}[1]{.... #1}).

HTH,
eric

[-- Attachment #2: Type: text/plain, Size: 295 bytes --]

-- 
MC .  -.. --- -  ..-. .-. .- --. .-  .- -  ..- -.-. .-..  .- -.-.  ..- -.-
NL Professor Eric S Fraga, UCL, http://www.homepages.ucl.ac.uk/~ucecesf/
PG Fingerprint: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D
BF >++++++++++[>++++++++++>+++++++++++[<]>-]>++.>++++.<-----.++++++.------.

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  parent reply	other threads:[~2010-08-25  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25  7:45 "{" in Latex fragments Christian Wittern
2010-08-25  8:21 ` Giovanni Ridolfi
2010-08-25  8:36   ` Scot Becker
2010-08-25  8:39   ` Eric S Fraga [this message]
2010-08-25 10:06     ` Christian Wittern

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=87aaobulvv.wl%ucecesf@ucl.ac.uk \
    --to=ucecesf@ucl.ac.uk \
    --cc=cwittern@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=giovanni.ridolfi@yahoo.it \
    /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).