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

Re: [css3-speech] voice-pitch

From: Daniel Weck <daniel.weck@gmail.com>
Date: Wed, 13 Jul 2011 21:51:15 +0100
Message-Id: <D5F689F1-63C9-47C8-AE6F-98AD47A851BF@gmail.com>
To: www style <www-style@w3.org>, fantasai <fantasai.lists@inkedblade.net>
Thanks!

http://dev.w3.org/csswg/css3-speech/#voice-pitch


On 13 Jul 2011, at 21:40, fantasai wrote:

> On 07/13/2011 01:02 PM, Daniel Weck wrote:
>> 
>> On 13 Jul 2011, at 20:28, fantasai wrote:
>>>> I would expect a speech engine to support a specific range of admissible
>>>> frequencies, and to gracefully handle "awkward"  values such as 0Hz.
>>> 
>>> You should specify this explicitly -- that there may be UA-specific limits
>>> on the frequency and that UAs must clamp out-of-range actual (as opposed to
>>> used or computed) values to this range.
>> 
>> What about this?
>> ...
> 
> Pretty good, but I would say, take the sentence
>  "Computed absolute frequency values that are negative are clamped to zero Hertz."
> out of the value definitions and prepend it to the "Speech-capable user agents"
> paragraph. Then move that entire thing after the property value definition list,
> since it's better to get an overview of the values first before describing this
> detail.
> 
> # absolute
> #   This keyword specifies that the provided frequency is expressed as an absolute,
> #   positive value. When a negative value is provided, it is clamped to zero.
> 
> For the first sentence:
>  s/provided/specified/
>  s/positive//
>  s/is expressed as/represents/
> Change the second sentence to
>  If a negative frequency is specified, the computed frequency will be zero.
> which is a little more accurate as to which values are affected how.
> 
> ~fantasai
> 
Received on Wednesday, 13 July 2011 20:51:46 GMT

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