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 <cwitt...@gmail.com> 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 > _______________________________________________ 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