Hi Will
That works fine now. I wonder if it would be a good idea to define the docinfo1
attribute in the collapse.conf file:
[attributes]
docinfo1=
So you don't need to remember to add it to the command-line.
It's a pity that there's not some easy way for a filter to inject arbitrary
JavaScript (or content in general) to the output header. That would eliminate
the need for the docinfo files.
Cheers, Stuart
On 27/08/11 02:04, Will wrote:
Hi Stuart& Lex,
Thanks for the feedback.
The Zip file seems to be corrupt?
Yes, sorry my fault. The filter has been re-uploaded, please try
again:
https://sourceforge.net/projects/collapsefilter/files/collapse_filter/1.0.0/
Personally I like the filter approach, it allows you to collapse arbitrary
sections instead of the paragraph-by-paragraph approach. If this cou
I have managed to replicate all (I think) functionality using just a
conf file. This has been uploaded to:
https://sourceforge.net/projects/collapsefilter/files/collapse_conf/1.0.0/
I think using a conf file has advantages over the filter method in
that it is simpler, cleaner& faster. Drawback is (I suppose) a conf
file restricts what can be done (but for this particular example, it
is quite simple so shouldn't be an issue). Let me know what you
think.
I still have a question though, and would like your input. CSS& JS
is currently separated into a docinfo file and embedded into the xhtml
output uising the -a docinfo1 switch. Is this the best way to include
it (it means the standard conf files do not need to be modified)? If
so, is it possible to either automatically include a file, or via the
command line specify where the docinfo file lives on the filesystem?
I can only see how to include it when it is in the source file
directory, which means the "standard" docinfo file must be copied to
every source directory before rendering.
Cheers,
Will
--
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.
