Quote:
Originally Posted by JSWolf
I'll bet you it won't come in my lifetime. You need a program that does TTS and looks at the code when doing so. Screen reads are not that.
<em> was not created to be different then <i>. It was created to replace <i> (because it was decide to deprecate <i>) until it was decided that it was a mistake and <em> was still kept because programs supported <em>.
Gotta love a standards committee that does things just because they can and not because they should aka some of the nonsense with ePub 3 (thanks to a committee).
|
Maybe it
won't (come in our lifetimes). But,Jon, does that mean we oughn't do it, when we know it's the right sort of tack to take?
Even
if I'm on the wrong side of the dirt when/if this is ever adopted universally; even if "em" is no longer used, but has been superseded by something
else, ("momentous!"), doing it right, now, will allow my successors to regex it (or whatever replaces that...looks around in suspicious paranoia for her friend
Gilliigan, her ChatGPI 4 API...) and make it user-friendly.
I resisted it for a while, (mostly due to a lack of a single adopted standard), but...I think about the things that are different for
me now, over the last 5 years of aging; I think of my husband's Grandmother and his Dad, both
vociferous readers who lost their vision and were thus reliant upon Audiobooks and...my attitude is,
I can do this little extra thing.
Hitch