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

Re: "phonemes" property in the CSS3 Speech module

From: Christoph Päper <christoph.paeper@crissov.de>
Date: Fri, 4 Feb 2011 16:07:49 +0100
Message-Id: <D0CA62ED-28A9-4019-9A35-64CE634E143F@crissov.de>
To: "www-style@w3.org list" <www-style@w3.org>
Daniel Weck:

> Please note that although the "tomato" pronunciation example indeed ties-in well with the concept of "dialect" (different accents), there are other use-cases whereby the disambiguation is required within the *same* "dialect". For example, the text token "read" in british english may be spoken as 'reed' or 'red'. Text-To-Speech engines usually process such token based on the surrounding context, but there are cases where the lack of context requires explicit authoring of a pronunciation rule (e.g. the line of text "I read it.").

So the discussion is about how this should be marked up …

  I <x style="phonemes:rɛd">read</x> it.

  I <x id="read-1">read</x> it.
  #read-1 {phonemes: rɛd}

  I <x class="read-simple-past">read</x> it.
  .read-simple-past {phonemes: rɛd}

  I <x class="IPA-rɛd">read</x> it.
  .IPA-rɛd {phonemes: rɛd}

  I <x speak="rɛd">read</x> it.
  [speak] {phonemes: attr("speak", string)}

  I <x grammar="tense:past, simple">read</x> it.

  <x grammar="tense:past, simple">I read it.</x>

… and consequently which of these CSS should support and thereby encourage?

I think the CSS Speech module should deal with dialect variations and proper names in Level 3, but should leave grammatical variation that is not graphemically encoded to Level 4 or markup languages altogether.
Received on Friday, 4 February 2011 15:08:27 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:43 UTC