[...] > > As I understand it (and I'm not 100% sure I do), ODF outputs can be styled > using a .styles file (for generating .fodt files using asciidoc) or an > .odt/.ott file (for generating .odt files using a2x). > > 1. The default asciidoc.odt.styles file is in the from the odt plugin > directory. > > 2. *.styles "theme" files are installed from theme plugin directories. > > 3. An odt/ott template document which is specified explicitly with the > a2x-backend.py --base_doc=path command option.
Hi Stuart, That would be my understanding too. > > @Lex: would --template be more descriptive option name than --base_doc ? I won't claim base_doc is a good name :) But in LO OO terms "template" is a document including content, and in this case we are definitly not using the content, we are only using the styles, so maybe style_doc or something similar. Just so it is not confusing with .styles styling :) > > My guess is that very few users will want to deal with .fodt files directly, > preferring .odt files instead i.e. a2x will be used in preference to > asciidoc. > > Taking up Lex's point, I think the vast majority of users would want to > style with ott templates and not .styles files. The ability to style using > interactively generated ott files was the raison d'être for an ODF backend > in the first place. > > So why complicate things with .styles themes plugins? Instead ship any > built-in .styles files with the odt plugin and make an asciidoc '-a > odf-styles=path' attribute available for those users who want to use their > own .styles files. > Simple is good. 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.
