Re: whither <u>...</u>?
"Daniel W. Connolly" <connolly@oclc.org>
Date: Wed, 15 Jun 94 15:32:41 EDT
Message-id: <9406151932.AA00878@ulua.hal.com>
Reply-To: html-ig@oclc.org
Originator: html-ig@oclc.org
Sender: html-ig@oclc.org
Precedence: bulk
From: "Daniel W. Connolly" <connolly@oclc.org>
To: Multiple recipients of list <html-ig@oclc.org>
Subject: Re: whither <u>...</u>?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Implementation Group
In message <9406151919.AA00859@ulua.hal.com>, "Daniel W. Connolly" writes:
>
>My vote: put it in for use in RTF, rainbow, etc. converters, but
>don't requre that it be rendered differently from B and I.
>
Hmmm... on the other hand, I'd like for the 2.0 DTD to represent
the set of stuff that's known to generally work. I'd like for folks
to be able to trust that any document that parses by the 2.0 DTD
will work with what's "out there," including Mosaic 2.x.
So I'm changing my vote: leave it out. And leave out STRIKE, and
whatever else is not consistently supported.
Then we're back to the question of how to represent "proposed"
elements.
More on that later....
Dan