View Single Post
Old 12-23-2023, 02:18 PM   #9
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,881
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by nabsltd View Post
Note that if converting to a Kindle format after finishing with edits, your "sectionbreak" paragraph will not be displayed at all, since Kindle properly trims all white space from the beginning and end of lines, and it treats a non-breaking space as if it is normal white space. I'm pretty sure that the spec doesn't prevent this, as a non-breaking space should be treated as white space, but just not a possible line break choice. But, most other renderers treat a non-breaking space as a special character that just happens to be an empty glyph.
For Kindle's, I have a pair of div's that surround the sectionbreak and seems to work quite well for azw3/KFX. For epub's I prefer the simpler choice.
DNSB is offline   Reply With Quote