On Tue, 27 Sep 2011, Miklos Vajna wrote:
On Sun, Sep 18, 2011 at 11:15:26AM +1000, Lex Trotman <[email protected]> wrote:
IIRC ODT can also work as a single XML file, but yes having a default zipped
file would be welcome (but probably the easiest part :-) Having a single XML
ODF file is most useful for debugging though.
So long as lo/oo can open it and the result is right it doesn't
matter, whichever is easier to generate.
Right, .fodt is a single xml file, especially for this kind of purposes.
I have started writing an ODT backend for AsciiDoc, and it currently
produces my test-document (curriculum vitae) almost exactly as the
output from the docbook2odf/unoconv toolchain.
Noteworthy items:
- LibreOffice/OpenOffice is not able to open a flat ODF file (single
XML file), however encapsulating a single XML file inside a zip will
works although is reported to be corrupted (but nevertheless loads
fine). Producing the content.xml does not have that issue :-/
- I asked on the LibreOffice forum to get single XML file import support,
which is very much wanted for testing ODF in general. Hope this is
something for the future...
- If we would like to produced zip-encapsulated ODT files, AsciiDoc would
need such infrastructure to facilitate the backend. Not sure how that
would work, but currently the backend is non-functional with
LibreOffice/OpenOffice.
- Embedded (data-uri) images works also in ODT, I have it implemented.
If images are not embedded, they are referenced by URI and could be
part of the zip file too.
- I have currently added my own style-sheet to the backend, we may want
to make it look more generic (maybe similar to the HTML output). Do we
want to allow asciidoc to replace the stylesheet, or is this better
left to unoconv/libreoffice/openoffice ? Both have some use, I guess.
- The stylenames are trashed by LibreOffice, so opening the generated ODT
document and saving it, will replace the properly named styles by
LibreOffice's ugly ones. Which should not be a problem, since ODT is
considered an 'output' format, likely to produce PDF ;-) The visible
style names are preserved, so LibreOffice users won't notice it.
Only the basics are implemented as of today:
- metadata
- title and headings
- emphasis, strong, monospaced, superscript, subscript, quoted,
doublequoted, ...
- numbered, bullet and named lists
- page-breaks and line-breaks
- sidebars
- admonitions
- URLs
Considering I only spent 3 hours on this with little knowledge of how
this works in AsciiDoc, I am convinced this is a better approach than
docbook2odf.
Kind regards,
--
-- 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.
