View Single Post
Old 04-14-2025, 04:10 PM   #8
ElMiko
Evangelist
ElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileRead
 
ElMiko's Avatar
 
Posts: 455
Karma: 65460
Join Date: Jun 2011
Device: Kindle
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;
}
Yup, I understand that the visuals wouldn't change (in most systems). In post #3 I was referring particularly to text-to-speech. That is, aurally, all three examples were rendered the same way. And I'm wondering a) why no difference (aurally) between <i>, <em>, and plain text, and b) for TTS, does it matter if the punctuation is inside the tags or outside them (eg. <em>"what?"</em> vs. "<em>what</em>?")
ElMiko is offline   Reply With Quote