Re: [O] Expansion of macros conditional on export type

2016-05-27 Thread Eric S Fraga
On Friday, 27 May 2016 at 10:26, Giacomo M wrote: > For chunks of text like institute affiliations, may I ask if you use > different BEGIN_EXPORT blocks or sth else? Depends. Most often a sequence of #+latex_header: lines as my eventual target for export is almost always LaTeX for submission to

Re: [O] Expansion of macros conditional on export type

2016-05-27 Thread Giacomo M
Il 27/05/2016 12:17, Eric S Fraga ha scritto: I know one way would be to use @@latex: ... @@ w/ ascii counterpart each time, but I would rather envision a single macro, which then gets defined in different way depending on the export, in order to reduce redundancy. You can put all the different

Re: [O] Expansion of macros conditional on export type

2016-05-27 Thread Eric S Fraga
> I know one way would be to use @@latex: ... @@ w/ ascii counterpart > each time, but I would rather envision a single macro, which then gets > defined in different way depending on the export, in order to reduce > redundancy. You can put all the different alternatives together? I do the

[O] Expansion of macros conditional on export type

2016-05-27 Thread Giacomo M
Dear all, I'm working on a paper where some co-authors use word and some (myself included) latex. Org seems the perfect way to mantain a central version. How do I deal with constructs that should be exported in different ways, e.g. \textdegree{} in latex vs