From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: odt export version conflict on emacs for mac os x Date: Sat, 31 Aug 2013 08:04:34 +0200 Message-ID: <513951A8-0878-4133-AD2B-36FAC7D4B98C@gmail.com> References: <87k3j5krwt.fsf@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59073) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFeIf-0003AO-8t for emacs-orgmode@gnu.org; Sat, 31 Aug 2013 02:04:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VFeIW-0007NZ-QM for emacs-orgmode@gnu.org; Sat, 31 Aug 2013 02:04:45 -0400 Received: from mail-ee0-x229.google.com ([2a00:1450:4013:c00::229]:58953) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFeIW-0007NT-JG for emacs-orgmode@gnu.org; Sat, 31 Aug 2013 02:04:36 -0400 Received: by mail-ee0-f41.google.com with SMTP id d17so1289979eek.14 for ; Fri, 30 Aug 2013 23:04:35 -0700 (PDT) In-Reply-To: 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins Cc: emacs-org list , Jambunathan K Hi, can someone please summarize this discussion for me and tell me what = action is required? Thank you! - Carsten On 29.8.2013, at 20:25, Skip Collins wrote: > Jambunathan K wrote: >>> After I do an ODT export, many ox-odt variables are duplicated with >>> old variable names: >>> | [-]-\ Group Org Export ODT >>> | | |--- Option Org Odt Schema Dir >>> | | |--- Option Org Odt Content Template File >>=20 >> Above ones come from NEW exporter, ox-odt.el >>=20 >>> | | |--- Option Org Export Odt Schema Dir >>> | | |--- Option Org Export Odt Content Template File >>=20 >> Above ones come from LEGACY exporter. Not used by ox-odt.el. >>=20 >> This is confusing but the behaviour is expected and NOT BUGGY. >=20 > Thank you for clarifying a confusing situation. I am not sure why I > assumed that the org-export-odt variables were the newer ones. >=20 > Suggestion for maintainers: a new, separate customization group, with > appropriate pointers in the documentation, would be helpful. >=20