View Single Post
Old 09-03-2019, 07:34 PM   #73
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 AliceWonder View Post
Wasn't suggesting to use it for the paragraph text, but ePub uses html and both 'pre' and 'code' elements are suppose to render with a monospace font.

[...]

Maybe not very many books need those tags, but they are part of the standard.
Yeah... like JSWolf said, <pre> is broken on many real life ereaders. In many cases, the text scrolls right off the end of the screen (especially with larger font sizes).

And remember:
  • There are very skinny/small devices too (cell phones).
  • Many devices don't even have touch.

Any sort of fancy CSS3 scrollbars don't work.

So many of the other solutions online try to use Javascript to help line breaking (displaying indented arrows, numbering lines, etc.)... can't rely on that in ebooks either.
Tex2002ans is offline   Reply With Quote