W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10320] Allow an arbitrary string as the voice for forwards compatilbity

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Sep 2010 08:11:14 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Ov48A-0002WE-Iy@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10320





--- Comment #4 from Philip Jägenstedt <philipj@opera.com>  2010-09-13 08:11:14 ---
Is there a reason to differentiate between predefined voices and predefined
tags? Given that they use the same syntax, I think it would be simplest for
both implementors and authors to unify the handling of them, simply calling
them tags. (Any tag can have a predefined style, and perhaps <narrator> and <i>
are both italic by default.)

As for "extensibility", how about saying that we any tag name with a - (hyphen)
in it may be used by authors for styling purposes. If they use this to style
specific speakers, that's fine. <-hixie>, <ian-says> or <i-h> would all be ok
to style parts spoken by you.

I think it's OK that CSS glue also works for new tag names without hyphens, but
that validators should warn about it. That makes it easier to introduce new
tags and style them in older UAs. That would be just like HTML, and hopefully
people won't go overboard in abusing it.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 13 September 2010 08:11:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC