View Single Post
Old 08-10-2023, 11:57 AM   #1680
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,092
Karma: 169815798
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
If the TTS is any ood, it will read italics properly. <em> is not needed. It should be <i>. <em> was invented to replace <i> when <i> was very mistakenly removed from HTML 5. So <em> doesn't actually need to exist since they allowed <i> back.
Not quite right, Jon. If for instance the <i> is wrapped around the name of a ship, say <i>HMCS Algonquin</i>, the name would be correctly spoken with no emphasis. Whereas in the example above, the <em>knew</em> would be correctly spoken with emphasis. Visually there might be no difference between using either tag but using TTS, they are very different. The <em> tag semantically emphasizes the important word(s) while <i> tag is just text conventionally styled in italic.

Much as adding accessibility components to an ebook does not make any difference when using your eyeballs to read the book but it can and does make a lot of difference for someone who is using TTS to access the ebook, using the <em> and <i> tags correctly costs me little and can be very useful to others.
DNSB is offline   Reply With Quote