On Tue, 9 Sep 2003, Dimitrie O. Paun wrote: [...]
It's fine to use CSS for the .template ones that we're going to server from the site. However, for the HTML we package, we shouldn't IMO. If they need such thing, they would have a custom default.dsl or some such. That's the very point -- we should allow the user to choose the L&F, not impose one; this is the purpose of having a site wide default.dsl.
I think you just gave a good argument for using cascading stylesheets in the Wine documentation.
If the look and feel is set by default.dsl, then only users who have access to the Wine source and have DocBook installed on their system can change the look and feel. All other users must change each and every file manually (because default.dsl puts hardcoded html attributes all over the place).
Cascading stylesheets don't require a server. I modified our build system to use one, winedoc.css, and all it requires is that we ship that file together with the .html files.
Then users that don't have access to the Wine source can change one file, winedoc.css, to change the look and feel of the whole doc.
For instance, to make the FAQ questions red and not bold, just edit winedoc.css and replace
.question { border-top: dashed thin; font-weight: bolder; }
with
.question { border-top: dashed thin; color: #FF0000; }
Ok, submitting a patch in that direction...