From: "Levy, Roger" <rlevy@ucsd.edu>
To: Viktor Rosenfeld <listuser36@googlemail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Defining new structural markup element
Date: Wed, 14 Dec 2011 19:06:48 +0000 [thread overview]
Message-ID: <497EE111-21B5-4B9A-913C-97067CCFEC04@ucsd.edu> (raw)
In-Reply-To: <20111214180851.GA62066@client195-35.wlan.hu-berlin.de>
Thanks so much, Viktor, this is exactly what I wanted!
Best
Roger
On Dec 14, 2011, at 1:08 PM EST, Viktor Rosenfeld wrote:
> Hi,
>
> the Worg page on LaTeX publishing covers this under "Block-level Markup"
> and "Inline Markup":
>
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-2
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10-3
>
> Haven't tried it myself so far (but planning to do so).
>
> Cheers,
> Viktor
>
> Levy, Roger wrote:
>
>> Hi,
>>
>> I'm a relative org newbie and I expect that this question is answered somewhere in the manual, but I've searched and I can't find the answer.
>>
>> I would like to define a new structural markup element for an org file and specify its translation into latex. e.g., I'd like to be able to put in my document
>>
>> #+begin_foo
>> bar
>> #+end_foo
>>
>> and have this translated into LaTeX as something like
>>
>> \em
>> bar
>> \em
>>
>> but I'd like to be able to flexibly specify the LaTeX commands inserted at the beginning and end of the "foo" block. Is there an easy way to do this?
>>
>> Best & many thanks in advance!
>>
>> Roger
>>
>>
--
Roger Levy Email: rlevy@ucsd.edu
Assistant Professor Phone: 858-534-7219
Department of Linguistics Fax: 858-534-4789
UC San Diego Web: http://idiom.ucsd.edu/~rlevy
prev parent reply other threads:[~2011-12-14 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 17:33 Defining new structural markup element Levy, Roger
2011-12-14 17:47 ` Nick Dokos
2011-12-14 18:08 ` Viktor Rosenfeld
2011-12-14 19:06 ` Levy, Roger [this message]
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=497EE111-21B5-4B9A-913C-97067CCFEC04@ucsd.edu \
--to=rlevy@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=listuser36@googlemail.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).