View Single Post
Old 04-10-2023, 05:23 PM   #53
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by JSWolf View Post
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.
What? It's already here. Click on the Braille topic. Watch the linked DAISY videos.

How the hell do you think programs read the HTML, convert to SSML, and feed it to the OS's Text-to-Speech engines?

Quote:
Originally Posted by JSWolf View Post
<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>.
Again. Read the HTML5 specs.

It's absurd to continue acting as if it's 1997 + HTML4.0.

There has been 25 years of enhancements since then, and billions of non-English speakers brought onto the internet.

As has been described to you a thousand times before, Internationalization was one of the huge enhancements of HTML5 over HTML4.
Tex2002ans is offline   Reply With Quote