- From: Belov, Charles <Charles.Belov@sfmta.com>
- Date: Wed, 20 Oct 2010 16:33:55 -0700
- To: <www-style@w3.org>
- Cc: "fantasai" <fantasai.lists@inkedblade.net>, "Claudio Santambrogio" <csant@opera.com>
> -----Original Message----- > From: www-style-request@w3.org > [mailto:www-style-request@w3.org] On Behalf Of fantasai > Sent: Wednesday, October 20, 2010 1:52 PM > To: www-style@w3.org; Claudio Santambrogio > Subject: [css3-speech] Drop phonemes section, mark properties > > Just from a quick scan through the last WD... > > http://www.w3.org/TR/2004/WD-css3-speech-20041216/#phonetic-props > > The phonemes section of css3-speech seems a little too > closely tied to the content to be stylistic. I suggest > dropping it; the use case should be handled by the markup somehow. > Would you be so kind as to provide an example as to how this would be handled by the markup? I actually think it does not go far enough. I don't know whether CSS3 contemplates content as selector, but given the example in the draft: @phonetic-alphabet "ipa"; #tomato { phonemes: "t\0252 m\0251 to\028a " } (which I would suggest changing to @phonetic-alphabet "ipa"; ..tomato { phonemes: "t\0252 m\0251 to\028a " } unless one is sure there will be only one occurrence of the word "tomato" on the page). Given my modified example, <p>I have a <span class="tomato">tomato</span> on my plate. This <span class="tomato">tomato</span> happens to be yellow, however.</p> using class selectors, I would need to go through and replace all un-spanned examples of "tomato" with the spanned version '<span class="tomato">tomato</span>'. Very tedious unless one is using a content management system; even then it adds bloat to the page. Better yet would be a content-based selector: @phonetic-alphabet "ipa"; [\wtomato\w] { phonemes: "t\0252 m\0251 to\028a " } which would leave the markup clean: <p>I have a tomato on my plate. This tomato happens to be yellow, however.</p> I do have a real-world concern use case that "Muni" (the San Francisco public transportation system) is pronounced Mew-nee not Moo-nee, and it would be tedious/bloating to have to tag it wherever it occurs rather than being able to specify it once in a style sheet. This also applies to many street names in San Francisco, and, I imagine elsewhere, as well as many company names. Or perhaps there needs to be a vocabulary-pronunciation download facility similar to what is being done with downloadable fonts. My apologies if this is too far off from your post. Hope this helps, Charles Belov SFMTA Webmaster
Received on Wednesday, 20 October 2010 23:41:36 UTC