![]() |
#1 |
mostly an observer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,518
Karma: 987654
Join Date: Dec 2012
Device: Kindle
|
Why the non-breaking space?
Over on the Kindle forum, there was a post from a would-be publisher who evidently convinced himself/herself that the non-breaking space was the way to insert a chapter break. I pondered this for a while, then realized that the default file that opens up when Sigil is opened reads like this:
<body> <p> </p> </body> I never really thought about that before, since I generally open an html file to start working on a book. Is there a reason why that non-breaking space is there? Is it just a gentle reminder that we are supposed to add some text? |
![]() |
![]() |
![]() |
#2 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,358
Karma: 203720150
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
It's just a placeholder--a blank line. And empty paragraph tags don't always render as blank lines in all readers.
It also serves to provide cursor placement (and a sane starting point) for Book View editing. Try removing the the non-breaking space (leaving just <p></p>) and see what happens when you try to edit in Book View. Also try removing the the entire line (<p> </p>) leaving nothing but the empty body tags and then switch to Book View and start typing. Then check Code View when you're done. The bottom line is that something needs to be there, so why not make it something that properly "seeds" Book View AND will render appropriately if left unaltered? Last edited by DiapDealer; 06-07-2015 at 10:44 AM. |
![]() |
![]() |
![]() |
#3 |
mostly an observer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,518
Karma: 987654
Join Date: Dec 2012
Device: Kindle
|
Ah yes, I remember typing <p> </p> to get a blank line in Kindle editions in 2008.
I will pass this wisdom on to the KDP inquirer. |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Non-breaking space | JSWolf | ePub | 38 | 06-09-2020 09:00 PM |
Non-breaking space (doubled) bug | Camelot | Sigil | 49 | 02-13-2015 04:20 PM |
Troubleshooting Kindle Touch and non-breaking space | utilitasetverita | Amazon Kindle | 4 | 09-05-2014 01:46 PM |
Odd S&R with non breaking space | BobC | Editor | 2 | 07-30-2014 04:19 AM |