Re: Wish List for New Spec

Scott E. Preece (preece@predator.urbana.mcd.mot.com)
Tue, 2 Jan 1996 10:26:57 -0600


Date: Tue, 2 Jan 1996 10:26:57 -0600
From: preece@predator.urbana.mcd.mot.com (Scott E. Preece)
Message-Id: <199601021626.KAA00226@predator.urbana.mcd.mot.com>
To: boo@best.com
Cc: www-html@w3.org
In-Reply-To: boo@best.com's message of Tue, 2 Jan 1996 08:13:29 -0800
Subject: Re: Wish List for New Spec

   From: boo@best.com (Walter Ian Kaye)
|
|   >The other reason for using the Q element, instead of entities, is that
|   >it allows USa to know that the material is a quotation.  This would
|   >allow a tool to, for instance, search only quoted material, exclude
|   >quoted material from a concordance, or present quotations in more styled
|   >ways than just changing the quote ccharacters (setting them in another
|   >font, for instance, or on a different background, or as sidebars, or
|   >using different rules to decide when to blockquote and when to inline
|   >quote).
|
|   Ah, but you could still do &guillemotleft;<SPAN CLASS="quote">The quotation
|   here</SPAN>&guillemotright; and achieve the same effect. (I'm guessing at
|   the entity names.)
---

That's not quite the same thing, since it puts the quotation marks
outside the material that is identified as a quote, implying that the UA
can't decide whether or not to use quotation marks at all (if the UA
chooses to show the quotation out-of-line, as an indented block or a
sidebar, the presence of the quotation marks outside that presentation is
going to be distinctly odd).

And why would you want to use the class attribute when there's already
an element for the specific purpose of handling quotations?

scott

--
scott preece
motorola/mcg urbana design center	1101 e. university, urbana, il   61801
phone:	217-384-8589			  fax:	217-384-8550
internet mail:	preece@urbana.mcd.mot.com