[Felix Wiemann]
> IMO the <hr>s at
>
<http://docutils.sf.net/test/functional/expected/standalone_rst_html4css1.html>
> are a bit too small for header and footer. What about changing the
> header and footer <hr>s to default width?
>
> (This could be done e.g. by assigning them the class
> "docutils-header" and "docutils-footer" instead of two classes
> "docutils header" and "docutils footer".)
Yes, that's fine; done. The <hr>s don't need the "docutils" classes
though; they're just for otherwise class-less <hr>s. I've changed the
classes to just "header" and "footer".
I also moved the <hr> tag inside the header and footer <div>s. That
way, the stylesheet can use contextual selection, and headers/footers
can be treated as a block.
Another way to get the same effect is to a rule to the stylesheet as
follows:
hr.header {
width: 100% }
But this has to be *after* the hr.docutils rule for it to work. This
works in Firefox, but I don't know about other browsers, and the order
requirement may be too subtle.
>> Modified: trunk/docutils/docs/ref/rst/directives.txt
>> ===================================================================
>>
>> +The "header" and "footer" directives create document decorations,
>> +useful for page navigation, [...]
> ^^^^^^^^^^^^^^^
>
> Header and footer shouldn't be used for navigation.
I don't know that they shouldn't. They will be, whether you or I like
it or not. Practicality over purity.
What's wrong with adding some links (Home, Docs, Download, etc.) to a
header?
> Docutils is not a web page creation system, and attempting to use it
> as one will almost inevitably cause trouble.
It's not a web *site* creation *system*, but it is a web *page*
creation *tool*. We use it as such for Docutils itself.
> Would you object to removing that?
-0. I wouldn't object, but I think it's a futile exercise. Better
perhaps would be to add some text that describes the limitations and
warns against trying to use Docutils as a complex web site creation
system.
--
David Goodger <http://python.net/~goodger>
|