View Single Post
Old 04-15-2025, 02:02 PM   #24
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,399
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
What is the CSS to change <em> so it's different from <i> when read by TTS but the same visually? Also, what TTS software reads <em> and <i> differently?
No CSS is needed. If the ePub to speech is standards compliant, the <i> and <em> tags are all that is needed. Visually, both default to using italic unless you deliberately modify that behaviour.

As I mentioned the Victor device does not care if it is reading ePub2 or ePub3. If you are reading ePub3, you can use SSML and a pronunciation lexicon to improve the quality. You may want to take a look at the CSS Speech Module chunk of the ePub3 specification mentioned by @Turtle91 or the CSS Speech article in Daisy's knowledge base articles.

Last edited by DNSB; 04-15-2025 at 02:15 PM.
DNSB is offline   Reply With Quote