On 4 October 2012 21:50, Wilhelm <[email protected]> wrote:
> Hi,
>
> if one uses the 'asciidoc' column specifier, asciidoc is called as a
> filter, using <stdin> as input-file. As a consequence it does not locate
> local filters or config-files in the directory <pathToDocument>/filters/...
>
I havn't tried it, but one possibility is to manually specify the filters
and config files on the command line instead of letting them be found
automatically, such arguments should be passed to the recursive call in
{asciidoc-args}.
.
>
> So, local configurations don't take place for nested asciidoc calls.
> That's very confusing.
>
Yes, the asciidoc style is intended to allow simple *standard* asciidoc
styling instead of a fixed cell style, not to allow arbitrary contents,
especially given the limits of docbook table contents.
>
> Is there a way to solve this?
If putting everything on the command line doesn't work, you could create a
(python or other) filter that takes the input from stdin saves it to a
temporary file in the document directory, calls asciidoc, collects the
results and deletes the temporary file and passes the results back to the
parent asciidoc.
Cheers
Lex
>
>
> --
> Wilhelm
>
> --
> 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 asciidoc+unsubscribe@**
> googlegroups.com <asciidoc%[email protected]>.
> For more options, visit this group at http://groups.google.com/**
> group/asciidoc?hl=en <http://groups.google.com/group/asciidoc?hl=en>.
>
>
--
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.
