View Single Post
Old 12-17-2022, 02:00 AM   #32
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,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by graycyn View Post
Should I get rid of "THE END" in a vintage text?
One word:

No.

THE END!

Quote:
Originally Posted by JSWolf View Post
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?
I linked to many (and many) within the DAISY Consortium's videos.

Also, actual screen readers:
  • JAWS
  • NVDA

already can—and do—distinguish between <i> + <em>.

They can also handle multiple languages in the HTML lang as well! (So can Thorium Reader!)

Just because most e-readers are limited on this emphasis/language stuff, doesn't mean you have to keep insisting every single ebook you create not follow the standards according to the best of your ability.

Last edited by Tex2002ans; 12-17-2022 at 02:10 AM.
Tex2002ans is offline   Reply With Quote