I thought I had submitted these ages ago, but I can't find them anymore so maybe I never did. Anyway, at the following URLs are an XHTML to SSML transformation for passing to Ceptral's speech synthesiser ‘Swift’, and an SSML to AppleTalk transformation for passing to Macintalk if Swift is unavailable or the user prefers Macintalk. Neither transformations are complete and feedback is strongly welcome. http://web.nickshanks.com/stylesheets/xhtml2ssml.xslt http://web.nickshanks.com/stylesheets/ssml2macintalk.xslt Notable features: • Preservation of xml:lang • Title attribute of abbreviations and acronyms read out • Omission of "http://www." at the start of web links. • Pauses, emphasis and de-emphasis for tags like <br>, <em> and <small> • Assuming you declare the ssml namespace, "http://www.w3.org/2001/10/synthesis", you can encode pronunciations directly into your XHTML: The place where I live is called <ssml:phoneme alphabet="x-apple-macintalk" ph="hAXrtfIXdSIXr"><ssml:phoneme ph="h a1 r t f ah0 d sh ah0 r"><!-- alphabet="x-cepstral-swift" -->Hertfordshire</ssml:phoneme></ssml:phoneme> To demonstrate the difference, select the following text and have the speech engine read it out: [[PHON]] hAXrtfIXdSIXr [[TEXT]] Hertfordshire n.b: In its current version Swift ignores phoneme elements with an alphabet attribute. I reported this and suggest they use x-cepstral-swift. It also reads out DOCTYPES, which is why the SSML transformation doesn't output one. Notable bugs: • I don't know how to return pitch, volume and emphasis values back to their pre-adjustment state in Macintalk (which uses a state machine rather than a tree), e.g: <em> fe <em> fi </em> fo </em> fum would become: [[EMPH +]] fe [[EMPH +]] fi fo fum not [[EMPH +]] fe [[EMPH +]] fi [[EMPH -]] fo [[EMPH -]] fum
Sorry, that example should have read: [[inpt PHON]] hAXrtfIXdSIXr . [[inpt TEXT]] Hertfordshire
What is the WebKit bug here?
It's a feature request, well, you could call it a bug that WebKit support for speech sucks :-) Obviously CSS is ignored too.
File web standard enhancement requests like this against the W3C specs for CSS Speech or the Web Speech API, both of which WebKit supports to some degree. Reopen if there is already a spec covering this phoneme pronunciation.