Quote:
Originally Posted by mrmikel
No break spaces exist because HTML does not recognize more than one space in a row as valid.
|
No, they are perfectly valid.
Indeed. And most often, when someone types two spaces in succession, it is simply a mistake, and the second one should be ignored. That’s what happens when anyone doesn’t try to be too helpful.
Quote:
|
So no break spaces allow you to enter spaces and make sure they will be shown.
|
That’s what HTML rendering software has been doing. But authors are not supposed to do such things but to use style sheets for spacing.
Quote:
|
Sigil has no way of reading your mind as to whether you REALLY want a space there all the time or not, so it inserts a guaranteed no break space.
|
That is mind-reading, and mosty reading minds wrong.
But it’s not really this feature that annoys me. Sigil seems to introduce no-break spaces around a link, too: when I have “foo bar zap” and I make “bar” a link, in Book View, Sigil makes the spaces around it nonspacing.
Quote:
|
And yes it is annoying, but that is the nature of epubs being based on HTML.
|
No, HTML implies no such thing.