From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Schmitz Subject: Exporting custom dynamic blocks Date: Tue, 19 May 2015 13:22:52 +0000 Message-ID: <84e317a68c2c4d37855ffd2ca4e2dddc@barcarole.visus.uni-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34712) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuhU6-0004le-7Q for emacs-orgmode@gnu.org; Tue, 19 May 2015 09:23:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YuhTz-0001fM-7k for emacs-orgmode@gnu.org; Tue, 19 May 2015 09:23:02 -0400 Received: from mx3.informatik.uni-stuttgart.de ([129.69.211.42]:38352) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YuhTz-0001ei-1E for emacs-orgmode@gnu.org; Tue, 19 May 2015 09:22:55 -0400 Received: from mx.visus.uni-stuttgart.de (impromptu.visus.uni-stuttgart.de [129.69.205.29]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx3.informatik.uni-stuttgart.de (Postfix) with ESMTPS id 2AB3B6242 for ; Tue, 19 May 2015 15:22:53 +0200 (CEST) Content-Language: de-DE 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" Hi, What is the canonical way of exporting custom dynamic blocks? Is there a me= chanism similar to org-dblock-write: only for exporting dblocks? I cannot f= ind any documentation on this. To give a little background to my question: I am currently writing a conver= sion from deadlines/schedules/effort to pgf-gantt charts. This was discusse= d before on this list, but I couldn't find anyone actually implementing it. Ideally I would like to create a custom dynamic block that contains the res= ult of my parsing and computation, and then have a custom exporter for that= dynamic block that creates the pgf-gantt code, so that I can later add exp= orters for other formats, e.g. html. If there is no such mechanism, what is the best way of storing that pgf-gan= tt source code so that it gets integrated into latex export, but doesn't in= terfere with other exporters? Currently I'm simply writing the pgf-gantt co= de into the custom block, and this does get exported correctly to latex, bu= t produces error boxes in html. Regards, Bernhard