From: Guenter M. <mi...@us...> - 2008-11-25 10:27:24
|
David Goodger <go...@py...> schrieb: > On Mon, Nov 24, 2008 at 18:40, Guenter Milde <mi...@us...> wrote: >> On 2008-11-24, Red Wraith wrote: >> IMO, styling via CSS is the way to go. Especially as most styles with >> vertical space for a transition also use indentation to mark paragraphs. > +1 Hiding the <hr /> is quite simple. However, some older and non-standard browsers will have difficulties with the replacement text. Test my example stylesheet in the other post. >> This would become easier, if >> a) specification (and embedding) of several stylesheets were possible >> (specifying several stylesheets is possible in LaTeX already) > -1. The C in CSS stands for "cascading". I know. But "cascading"s stands for the modularity of the stylesheets and the various possibilities to combine them. > You can chain stylesheets together, Yes, but you are not limited to a linear chain foo.html A.css B.css D.css but might also have a tree like bar.html A.css, B.css C.css D.css,E.css > so there is no need for to be able to specify multiple > stylesheets. There is a need. In addition to the reasons given by Trent (producing self-contained documents from using a customised style), I want to add: 3. An "intelligent" search path would allow to embed both, local css and standard styles easily. 4. The FAQ about --stylesheet overriding --stylesheet-path overriding --stylesheet would get an easy solution: the arguments from the different options are appended to the list of stylesheets. 5. LaTeX has a vast number of pre-defined styles (called packages) and a common latex document will need more than one. E.g. with --stylesheet=times,parskip you get a document typeset in Times with paragraph separation by vertical space. 6. Combining style variants becomes possible from the command line (or config file) without additional command line arguments and without the need for writing a separate stylesheet for every style combination. > Instructions here: > http://docutils.sourceforge.net/docs/howto/html-stylesheets.html It is important that you do not edit a copy of html4css1.css directly because html4css1.css is frequently updated with each new release of Docutils. So, how else should I produce self-contained documents with custom style? >> b) Docutils included a collection of pre-defined style sheets (e.g. in >> the sandbox), so that users without CSS knowledge can customise the >> layout by combining them. > Sure, please go ahead. How about a sandbox project with collected stylesheets? The "good ones" (most requested and tested) could then be transferred to the core. Günter |