You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The {numbered} macro specifies whether Chapters and Sections need to be numbered. In ODF the numbering is part of the style for each section-level, and thus if we want to influence the numbering we need to influence the stylesheet (contrary to how it works for XHTML).
Now, it is possible to eg. create 2 stylesheets, one for numbered and one for unnumbered, but that would lead to a lot of stylesheet duplication. And if another macro is required to influence the stylesheet (eg. for icons support), we need to duplicate it once again (having 4 different stylesheets for each combination). So that is not really an option.
Processing the stylesheet and allowing macros in stylesheets, might be required to make this manageable.
The text was updated successfully, but these errors were encountered:
The {numbered} macro specifies whether Chapters and Sections need to be numbered. In ODF the numbering is part of the style for each section-level, and thus if we want to influence the numbering we need to influence the stylesheet (contrary to how it works for XHTML).
Now, it is possible to eg. create 2 stylesheets, one for numbered and one for unnumbered, but that would lead to a lot of stylesheet duplication. And if another macro is required to influence the stylesheet (eg. for icons support), we need to duplicate it once again (having 4 different stylesheets for each combination). So that is not really an option.
Well, yes there is a combinatorial increase, but this is just s
selection process, easy to understand and easy (if tedious) to
maintain.
Processing the stylesheet and allowing macros in stylesheets, might be required to make this manageable.
This has the issue that the stylesheets are going to have the
combinatorial increase inside them, really messy and hard to maintain
I am also not sure that either is really worth the cost, just say
setting numbered doesn't work for odf. Remember also that any
presentational info like this in the asciidoc will be overridden by
the styles applied from the ODF template (and being able to apply gui
generated templates was the point of the odf backend :)
Cheers
Lex
Reply to this email directly or view it on GitHub: #15
The {numbered} macro specifies whether Chapters and Sections need to be numbered. In ODF the numbering is part of the style for each section-level, and thus if we want to influence the numbering we need to influence the stylesheet (contrary to how it works for XHTML).
Now, it is possible to eg. create 2 stylesheets, one for numbered and one for unnumbered, but that would lead to a lot of stylesheet duplication. And if another macro is required to influence the stylesheet (eg. for icons support), we need to duplicate it once again (having 4 different stylesheets for each combination). So that is not really an option.
Processing the stylesheet and allowing macros in stylesheets, might be required to make this manageable.
The text was updated successfully, but these errors were encountered: