- From: Daniel Weck via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 07 Feb 2011 00:09:58 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-speech
In directory hutz:/tmp/cvs-serv27646
Modified Files:
Overview.html Overview.src.html
Log Message:
added new pending issues.
removed the descendants restriction for speakability:none and explained the expected behavior with pause collapsing and additive adjacent rests.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-speech/Overview.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- Overview.html 6 Feb 2011 21:51:00 -0000 1.22
+++ Overview.html 7 Feb 2011 00:09:56 -0000 1.23
@@ -38,13 +38,13 @@
<h1 id=top>CSS3 Speech Module</h1>
- <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 06 February
+ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 07 February
2011</h2>
<dl>
<dt>This version:
- <dd><!--<a href="http://www.w3.org/TR/2011/WD-css3-speech-20110206">http://www.w3.org/TR/2011/ED-css3-speech-20110206</a>-->
+ <dd><!--<a href="http://www.w3.org/TR/2011/WD-css3-speech-20110207">http://www.w3.org/TR/2011/ED-css3-speech-20110207</a>-->
<a
href="http://dev.w3.org/csswg/css3-speech">http://dev.w3.org/csswg/css3-speech</a>
@@ -162,7 +162,13 @@
CR period if there has not been enough interest from implementers:
<ul>
- <li><a href="#issue-phonemes">phonemes</a></li>
+ <li><a href="#issue-phonemes">phonemes</a>
+
+ <li><a href="#issue-voice-cues-volume">audio cues volume level relative to
+ voice-volume</a>
+
+ <li><a href="#issue-speakability-name">"speakability" not an ideal name
+ ?</a></li>
<!-- li><a href="#issue-mark">mark</a></li -->
<!-- li><a href="#issue-speak_none">speak:none</a></li -->
</ul>
@@ -456,11 +462,23 @@
class=property>voice-volume</code></a>’ refers to the amplitude of
the waveform output by the speech synthesiser. This may be mixed with
other audio sources, influencing the perceived loudness of synthetic
- speech relative to these sources. ‘<a href="#voice-volume"><code
+ speech relative to these sources.
+
+ <p> ‘<a href="#voice-volume"><code
class=property>voice-volume</code></a>’ does not apply to <a
href="#cue-props">audio cues</a> for which there is a separate means to
set loudness (absolute, or relative to ‘<a
href="#voice-volume"><code class=property>voice-volume</code></a>’).
+ <span class=issue id=issue-voice-cues-volume> ISSUE: shouldn't audio cues
+ be subjected to the voice-volume, so that an inaudible element gets its
+ entire content (within the aural "box" model) muted as well ? The
+ rationale is that voice-volume:silent is largely equivalent to
+ visibility:hidden, which affects border, padding and spacing (i.e. the
+ entire content with regards to the CSS "visual" box model). The audio cues
+ should therefore only be allowed to set their volume levels
+ <em>relatively</em> to the inherited voice-volume, not with absolute
+ values as these may incorrectly enable audio output when the voice-volume
+ itself is muted. </span>
<p>Values have the following meanings:</p>
<!-- dl>
@@ -520,8 +538,11 @@
the ‘<a href="#voice-volume"><code
class=property>voice-volume</code></a>’ value and may therefore
generate audio output). The latter requires no time and is not rendered in
- the aural dimension (including its descendants, which cannot override the
- inherited ‘<code class=property>none</code>’ value).
+ the aural dimension
+ <!-- (including its descendants, which cannot override the inherited 'none' value). -->
+ (although descendants may override the ‘<a
+ href="#speakability"><code class=property>speakability</code></a>’
+ value and may therefore generate audio output).
<table class=propdef summary="name: syntax">
<tbody>
@@ -667,6 +688,9 @@
<td>speech
</table>
+ <p class=issue id=issue-speakability-name> ISSUE: should the "speakability"
+ property be named differently ? e.g. "speaking"
+
<p>This property specifies whether text will be rendered aurally.
<p>Values have the following meanings:
@@ -686,10 +710,18 @@
<dd> This value causes an element (including pauses, cues, rests and
actual content) to not be rendered (i.e., the element has no effect in
- the aural dimension). Descendant elements do not get rendered either;
- this behavior cannot be overridden by setting the ‘<a
- href="#speakability"><code class=property>speakability</code></a>’
- property on the descendants.
+ the aural dimension).
+ <p class=note> Note that any of the descendants of the affected element
+ are allowed to override this value, so they may actually take part in
+ the aural rendering. However, the pauses, cues, and rests of the
+ ancestor element remain "deactivated" in the aural dimension, and
+ therefore do not contribute to the <a href="#collapsing">collapsing of
+ pauses</a> or additive behavior of adjacent rests.</p>
+ <!--
+Descendant elements do not get rendered either;
+this behavior cannot be overridden by setting the 'speakability' property on the descendants.
+-->
+
<dt><strong>normal</strong>
@@ -708,11 +740,10 @@
class=property>normal</code>’. In the case of ‘<code
class=property>normal</code>’, this would result in descendants
being rendered in the aural dimension even though they would not be
- rendered in the visual space. To ensure that an element <em>and its
- descendants</em> do not get rendered in the aural dimension, use the
- ‘<code class=property>none</code>’ value for the ‘<a
- href="#speakability"><code class=property>speakability</code></a>’
- property.</p>
+ rendered on the visual canvas.
+ <!-- To ensure that an element <em>and its descendants</em> do not get rendered in the aural dimension,
+use the ‘<code class=property>none</code>’ value for the ‘<code class=property>speakability</code>’ property. -->
+ </p>
<!-- p class="note">
Note that the value of the ‘<code class=property>visibility</code>’ property (see [[!CSS3BOX]])
may affect the computed value of ‘<code class=property>voice-volume</code>’, but do not affect the ‘<code class=property>speakability</code>’ property.
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-speech/Overview.src.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- Overview.src.html 6 Feb 2011 21:51:00 -0000 1.23
+++ Overview.src.html 7 Feb 2011 00:09:56 -0000 1.24
@@ -99,6 +99,8 @@
implementers:
<ul>
<li><a href="#issue-phonemes">phonemes</a></li>
+<li><a href="#issue-voice-cues-volume">audio cues volume level relative to voice-volume</a></li>
+<li><a href="#issue-speakability-name">"speakability" not an ideal name ?</a></li>
<!-- li><a href="#issue-mark">mark</a></li -->
<!-- li><a href="#issue-speak_none">speak:none</a></li -->
</ul>
@@ -266,9 +268,21 @@
<p>The 'voice-volume' refers to the amplitude of the waveform output by
the speech synthesiser. This may be mixed with other audio sources,
influencing the perceived loudness of synthetic speech relative
-to these sources. 'voice-volume' does not apply to <a href
+to these sources.
+</p>
+<p>
+'voice-volume' does not apply to <a href
="#cue-props">audio cues</a> for which there is a separate means
-to set loudness (absolute, or relative to 'voice-volume').</p>
+to set loudness (absolute, or relative to 'voice-volume').
+
+<span class="issue" id="issue-voice-cues-volume">
+ISSUE: shouldn't audio cues be subjected to the voice-volume,
+so that an inaudible element gets its entire content (within the aural "box" model) muted as well ?
+The rationale is that voice-volume:silent is largely equivalent to visibility:hidden,
+which affects border, padding and spacing (i.e. the entire content with regards to the CSS "visual" box model).
+The audio cues should therefore only be allowed to set their volume levels <em>relatively</em> to the inherited voice-volume, not with absolute values as these may incorrectly enable audio output when the voice-volume itself is muted.
+</span>
+</p>
<p>Values have the following meanings:</p>
@@ -325,7 +339,8 @@
including any pause before and after the element, but no sound is generated
(although descendants may override the 'voice-volume' value and may therefore generate audio output).
The latter requires no time and is not rendered in the aural dimension
-(including its descendants, which cannot override the inherited 'none' value).
+<!-- (including its descendants, which cannot override the inherited 'none' value). -->
+(although descendants may override the 'speakability' value and may therefore generate audio output).
</p>
@@ -448,6 +463,10 @@
</tbody>
</table>
+<p class="issue" id="issue-speakability-name">
+ISSUE: should the "speakability" property be named differently ? e.g. "speaking"
+</p>
+
<p>This property specifies whether text will be rendered aurally.</p>
<p>Values have the following meanings:</p>
@@ -464,8 +483,19 @@
This value causes an element
(including pauses, cues, rests and actual content)
to not be rendered (i.e., the element has no effect in the aural dimension).
+<p class="note">
+Note that any of the descendants of the affected element
+are allowed to override this value, so they may actually take part in the aural rendering.
+However, the pauses, cues, and rests of the ancestor element remain
+"deactivated" in the aural dimension,
+and therefore do not contribute to the
+<a href="#collapsing">collapsing of pauses</a>
+or additive behavior of adjacent rests.
+</p>
+<!--
Descendant elements do not get rendered either;
this behavior cannot be overridden by setting the 'speakability' property on the descendants.
+-->
</dd>
<dt><strong>normal</strong></dt>
@@ -477,9 +507,9 @@
<p class="note">
Note that although the 'none' value of the 'display' property cannot be overridden by descendants of the affected element (see [[!CSS3BOX]]),
the 'auto' value of 'speakability' can however be overridden by descendants, using either of 'none' or 'normal'.
-In the case of 'normal', this would result in descendants being rendered in the aural dimension even though they would not be rendered in the visual space.
-To ensure that an element <em>and its descendants</em> do not get rendered in the aural dimension,
-use the 'none' value for the 'speakability' property.
+In the case of 'normal', this would result in descendants being rendered in the aural dimension even though they would not be rendered on the visual canvas.
+<!-- To ensure that an element <em>and its descendants</em> do not get rendered in the aural dimension,
+use the 'none' value for the 'speakability' property. -->
</p>
<!-- p class="note">
Received on Monday, 7 February 2011 00:10:00 UTC