Unwanted $nbsp;

[Nathanael]

I hope this hasn't been addressed before (a quick search didn't turn up anything).

One of the most common formatting errors in etexts is inappropriate line breaks. When correcting these in Sigil in Book View, I generally add a space at the end of the line, then hit delete. However, Sigil inserts an $nbsp; instead of a normal space, which is not, of course, what I want.

I'm new to Sigil, so I'm sure there's an easy fix, I just don't know what it is.

--Nathanael

EDIT: Forgot to say. I'm using Sigil 0.2.3 on Ubuntu 10.10b x64.

[Jellby]

Have you tried first deleting the newline and then adding the space? It could be (wild guess) that when you add a space at the end of a line Sigil uses a non-breaking space to avoid having it discarded.

[GeoffC]

You might have to use Sigil to create the original, and then manually adjust the code to suit; perhaps?

[Nathanael]

Originally Posted by Jellby

Have you tried first deleting the newline and then adding the space? It could be (wild guess) that when you add a space at the end of a line Sigil uses a non-breaking space to avoid having it discarded.

Hey, good guess, that. At least I thought it was. I was surprised when it didn't work. Deleting the break first then hitting space still gives me an nbsp.

--Nathanael

[Nathanael]

Originally Posted by GeoffC

You might have to use Sigil to create the original, and then manually adjust the code to suit; perhaps?

Except that I'm using it to fix errors in downloaded epubs. Recreating a book from scratch just to fix a stray line break might be a bit overkill. Perhaps.

--Nathanael

[GeoffC]

Originally Posted by Nathanael

Except that I'm using it to fix errors in downloaded epubs. Recreating a book from scratch just to fix a stray line break might be a bit overkill. Perhaps.

--Nathanael

errors in downloaded epubs ... shock horror ! (now when was the last time I saw an error in a mobi ? )

[mrmikel]

I noted this behavior before and it can screw up formatting and nearly all editors do it.

[nyrath]

I think the author of Sigil mentioned that this is due to the Qt software package he used to handle the internal structure. It is a bug in Qt, so he is powerless to fix it.

[Nathanael]

Originally Posted by nyrath

I think the author of Sigil mentioned that this is due to the Qt software package he used to handle the internal structure. It is a bug in Qt, so he is powerless to fix it.

Hmm. Not a big deal. I'll just have to edit in codeview mode I guess. Thanks.

--Nathanael

[Nathanael]

Originally Posted by GeoffC

errors in downloaded epubs ... shock horror ! (now when was the last time I saw an error in a mobi ? )

Yeah, tell me about it. Being the overly fastidious (read: anal retentive) type, however, I just can't bear to read past an error without stopping to fix it. Which means I'm generally reading an epub on my reader, with my laptop open with a second copy of the epub loaded into Sigil. Really slows down the reading and all but negates the whole point of an ereader. But like I said, I just can't stand to let a formatting error go unaddressed.

--Nathanael.

[theducks]

Originally Posted by Nathanael

Yeah, tell me about it. Being the overly fastidious (read: anal retentive) type, however, I just can't bear to read past an error without stopping to fix it. Which means I'm generally reading an epub on my reader, with my laptop open with a second copy of the epub loaded into Sigil. Really slows down the reading and all but negates the whole point of an ereader. But like I said, I just can't stand to let a formatting error go unaddressed.

--Nathanael.

Even if there are not really "errors".

"I can do better than that"
"I want it to look more like my Pbook version"
"Where is the <image>?" Rummage, rummage, Scan.. Ah!