W3C home > Mailing lists > Public > public-html@w3.org > October 2008

Re: <q>

From: Ben Boyle <benjamins.boyle@gmail.com>
Date: Tue, 28 Oct 2008 23:51:04 +1000
Message-ID: <5f37426b0810280651kd11bc4bl809d7efa898f3486@mail.gmail.com>
To: "Justin James" <j_james@mindspring.com>
Cc: "Ivan Enderlin" <w3c@hoa-project.net>, "Olivier GENDRIN" <olivier.gendrin@gmail.com>, "Sam Kuper" <sam.kuper@uclmail.net>, "Chris Wilson" <Chris.Wilson@microsoft.com>, "HTML WG" <public-html@w3.org>

On Tue, Oct 28, 2008 at 11:32 PM, Justin James <j_james@mindspring.com> wrote:
> I misspoke... my problem is with the idea of <q> inserting any kind of
> punctuation.

I know where you're coming from. Worth remembering this handy css: quotes: none;

Others can use this to specify quote marks they want.
All catered for already in the specs.

> Huge problems with this, as noted above. In addition, what about UAs that
> use a default stylesheet different from what the author expects?

Author stylesheet should override UA.

> Or do not use CSS at all?

Any browsers in this category that would actually render quotes in the
first place?
I can understand the problem in theory, but I think it's something
we're unlikely to encounter.

> What if the quote contains a quote? Should the inside quote
> also use <q>? What if the inner contents come from elsewhere, like an
> authoring tool or are pulled from XML and inserted via JavaScript? No, I
> think that the idea of <q> rendering quotes, regardless of the rules it
> uses, is a very bad idea.

Yep, well, you don't have to use <q>. Use punctuation instead of markup.
Anyone tried <q> with and without specifying quotes in css with voice
browsers? It's fun.

ps: Thanks to those for answering the english/french nesting question.
Appreciate that.

Received on Tuesday, 28 October 2008 13:51:45 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:38 UTC