W3C home > Mailing lists > Public > www-style@w3.org > July 2011

Re: [css3-speech] voice-family

From: Daniel Weck <daniel.weck@gmail.com>
Date: Wed, 6 Jul 2011 20:10:15 +0100
Message-Id: <B03B37A5-5536-4FF8-9C6E-F017481D0469@gmail.com>
To: "www-style@w3.org style" <www-style@w3.org>, fantasai <fantasai.lists@inkedblade.net>
On 6 Jul 2011, at 18:20, fantasai wrote:
>> Since we explicitly leave the matching algorithm up to the  
>> synthesizer it
>> might even be necessary to write something like:
>>
>> voice-family: 60 male, 60 female, 30 male, 30 female;
>>
>> The intent here is to prefer a mature male voice if one is  
>> available, with
>> a mature female next, followed by an adult male etcetera.  
>> Essentially trying
>> prioritize age over gender.
>
> What happens if I have a male voice that's 55 years old? Do I use  
> that, or
> fall back to 60-year-old female?

Well, a concrete voice instance available on the user's system is  
likely to support an age range. So your example would actually be more  
accurate as such: I have a "male voice suitable for 40-50 years old",  
which would not get selected based on the author's criteria "60  
male" (nor would it based on any of the other author-provided  
alternatives).

So I think we are missing prose similar to font-family for defining  
the mapping between a generic voice-family and "best-match" candidates  
on the user's system:

---
User agents should provide reasonable default choices for the generic  
font families, which express the characteristics of each family as  
well as possible within the limits allowed by the underlying technology.
User agents are encouraged to allow users to select alternative  
choices for the generic fonts.

---

http://www.w3.org/TR/CSS21/fonts.html#generic-font-families
Received on Wednesday, 6 July 2011 19:10:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT