On 4 October 2011 17:46, Lex Trotman <[email protected]> wrote: > Hi Stuart, > > Now we have plugin backends, the question of integration with a2x arises. > > I propose the following simple method. > > a2x gets a -b --backend option. If it is specified a2x uses "asciidoc > --backend list" to get the directory for the backend and looks for an > a2x.conf in that directory as well as the usual places. > > That a2x.conf will be expected to define a to_backendname(self) > function like the others in class A2X. > > a2x will also accept a --backend-opts in a similar way to xslt-opts, etc > > when --backend is specified the to_backendname() function is called > instead of the to_formatname() function. > > This should allow the plugin to re-use as much as possible of a2x's > existing infrastructure. > > This executes arbitary code, but a2x already does that from its conf > files anyway so there is no reduction in safety. > > If it sounds ok, then I'm happy to provide a patch for this as part of > developing the ODF backend with Dag. > > Cheers > Lex >
See https://github.com/dagwieers/asciidoc-odf/zipped for a first pass modified a2x and example a2x.conf backend plugin. Cheers Lex -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
