Hi,
It's clear that ODF support will not be part of AsciiDoc. Which, if you
had told me from the start, would probably have not motivated me to write
the ODF backend, but I am at a point of no return now... Well played ;-)
But I am concerned that an output backend may never become really popular
(or even known) if it is not mentioned in the User Guide as prominently as
the other output backends (eg. in the list of attributes each backend
supports etc...). And I wouldn't be the author if I wasn't convinced about
the potential the ODF backend brings to AsciiDoc.
So is there something we can do to promote backends more/better in a
future release ?
Also, I plan to release the ODF backend (as-is) when the next AsciiDoc
version is ready. Even if not everything works exactly as I want, I hope a
wider availability might bring more people to this project to help adding
more themes or finish the backend.
It should be clear however that format style (names), attributes and
constructs may still change when we improve the functionality. (eg. the
book doctype currently hardcodes a lot of how the cover looks, which we
might influence through attributes instead)
Thanks for your help throughout !
--
-- 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.
