View Single Post
Old 12-17-2022, 05:30 AM   #33
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,212
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 graycyn View Post
There is this little phenomenon where technology continues to develop as years pass ... you know, once upon a time, we had no reason to discuss this issue, because THERE WERE NO EBOOKS or EREADERS and HTML5 did not exist yet.

By the way, TTS can, in some apps, actually pronounce foreign language words correctly if they are marked up with the appropriate language. So it's not *that* far of a jump to think that eventually, TTS/screen readers could emphasize a word as well.

If I want to take the time to create better semantics, why not? Who, exactly, does it harm? The average reader could care less about the code and it's not even that much bloat!
How would you read <i> and <em> differently anyway when they are both needing to be read so you get the idea it's italicized?
JSWolf is offline   Reply With Quote