[...] >> 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
If you support only flat files you no longer support my use-case for this backend, the ability to apply styles generated interactively using LO or OO and stored in an OTT file. This capability provides a way to configure presentation for users without special expertise, if they have to write ODF-XML styles in a theme then this backend provides no benefit over any other toolchain. It would be totally inappropriate to have users tweeking the output each time they generated it becuase they cannot do it any other way. Cheers Lex -- 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.
