Hi Christian,
On Fri, Apr 12, 2013 at 03:08:17PM +0200, Christian Egli wrote:
> Buddy Butterfly <buddy.butter...@web.de> writes:
> > Here I would suggest that one can place this data inbetween
> >
> > #+BEGIN_TASKJUGGLER
> > #+END_TASKJUGGLER
>
> This is something I'd like to add support for. I just never got around
> to look at how this could be implemented. It has some implications as
> you could destroy your otherwise valid tjp file. But it might cover some
> of your use cases above. Do you know how this could be done in the new
> exporter?
I believe you can use the :export-block property when defining the
backend to specify blocks.
Quoting from the docstring of org-export-define-backend:
:export-block
String, or list of strings, representing block names that
will not be parsed. This is used to specify blocks that will
contain raw code specific to the back-end. These blocks
still have to be handled by the relative `export-block' type
translator.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
