From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darlan Cavalcante Moreira 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: Fri, 26 Mar 2010 14:51:47 +0100 Message-ID: <4bacbbf0.1067f10a.5441.3df5@mx.google.com> References: <5268d87d1003242050u48b1a3c6h2b7ee739e59227b3@mail.gmail.com> <4bab42bc.0e67f10a.1185.46e0@mx.google.com> <4BAB5B87.4090308@gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nv9x1-0007eC-FF for emacs-orgmode@gnu.org; Fri, 26 Mar 2010 09:51:51 -0400 Received: from [140.186.70.92] (port=58559 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nv9wz-0007cy-LA for emacs-orgmode@gnu.org; Fri, 26 Mar 2010 09:51:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nv9wx-0004g8-Vu for emacs-orgmode@gnu.org; Fri, 26 Mar 2010 09:51:49 -0400 Received: from mail-ew0-f227.google.com ([209.85.219.227]:57043) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nv9wx-0004fn-QL for emacs-orgmode@gnu.org; Fri, 26 Mar 2010 09:51:47 -0400 Received: by ewy27 with SMTP id 27so142670ewy.30 for ; Fri, 26 Mar 2010 06:51:45 -0700 (PDT) In-Reply-To: <4BAB5B87.4090308@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Christian Wittern Cc: Org Mode Mailing List As I understand, whenever org sees something like "\something" it will understand that this is a latex command and it will just write it as it is in the exported latex file. Therefore, if you put something like #+LATEX_HEADER: \newcommand{\blue}[1] {\textcolor{blue}{#1}} in the beginning of the org file than latex will know the command "blue" and writing "\blue{some text}" in the org presentation will work as expected. I even tried defining latex commands with two arguments such as the with the line below #+LATEX_HEADER: \newcommand{\blueRed}[2]{\textcolor{blue}{#1} \textcolor{red}{#2}} and it works! I don't know this newfontfamily command in latex, but if you can use a command in latex then you can do the same in org. Notice, however, that I used "#+LATEX_HEADER:". That is, I created a macro in Latex, not in org. Macros defined in org are created with "#+MACRO:". - Darlan At Thu, 25 Mar 2010 21:48:07 +0900, Christian Wittern wrote: > > Darlan, > > Thank you again. I think I understand the problem now. > > On 2010-03-25 20:02, Darlan Cavalcante Moreira wrote: > > Summarizing, define your macros as Latex macros instead of TeX ones and > > they should work. That is, something like \J{XXX}. > > > > Currently, the definition is > \newfontfamily{\J}[Scale=0.85]{Osaka} > > If I say \J{XX} in my documents, org-mode's latex export does the right > thing and I get what I need, so does this definition as you call it also > define a LaTeX macro? Or is this just pure luck? Still mystified by > all this, but very glad that I can say goodbye to WYSWIG presentation > software:-) > > All the best, > > Christian >