From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: [Exporter] How to save 'info' plist for later use? Date: Wed, 10 Jul 2013 17:33:58 +0200 Message-ID: <87ehb6fmzd.fsf@gmail.com> References: <87a9lur8d0.fsf@gmail.com> <8761wir623.fsf@gmail.com> <87vc4i1uf4.fsf@gmail.com> <87wqoyppfw.fsf@gmail.com> <87vc4iplbv.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwwPF-0003yd-Jw for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 11:34:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwwPE-0006wk-5N for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 11:34:13 -0400 Received: from plane.gmane.org ([80.91.229.3]:44380) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwwPD-0006wg-Uv for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 11:34:12 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UwwPB-0000gt-Vz for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 17:34:09 +0200 Received: from g231110193.adsl.alicedsl.de ([92.231.110.193]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Jul 2013 17:34:09 +0200 Received: from tjolitz by g231110193.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Jul 2013 17:34:09 +0200 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: emacs-orgmode@gnu.org Jambunathan K writes: > Add a filter or a translator. One of the arguments to that filter is > the plist you are looking for. Work back from there and you will get > the right APIs to use. > > The snippet below from ox-odt.el should be a good starting point for > further exploration. The translators do fairly *non-trivial* > transformation on the "lispy" parse-tree before triggering off the > actual export. There you will see the APIs for element translation. > > :filters-alist '((:filter-parse-tree > . (org-odt--translate-latex-fragments > org-odt--translate-description-lists ; Dummy symbol > org-odt--translate-list-tables))) Thats indeed close to what I need and a useful example, thanks. -- cheers, Thorsten