View Single Post
Old 11-12-2023, 11:47 AM   #66
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: 80,105
Karma: 148951733
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
I have a client with a non-fiction book right now--no charts, tables, etc. (the sort of stuff that leads to using block-style, typically, for layout reasons) and he's insisting on using both--first-line indent AND line-between. I'm screaming inside, where you can't see it.

ALSO--you don't use non-breaking spaces or that nonsense for BLANK LINES. Utter bollox. Use CSS or don't do it at all. You have no way of knowing what renderers will do on various devices. Assuming that nbsp will work is..folly.

Hitch
I've seen <p>&nbsp</p> as a paragraph space too many times. The good thing about it is that it's easy to search/replace out. The bad thing is it's bad code and whoever did it should be made to create stone tablets of that book. Same thing goes for anyone using Kindle Create or Vellum.
JSWolf is offline   Reply With Quote