the features you refer to are marked "at risk" in CSS3-Speech, and have therefore not been included in the EPUB CSS Profile. This decision stands. However, note that Reading Systems may still implement support for these features, and stylesheets may still include them, something that would contribute to removing  the "at-risk" branding from the CSS WD.
The informative statement in the Overview document that you refer to ("such as pronunciation, volume, pitch and rate"), will be changed to "such as pronunciation, prosody and voice characteristics". Thanks for noting this inconsistency.
On Sep 7, 2011, at 7:48 AM, jtchen0901 wrote:
> hi Markus,
> According to the chapter,
> http://idpf.org/epub/30/spec/epub30-overview.html#sec-tts ,
> the EPUB 3 should provide the TTS facilities such as pitch and rate.
> However, in the section 3.3.3 CSS 3.0 Speech,
> the '-epub-voice-rate' and '-epub-voice-pitch' are omitted.
> Since the real world voice book products are already able to adjust the
> voice rate by hand,
> I suggest you to consider putting both '-epub-voice-rate' and
> '-epub-voice-pitch' attributes back to the section 3.3.3.
> Jiang-Chun Chen
> 寄件者: "Markus Gylling" <markus....@gmail.com>
> 日期: 2011年9月7日 06:37
> 收件者: "Google Groups EPUB" <epub-work...@googlegroups.com>
> 主旨: new draft available
>>  http://idpf.org/epub/30/spec/=
> 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.
I recommend that we use simply state the following:
The ability of Reading Systems to paginate absolutely positioned layouts
is not guaranteed.
In 3.3.4, we specifically require an RS to support OpenType and correctly
refer to the ISO version of that specification.
However, there are many people who believe that OTF fonts only include
SFNT-based (aka TrueType) content and do not also implement the CFF-based
version. Do we think there is a need for a NOTE about the need for
On 9/6/11 6:37 PM, "Markus Gylling" <markus....@gmail.com> wrote:
Please note that "pitch" and "rate" CSS properties were *not* included in the EPUB3 CSS-Speech subset, these features were/are only (wrongly) mentioned in the "overview" section, see my recent email about rectifying this issue (Markus, thank you for fixing the first sentence of [2.10 Text-to-speech], which I did not catch):
> Since discussions about "fixed format" are still ongoing, I'd like to
> suggest a rewording of the NOTE in 3.3.1.
I see the point you (and Dave C) are making. However, as I recall (and as unlikely as it perhaps may seem) we spent quite some time fiddling with this passage early this year to get it to a state that everyone could live with. Therefore I am really hesitant to change it now.
Future minor updates can revise this passage to adapt it to changes in the environment.
Hope this works for you.
Thanks for this suggestion. As there is a potentially infinite amount of such clarifying notes we could add, I have added this as an issue to the tracker with status deferred (a label we to use facilitate retrieval in the future when doing revision work).
This means that I am suggesting we do not make any edits to the spec now with regards to this suggestion; let me know if this does not work for you.
[Apologies in advance if this has been previously discussed] In 3.3.4, we specifically require an RS to support OpenType and correctly refer to the ISO version of that specification. However, there are many people who believe that OTF fonts only include SFNT-based (aka TrueType)
* fixed profile reference in ContentDocs 126.96.36.199 (r3171)
* fixed a typo (missing word) in ContentDocs 188.8.131.52.3 (r3172)
* fixed profile reference and corrected example indentation in MediaOverlays (r3173, r3174)
* fixed CSS Writing Modes dated reference in ContentDocs 3.3.6 (r3175)
* fixed informative prose re CSS Speech in Overview 2.10 (r3176)
* added restriction on -epub-hyphens 'all' value in ContentDocs 3.3.5 (r3176)
(Note, in the list above, the parentheses reference the revision number. Refer to http://code.google.com/p/epub-revision/updates/list for diffs.)