On 13/02/12 17:17, Lex Trotman wrote:
On 13 February 2012 14:39, Stuart Rackham<[email protected]> wrote:
On 13/02/12 15:38, Lex Trotman wrote:
On 13 February 2012 13:09, Dag Wieers<[email protected]> wrote:
On Mon, 13 Feb 2012, Stuart Rackham wrote:
On 13/02/12 13:18, Dag Wieers wrote:
I would appreciate a listing in the filters-section of the website.
Even
though it's not feature-complete, it's already quite usable for a lot
of stuff. (Hey, I am using it for various documents ;-))
I assume you mean in the Plugins table 1 in
http://www.methods.co.nz/asciidoc/plugins.html
If so could you package it as a plugin so it can be downloaded and
installed using the asciidoc backend install command e.g.
asciidoc --backend install odt-0.1.zip
Right, the problem is that it currently relies on the latest asciidoc.
And
it requires the a2x changes from Lex. (I don't think they have been
integrated yet ?)
Hi Dag,
Stuart has put the changes in a2x in mercurial. I *think* but don't
guarantee that I tested the a2x backend to work with it. If it
doesn't shout and I'll try and help, but I don't have much time at the
moment.
I've just tried:
$ a2x -b odt doc/article.txt
a2x: ERROR: No base document found
Looking at your a2x-backend.py source I see that you need to pass a
--base_doc option sepecifying an odt file with the desired styles and also
saw a comment 'TODO default base doc?' in the source. Would be nice to just
go 'a2x -b odt some_document.txt' to generate an .odt file.
Hi Stuart,
Agree, thats why the comment is there.
What we need is a document that gets installed to use as the default.
If Dag can make one with *all* the asciidoc_odf styles in it (but no
content that he would mind having installed on all asciidocs) and save
it from libreoffice as a normal packaged odt file then that should do.
Then the default needs to point to where it will get installed, I
guess the backend dir. a2x has that somewhere since it found this
backend :)
Yes, the backend plugin directory (or sub-directory) is the place for it, the
odt a2x-backend.py could find it using os.path.dirname(__file__)
Cheers
Lex
Cheers, Stuart
Cheers
Lex
I will look at creating a package: think about versioning and defining a
release-plan (new milestones).
Will let you know when it's ready. Thanks !
--
-- dag wieers, [email protected], http://dag.wieers.com/
-- dagit linux solutions, [email protected], http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
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.
--
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.
--
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.
