Quote:
Originally Posted by JSWolf
Sure, why not. Nobody has yet to come up with a TTS that reads <em> and different then <i>. So why bloat the code with <em> when <i> will do perfectly well?
|
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!