italic at end of line causes next line to start with a space

[ebookreadr]

I have been having this problem for a very long time and have not been able to resolve it.

When an italicized word is at the end of a line and there is a space after it sometimes the next line will start with a space. This happens when the text is justified. This happens regardless of whether you use <span class"... or <i>. Sometime the justification sees the space correctly and sometime it treats it like a separate word.

I am using a 2nd gen nook Simple Touch. If I convert the justification to the left it is ok. I use Sigil to make changes/corrections to my ebooks. I use the convert feature of Calibre to justify the lines. This makes it easier for me to read. I read by shape as well as spelling and when the format/spacing is different it breaks my reading flow.

This is not a major thing, but has been bugging me for years and I have not found a way to fix this.

Any ideas would be greatly appreciated.

[Notjohn]

I use Sigil to make changes/corrections to my ebooks. I use the convert feature of Calibre to justify the lines.

Sigil exists to build e-books. Calibre exists to manage digital libraries. I think you would do better to use each for what it's meant to do. Justification is a menu option in Sigil, but better would be to include a style sheet in which each paragraph style contains the instruction; this is mine:

p {
margin-top:0.0em;
margin-bottom:0.0em;
text-indent:1.5em;
text-align:justify;
}

I have never seen the spacing problem you mention, but then I don't ordinarily read on a Nook.

[DiapDealer]

Sounds like a Nook rendering issue to me. I've never noticed the the extra spacing mentioned in any of my Sigil-created epubs.

Renderer-specific justification overrides are not likely going to be something Sigil has the ability to affect.

[theducks]

Never saw that on my Astak. (old RMSDK)

[ebookreadr]

Originally Posted by Notjohn

Sigil exists to build e-books. Calibre exists to manage digital libraries. I think you would do better to use each for what it's meant to do. Justification is a menu option in Sigil, but better would be to include a style sheet in which each paragraph style contains the instruction; this is mine:

p {
margin-top:0.0em;
margin-bottom:0.0em;
text-indent:1.5em;
text-align:justify;
}

I have never seen the spacing problem you mention, but then I don't ordinarily read on a Nook.

Thanks for you input. I use the Calibre convert to quickly remove the spaces between lines and paragraphs, change the left/right margins to 3pts, and change the indent to 1em. I do this because sometimes the book's original formatting is off - like having a double line space between paragraphs or large left/right margins. I don't know if these are caused by the nook or not. Often they look OK in Sigil or the Calibre reader, but not on the nook. But a quick convert to make them more readable on the nook.

PS - I also have used Sigil to fix those things, but usually when I am fixing typos or remove extra coding that the nook can't read correctly such as some special characters etc.

My general feeling is that this may be a problem with the nook, but I can't afford a new reader at this time and it has been very reliable. So I'll live with it. Besides, if I hadn't tried fixing different things for the nook, I would not have learned how to use Sigil (or other editing programs etc)

Thanks for all the comments..

[JSWolf]

Originally Posted by Notjohn

p {
margin-top:0.0em;
margin-bottom:0.0em;
text-indent:1.5em;
text-align:justify;
}

That's not good code at all. You do not need 0.0em. Just use 0

body {
widows: 1;
orphans: 1;
margin-top: 0;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;
text-align: justify;
}
p {
margin-top: 0;
margin-bottom: 0;
text-indent: 1.2em
}

Now that's better code.

As for the nook, B&N has done some odd things with RMDSK that causes some oddities.

[Turtle91]

That's not good code at all. You do not need to break out all the margins. Just use:

body {
widows: 1;
orphans: 1;
margin: 0;
}
p {
margin: 0;
text-align: left;
text-indent: 1.2em
}

Now that's better code.

[RbnJrg]

Originally Posted by Turtle91

That's not good code at all. You do not need to break out all the margins. Just use:

body {
widows: 1;
orphans: 1;
margin: 0;
}
p {
margin: 0;
text-align: left;
text-indent: 1.2em
}

Now that's better code.

I think JSWolf used

margin-top: 0;
margin-bottom: 0;
margin-left: 0;
margin-right: 0;

instead of

margin: 0;

because Nook doesn't support the shorthand form.

Regards
Rubén

[Turtle91]

lolz

I was giving Jon grief because he's very predictable on certain things... thus the

[jbacelar]

Originally Posted by Notjohn

Sigil exists to build e-books. Calibre exists to manage digital libraries.

And for to build e-books.

Why do not you take a look at the Calibre editor's manual? (https://manual.calibre-ebook.com/edit.html) and so you can speak with real knowledge of the subject.

[dwig]

Originally Posted by jbacelar

And for to build e-books.

Why do not you take a look at the Calibre editor's manual? (https://manual.calibre-ebook.com/edit.html) and so you can speak with real knowledge of the subject.

True. It is now somewhat of a "Swiss Army Knife" tool.

At its core, calibre is a library manager and format converter. It has grown over the years adding satellite apps for ebook reading and for true ebook editing. The latter being roughly the equivalent of Sigil. Sigil remains a rather "single minded" but powerful tool; its purpose being solely ebook creation & editing.

[JSWolf]

This thread does not belong in the Sigil forum as it has nothing to do with Sigil.

[DiapDealer]

Originally Posted by JSWolf

This thread does not belong in the Sigil forum as it has nothing to do with Sigil.

That's not your decision to make. You sent your report, I read it and decided against moving it, now let it go.

[BetterRed]

Kovid's decision to develop the calibre editor was motivated, in part at least, by the fact that Sigil didn't have anyone maintaining it - i.e. it had been 'abandoned'.

I also recall he produced the first version remarkably quickly. Presumably because: he could leverage what calibre already had; he enjoyed doing it, or so he said at the time; there were no legacy issues (i.e. a current user base); he could avoid Sigil's legacy issues - e.g. WYSIWYG Book Editor; and he could add some features - AZW3 support, multilingual spell checking, user functions in S&R, Live CSS tool etc, checkpoint/recovery.

IIRC the initial release of the calibre editor, and Kevin H announcing he would take Sigil under his wing happened within a few weeks of one another.

I've often wondered: if Sigil had been rescued sooner, would Kovid have developed the calibre editor when he did.

Nothing above should be read as me being critical of user-none, Kevin H or anyone else.

BR

[DiapDealer]

Originally Posted by BetterRed

I also recall he produced the first version remarkably quickly.

Amazingly quickly. Scary quick, actually.