Firmware 3.18.0 discussion

[jackie_w]

Originally Posted by Nick_1964

The whole goal of the extra css (in my case) is overriding values in the current stylesheet.
Now I can't find the current topic back anymore because otherwise i would had placed it there, but I was told that when I don't use the !important "flag" the values in the extra.css is just added to the normal .css of the book and if that contains other values it will follows them.
So if there is already a margin-top of 1em in it, you can only override that with a margin-top=0!important (if that isn't true, I lie because people told me that is) so that is why i use the whole extra css.. I can edit a whole lot with Sigil, but now the wsyiwyg interface seems to give another result when I open it in the book..

See post #297. You definitely do not need !important in your extra_css @page command.

[Nick_1964]

Originally Posted by jackie_w

See post #297. You definitely do not need !important in your extra_css @page command.

Ok, I was told to use it to override things.
Like a lot of Dutch books from one publisher have always something like this in their books:
@page {
margin: 10 10 10 10
}

I can edit them all to remove it ( it is an example because a lot more irritating things are in it,but i was told to use the !important flag, which is a valid command.

So adding @page {
margin: 0 0 0 0 !important
}
Must override it.
If I don't use the !command I can add the above line without the !important but then the first one is leading.
So I can't use normal commands like I said so, if they are already in the css with another value.
All editors I used follow the valid !command only the RMDSK or the ADE don't

I do and am very gratefull of your suggestions and it is not being ignorant from my side but I am almost sure that with early firmwares with another version of the RMDSK did support the !important command but I can be completely wrong.

I even found the original message that I stored where the !important flag was recommended:
https://www.mobileread.com/forums/sho...5&postcount=34
So somewhere i must made it wrong.

[JSWolf]

What I would do is change body in CSS to mine and remove @page from the CSS. It's trivial to do this in the eBook editor. Plus, you can get rid of any excess CSS entries and any bits of the eBooks you don't want like a page full of review quotes or bonus material that's really just a preview for some other book.

[jackie_w]

@Nick and @JSWolf,

As you are both determined that what I have to say is wrong, irrelevant or possibly both, then I'll leave you to your own misconceptions.

[Nick_1964]

Originally Posted by jackie_w

@Nick and @JSWolf,

As you are both determined that what I have to say is wrong, irrelevant or possibly both, then I'll leave you to your own misconceptions.

Ho,who stop, I don't never,ever say you was wrong,I only say that I don't understand, I tried this !important flag with my old Sony (using an older RMDSK) and it worked like a charm.
So I fully say that you are right,I only don't understand why it worked first and don't do now.

The extra CSS was there FOR ME to override settings that are in the .css, the only way to override the settings now, is to delete the ones that are wrong rather then override them with the !important flag.
So for sure I stop using that setting,but then the whole role/need for the extra css is gone (for me)

Adding settings with the extra css to the existing one, while this settings are with other values in that existing .css,doesn't override them if they are more heavvy.
So if there is an bottom-margin=10 setting in the original .css, a setting added (while the other is still there) with a lower value while leaving the original,doesn't work.

So yes, I have to stop using the !important setting like you said because if it is in the .css the current version just (seems to) ignores the whole newly created .css
But then,there is no longer need for me using the whole extra css at all because it can only be used to add missing values in it,it does not overwrite existing ones.

[Jarrett]

Where's 3.19? Feels like it's been a while

[MacEachaidh]

I'm once again seeing the bug where a final single-line para at the end of a chapter, if it appears at or near the bottom of a screen, is pushed over to the next screen, leaving an uncoded gap. This is on my Touch, running 3.18.0, and is counter to my widows/orphans settings.

I had an idea this had been addressed. Was I wrong, or is it back for some reason?

[GeoffR]

Originally Posted by MacEachaidh

I'm once again seeing the bug where a final single-line para at the end of a chapter, if it appears at or near the bottom of a screen, is pushed over to the next screen, leaving an uncoded gap. This is on my Touch, running 3.18.0, and is counter to my widows/orphans settings.

I had an idea this had been addressed. Was I wrong, or is it back for some reason?

I think that is intentional. It has been like that forever.

The ePub built-in stylesheet has the following line:

body { padding-bottom: %1 !important; }

where %1 is the height of one line.

In other words, a blank line is added automatically at the end of every chapter, the effect of which is to (sometimes) push the last line onto the next page.

Some publishers also add their own code to do the same thing, sometimes by adding a blank paragraph at the end of a chapter. In some cases this can combine with the stylesheet to push more than one line to the next page.

(Edit: Those who patch the firmware might not see this, depending on their choice of patches, because some of the patches remove this line from the built-in stylesheet to make room for other things.)

[davidfor]

Originally Posted by GeoffR

I think that is intentional. It has been like that forever.

The ePub built-in stylesheet has the following line:

body { padding-bottom: %1 !important; }

where %1 is the height of one line.

In other words, a blank line is added automatically at the end of every chapter, the effect of which is to (sometimes) push the last line onto the next page.

I don't think it is just this. I've seen this happen when the chapter finished halfway down the page.

Some publishers also add their own code to do the same thing, sometimes by adding a blank paragraph at the end of a chapter. In some cases this can combine with the stylesheet to push more than one line to the next page.

If I edit a book, I always remove those. But, I can't see why an empty paragraph after the last line of text would do this. It could cause an extra empty page to appear, but it shouldn't have an affect on the previous paragraph.

[GeoffR]

Originally Posted by davidfor

If I edit a book, I always remove those. But, I can't see why an empty paragraph after the last line of text would do this. It could cause an extra empty page to appear, but it shouldn't have an affect on the previous paragraph.

You are right, the empty paragraph itself would get pushed to the next page and result in a blank page.

BTW I haven't seen the this happen once in the last year or two since I have been using a patch which removes the padding-bottom line from the built-in stylesheet. (Edit: I also have orphans:1;widows:1; set in every book, and strip any page-template.xpgt files from every book.)

[davidfor]

Originally Posted by GeoffR

You are right, the empty paragraph itself would get pushed to the next page and result in a blank page.

BTW I haven't seen the this happen once in the last year or two since I have been using a patch which removes the padding-bottom line from the built-in stylesheet. (Edit: I also have orphans:1;widows:1; set in every book, and strip any page-template.xpgt files from every book.)

I can see that setting a padding or margin on the last paragraph might have an effect like this. It depends on whether the renderer thinks these have to be included.

And I forgot to say, I don't think something has changed about this. I never saw it much, but it seems to be happening a lot less. At a guess, before it was once every 20-30 chapters. Now it is probably less than once every 50 chapters. Of course, now that I said that, I know what's going to happen on the way home. Maybe I'll read a kepub.

[GeoffR]

Originally Posted by davidfor

And I forgot to say, I don't think something has changed about this. I never saw it much, but it seems to be happening a lot less. At a guess, before it was once every 20-30 chapters. Now it is probably less than once every 50 chapters. Of course, now that I said that, I know what's going to happen on the way home. Maybe I'll read a kepub.

If it is caused by one line of padding, and you read with N lines of text per page and have orphans:1;widows:1, then I think on average it should happen once every N chapters. If you have orphans/widows set higher than 1 then it might happen more often.

Edit: Another factor that could affect it is font-size rescaling that can happen when a book is converted with Calibre. The added line of padding is based on the body font size, but font-size rescaling can increase the body font size and reduce the paragraph font size, so that one line of body padding is larger than one line of text. That would make it happen more often and could also cause more than one line of text to be pushed to the next page.

[MacEachaidh]

In the instance that prompted the question, there's no line or break padding the code, and if the screen break hadn't been forced, the chapter would have ended with four more lines to spare on that particular screen.

It's nothing Calibre's adding, because I don't use it. And I tried setting widows and orphans to 1, and then to 0, and it's still occurring.

It doesn't happen often of late, hence my surprise at seeing it again. I was sure someone had proclaimed it "fixed" a couple of releases ago.

[JSWolf]

Originally Posted by jackie_w

@Nick and @JSWolf,

As you are both determined that what I have to say is wrong, irrelevant or possibly both, then I'll leave you to your own misconceptions.

I never said anything like that. I was just giving another option based on what I do.

[davidfor]

Originally Posted by Jarrett

Where's 3.19? Feels like it's been a while

Checking the first post, we're not quite two months since the last one. I expect to see another one before the end of the year, but, I doubt it will be this month.