View Single Post
Old 04-14-2025, 05:11 PM   #11
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,173
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 Karellen View Post
You won't see a difference between <i> and <em> in ereaders, unless you have specifically styled them differently in the CSS.

My understanding is that it is helpful for accessibility coding. ie for Read Aloud software. If you want to emphasize certain words in a sentence, you would use <em>, but if you just need italics, say for the name of a ship (USS Enterprise) then you would use <i> because you don't want the voice reader to emphasize the name of the ship.

I would never use <span>s for bold or italic.

In my css I use

em, i, .italic {
font-style: italic;
}

b, strong, .bold {
font-weight: bold;
}
You don't need that CSS for i, em, b, strong.

Can you point out a TTS that reads <em> differently then <i>? Nobody has been able to name one when I've asked.
JSWolf is offline   Reply With Quote