From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giacomo M Subject: Expansion of macros conditional on export type Date: Fri, 27 May 2016 12:03:15 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/html; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34666) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6Eby-0007t9-HB for emacs-orgmode@gnu.org; Fri, 27 May 2016 06:03:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b6Ebu-0006PZ-AO for emacs-orgmode@gnu.org; Fri, 27 May 2016 06:03:21 -0400 Received: from mail-wm0-x22a.google.com ([2a00:1450:400c:c09::22a]:37013) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b6Ebu-0006PU-3k for emacs-orgmode@gnu.org; Fri, 27 May 2016 06:03:18 -0400 Received: by mail-wm0-x22a.google.com with SMTP id z87so130667133wmh.0 for ; Fri, 27 May 2016 03:03:17 -0700 (PDT) Received: from [127.0.0.1] ([212.189.161.135]) by smtp.gmail.com with ESMTPSA id c2sm7871458wme.4.2016.05.27.03.03.16 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 27 May 2016 03:03:16 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org

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 corresponding symbol in odt, or \ce{CO2} vs CO_2? For citations I'm using org-add-link-type as found in reddit, but it looks cumbersome to create specific alternatives via links each time. Another issue seems to declare institutes along with authors in latex vs odt in the title section.

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.

Any ideas on where I can find related best practices?

Thanks,

Giacomo M