View Single Post
Old 02-16-2011, 03:27 AM   #35
ldolse
Wizard
ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.
 
Posts: 1,337
Karma: 123455
Join Date: Apr 2009
Location: Malaysia
Device: PRS-650, iPhone
Quote:
Originally Posted by JSWolf View Post
But with an eBook, you cannot have asterisks for ambiguity as youdon't know where the section break will land on the screen. So if you want asterisks, it's bets to have them in every section break or just space in every section break. having them where they are in a pBook to make the end or beginning of a page is sloppy slipshod unprofessional work.
Use page-break-before:avoid for either white-spaced scene breaks (defined as a blank paragraph with an nbsp) or asterisks/dingbats. This guarantees that the wherever they fall there will always be at least two lines of text above them, at least on my testing with ADE.

I realize that defining an empty paragraph with an nbsp is sometimes considered bad html coding vs using css margins alone, but I think there is too much of a risk that format shifting software will discard those margins, while blank paragraphs will typically be retained, and can have their own style applied.

Last edited by ldolse; 02-16-2011 at 03:33 AM.
ldolse is offline   Reply With Quote