View Single Post
Old 06-12-2020, 05:18 AM   #14
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: 74,614
Karma: 130140792
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 Hitch View Post
At some point in time, at some point in space, you'd run into trouble using those, semantically, or for those who are visually impaired using read-aloud, etc. I mean, if you don't tell a heading that it's a heading, it's "wrong" structurally, at the very least. How would it know what to say to the person to whom it's reading? "Big text paragraph?" Rather than heading?

Ditto muddling paragraphs with divs.

Hitch
I've seen a lot of eBooks that don't quite code the way they should. Most eBooks use <p> for the chapter headers. Most use a <div> to simulate a <blockquote>. Most use a class with <p> where just <p> is appropriate. Some use a <span> for bold and/or italic. So it's no wonder a text-to-speech program cannot get the correct inflections when it doesn't know what it's reading isn't just plain text. Also, using <em> and <strong> (IMHO) is wrong if you just want italic and bold.
JSWolf is offline   Reply With Quote