On 28/11/11 11:28, Dag Wieers wrote:
On Mon, 28 Nov 2011, Stuart Rackham wrote:
On 27/11/11 13:30, Dag Wieers wrote:
On Thu, 24 Nov 2011, Dag Wieers wrote:
> On Fri, 25 Nov 2011, Stuart Rackham wrote:
> > > The code filter is didactic example I wrote to illustrate how to write
> > a
> > filter (http://www.methods.co.nz/asciidoc/userguide.html#X56), > > strictly
> > speaking it probably shouldn't even be in the distribution. If you > >
want to
> > take it further then the best course would be to rename your enhanced
> > version and publish it as a filter plugin.
> > I understand.
> > I don't want to take it further, in fact I just finished color highlight
> support for the source-highlight project for ODF output, and that is > clearly
> the way forward.
> > But for the people that try code-filter, having ODF and bash/ksh support
> might
> be sufficient. Even if it's a didactic example ?
I have to add to this that the AsciiDoc User Guide does use the
code-filter and
therefor without these improvements added, will fail to convert to ODF.
For that reason I would recommend adding ODF support to upstream's
code-filter.
Adding additional languages doesn't add anything in terms of illustrating how
to write a filter and would just encourage people to use it in production. If
someone has a burning desire to use and extend it then they should fork it and
publish it as a filter plugin.
But the result is that the AsciiDoc User Guide cannot be converted without
failure to anything other than what code-filter supports.
Ah, I now see your point, I've removed the code filter example from the manual:
http://code.google.com/p/asciidoc/source/detail?r=942a3d5cf64002e3bf34e5d27e3a1d5726a2cdfc
Cheers, Stuart
I'll add that to the asciidoc-odf README.
--
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.
