RE: In support of the "line space" (nee <hr>)

For <hr>, I propose the following decision tree:

1. Does <hr> have any legitimate non-presentational uses?
   If no, get rid of it entirely.
   If yes, rename it and preserve the correct aspects of it.

Accentuate the positive, eliminate the negative. :-)

Alexander raises a few good points.

1. English-language-specifics

Is the "line space" technique specific to English-language texts? Can anyone
provide examples for/against?

2. Unnamed <section>s

Does an unnamed <section> capture the same meaning?

There will always be many answers to the question of how to map
chapters/verses, etc. to <section>s.

>I. e. the author considered the second subsection too small
>to give it a heading.

The part I quoted was just the very end of one block of text and the very
beginning of the next. And this particular story doesn't have any named
sections at all (besides chapters), which is pretty common (at least in my
library). So it wasn't that the author thought the subsection was "too
small", but rather that a 'pause' was necessary before continuing. An
unnamed <section> doesn't indicate any kind of a pause.

>The example [of 3 asterisks] you give dates from the old days.

Well, 1999 in any case. :-) It's written from the viewpoint of a writer,
where there is still a strong expectation to deliver dead-tree manuscripts.
I wanted to show one possible presentation of this element.

>Adding a new empty element with no information inside is
>not a good thing for the future Web

Just curious, why do you say this? Sometimes the lack of information carries
meaning. What I really don't want to see is:

<p class="center">*&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;*</p>


3. Don't add presentational attributes in any case

Violently agree. :-)

Thanks,

.micah

Received on Wednesday, 21 August 2002 19:50:01 UTC