- From: Daniel Weck <daniel.weck@gmail.com>
- Date: Tue, 7 Jun 2011 09:29:25 +0100
- To: fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
On 7 Jun 2011, at 08:24, Daniel Weck wrote: > On 7 Jun 2011, at 02:25, fantasai wrote: >> On 06/07/2011 03:47 AM, Daniel Weck wrote: >>> Good point. Voice names are space-separated in SSML's 'name' >>> attribute, but values are comma-separated in the 'voice-family' >>> CSS property. I agree that the CSS Speech module should allow >>> spaces in (quoted) voice names, >> >> I agree. Certainly the CSS Speech module should not make any >> restrictions on >> string values. It can make restrictions on unquoted names, however. >> >> Possibilities: >> - Allow unquoted names per font-family, concatenating adjacent >> idents with a single space. >> - Allow unquoted names per font-family, concatenating adjacent >> idents with a single underscore. >> - Allow unquoted names only as a single ident. This would work fine >> for names with underscores, >> but names with spaces would need quoting. > > Yes, we need to disambiguate the handling of adjacent, whitespace- > separated identifiers. I prefer option #1, as this matches 'font- > family': > > http://www.w3.org/TR/CSS21/fonts.html#font-family-prop > > " > If a sequence of identifiers is given as a font family name, the > computed value is the name converted to a string by joining all the > identifiers in the sequence by single spaces. > " Prose now heavily updated to match the 'font-family' model: http://dev.w3.org/csswg/css3-speech/#voice-props-voice-family Cheers, Dan
Received on Tuesday, 7 June 2011 08:29:56 UTC