Re: Quick Question on <Hn> and <HR>
Martijn Koster <m.koster@nexor.co.uk>
Errors-To: listmaster@www0.cern.ch
Date: Fri, 29 Apr 1994 13:24:50 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <9404291121.AA23573@dxmint.cern.ch>
Errors-To: listmaster@www0.cern.ch
Reply-To: m.koster@nexor.co.uk
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Martijn Koster <m.koster@nexor.co.uk>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Quick Question on <Hn> and <HR>
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Dave Ragget wrote:
@ I ... have added alignment parameters to headings and
@ paragraphs in HTML
and Paul replied:
> *nod* I know. What I am trying to say is why not just go this simple one
> stage further. I know Martijn Koster is "worried" about this being a
> client side issue, and to a large extent I do agree. But the client
> needs some help, and depending on the context the positioning of that
> line can make all the difference.
What I said was that the dislike of a browsers display of a certain
HTML+ construct is not sufficient a reason to change the use of that
construct. I agree, if we can give clients hints to improve rendering
of our documents that is a good thing. If you want no space after a H*
(before the next block) that is property of the H*, and can neatly be
handled with parameters of an H*, as Dave suggested.
Chris Lilley wrote "the rule is clearly a top line, a part of the title",
and I can see that. Maybe an <H1 rule=bottom> would do this?
What I want to prevent is the HR being used in another way than as a
block separator. Something like "<H1>Hi<Hr>there</H1>" strikes me as
abuse, and your proposed change to the DTD would allow that.
-- Martijn
__________
Internet: m.koster@nexor.co.uk
X-400: C=GB; A= ; P=Nexor; O=Nexor; S=koster; I=M
X-500: c=GB@o=NEXOR Ltd@cn=Martijn Koster
WWW: http://web.nexor.co.uk/mak/mak.html