Re: For the future - requests for the W3C (fwd)

MegaZone (
Mon, 13 May 1996 19:40:44 -0700 (PDT)

Message-Id: <>
Subject: Re: For the future - requests for the W3C (fwd)
Date: Mon, 13 May 1996 19:40:44 -0700 (PDT)
From: MegaZone <>

Once upon a time Abigail shaped the electrons to say...
>I agree, MD is not very important. However, it cannot hurt to put it
>in the DTD. Most browsers won't do anything with MD, but that doesn't
>degrade the document - it is an attribute which can safely be ignored.
>However, if there would be a browser which deals with it, it would
>be convenient to have it in the DTD; if only to validate documents.
>Same for LANG. Most mentioned feature of LANG is the style of quotes.

I see your points.  My concern is adding tags when their usage isn't
clearly defined.  I suppose MD is rather clear, but LANG still seems the
subject of a lot of discussion.  To me it seems more appropriate to
keep it in experimental DTDs than to put it in the official release.
But it isn't a show stopper, browsers that don't get it can ignore it.
I just don't want to encourage it's use when the use part isn't clear.

>Allowing SRC to <LI> allows for different bullets in the same list.
>(For instance, an index with different bullets for "advanced" topics).
>Adding SRC to <UL> in stead of repeating it in each <LI> is just
>convenience for the author. I don't see anything wrong about that.

Granted.  Just seemed redundant, but ease of use is also an issue.
Having more time to think about it, I guess I've changed my mind.
Having it in both shouldn't cause a problem and it would be nice.

>If you do not have ID and TO, wouldn't <TAB> give the same problems
>as graphics now? That is, give very ugly effects on browsers which
>already indent paragraphs? I think indenting paragraphs should be
>dealt with in style sheets -- that would give me an opportunity 
>to turn it off. *grin*

I thought of maybe <P TAB> vs <P> to tab or not to tab...  but there
are cases outside of a <P></P> block one might want to tab over text.
And having <TAB> allows for something later, like maybe

<SETTAB ID=1 5%>
<TAB TO=1> 
would indent 5%

As well as the abilities given in 3.0 where you can tab over to align
with any ID setting.

I admit it isn't crystalized, more like jello, but I'm thinking of
future possibilities.

As for the browsers that indent <P> already, it is an implimentation
issue.  If they add support for <TAB> then I would drop the indentation
of <P>.  Or add logic so that <P><TAB> only gets *one* indent, but say
<P><TAB><TAB> gets two, etc.

It won't break any existing systems.

TAB should have more uses than indenting paragraphs.

Although I work for Livingston Enterprises Technical Support, I alone am
responsible for everything contained herein.  So don't waste my managers'
time bitching to them if you don't like something I've said.  Flame me.
Phone: 800-458-9966  <> 
FAX: 510-426-8951    6920 Koll Center Parkway #220, Pleasanton, CA 94566