On Wed, 15 Feb 2012, Stuart Rackham wrote:
One plugin zip file per backend is what we're stuck with, but the generation
of odt-1.0.zip, odp-1.0.zip would be automated by the makefile so it's
probably not as bad as it appears.
Indeed, this works fine now. I guess if I would have used different Github
projects for each, the zip-file could have been produced by Github on the
fly, rather than needing to be generated and uploaded.
But having them together has some advantages too.
Re 'cv' and 'hp' themes, I don't understand ODF themes but, couldn't they be
built into the ODF backends handled by passing them in the a2x
--backend-opts option which passes it on to the a2x-backend.py? e.g.
a2x --backend odt --backend-opts="--theme=cv" mydoc.txt
That's possible, but they are IMO more useful for flat XML ODF output (the
ODF files asciidoc generates). In fact, I think it's sufficient to have
a2x only consider about templates and asciidoc only consider themes.
After experimenting yesterday with the ODT output a2x generates (and
fixing a few issues along the way) I am not so convinced the current
implementation is good. We lack certain information the flat XML ODF gets
automatically from the backend (like metadata), so maybe a better approach
is to only generate flat XML ODF output and let LibreOffice do the
conversion to packaged ODF files. It saves us the trouble of
destructing/constructing zip files.
However there are some issues with the current implementation of
LibreOffice:
- LibreOffice fails to convert when an instance is already running
- LibreOffice has no way to apply styles during conversion
At the moment unoconv can do both things, but I think it is worthwhile to
get both problems fixed upstream.
I wonder if --theme is sufficiently general for it to be added to a2x (which
would then passed to a2x-backend.py as self.theme) -- the above example
command would become:
a2x --backend odt --theme=cv mydoc.txt
This would do away with the need for separate 'theme' zip files (the AsciiDoc
themes are specific to HTML (html5 and xhtml11 backends)).
Yes, and it would do away with the confusion if you installed a theme, but
cannot use it with another backend. Maybe adding backend names to themes
would not be a bad practice. Or at least change the directory layout to
reflect that ?
It's not that important to me at the moment though :)
--
-- 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.
