Thread: HTML question about italics and bold
View Single Post
Old 04-15-2025, 07:45 AM   #17
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,190
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Turtle91 View Post
You can change how emphasized words are spoken using css assuming the device supports the standards... you can also change how emphasized words are displayed with css.

The defaults of <i>/<em> and <b>/<strong> are the same (italics and bold respectively) but they can be changed. So Wolfe's assertion that there is no difference is a little misleading. There is a semantic difference. <i> is for a visual only presentation (however you want it to look), while <em> is whether the word is supposed to be emphasized (typically when read aloud, but even when you are visually reading the word - I can assign an emphatic voice in my mind while reading...) DNSB gave a good example in #9.

Whether or not anyone has used a device that sufficiently differentiates the semantic coding does not invalidate the difference in coding...

I also choose to code my books with the assumption that meeting accessibility standards, as well as proper use of semantic tags, will just make the books better as/when devices improve their support... I also won't have to go fix the books if a major portion of the world passes laws requiring book producers to follow accessibility standards (like the EU did)....
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?
JSWolf is offline   Reply With Quote