Instructions for patching firmware 3.11.0

[GeoffR]

Originally Posted by neil74

# Example for Glo/Aura:
replace_string = DBDC0D, `min-height: 70px;`, `min-height: 40px;`
replace_string = DBDC20, `max-height: 70px;`, `max-height: 40px;`
replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 040;`
replace_string = DBDC58, `font-size: 16px;`, `font-size: 26px;`
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom:13px;`
replace_string = DBDC80, `margin-top: 0px;`, `margin-top:-5px;`

That looks like slantybard's example for the H2O, it will be too big for the Aura. If you want your Aura to look like slantybard's H2O then try something like this:

replace_string = DBDC0D, `min-height: 70px;`, `min-height: 32px;`
replace_string = DBDC20, `max-height: 70px;`, `max-height: 32px;`
replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 105;`
replace_string = DBDC58, `font-size: 16px;`, `font-size: 20px;`
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom:10px;`
replace_string = DBDC80, `margin-top: 0px;`, `margin-top:-4px;`

Or see Jellby's example for the Aura.

But nothing has changed with the footer recently (apart from footerMargin, which does nothing), so if you use exactly the same values you had before the upgrade you should get exactly the same result after.

[Nick_1964]

Originally Posted by PeterT

I thought there WERE instructions for mac users here!

Hope I don't understand you wrong, the instructions are in the patch files and the same for windows or mac,so you can edit,disable or enable them,then run the sh file to compile it.

[dedalos]

Originally Posted by GeoffR

That looks like slantybard's example for the H2O, it will be too big for the Aura. If you want your Aura to look like slantybard's H2O then try something like this:

replace_string = DBDC0D, `min-height: 70px;`, `min-height: 32px;`
replace_string = DBDC20, `max-height: 70px;`, `max-height: 32px;`
replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 105;`
replace_string = DBDC58, `font-size: 16px;`, `font-size: 20px;`
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom:10px;`
replace_string = DBDC80, `margin-top: 0px;`, `margin-top:-4px;`

Or see Jellby's example for the Aura.

But nothing has changed with the footer recently (apart from footerMargin, which does nothing), so if you use exactly the same values you had before the upgrade you should get exactly the same result after.

For aura hd is the same?

[GeoffR]

Originally Posted by dedalos

For aura hd is the same?

There are three different scales: One for AuraHD and H2O, another for Glo and Aura, another for Touch and Mini.

Edit: To be clearer: The AuraHD should use the same examples as the H2O. The Glo should use the same examples as the Aura.

[PeterT]

Originally Posted by Nick_1964

Hope I don't understand you wrong, the instructions are in the patch files and the same for windows or mac,so you can edit,disable or enable them,then run the sh file to compile it.

Niuck; my reply was for Neil74 who had said

Originally Posted by neil74

Also anybody know how to run the patcher on a mac? No joy so far so I am having to use my work PC

I was merely pointing out that the instructions do show how to run the patcher on a mac.

[dedalos]

It's a bit 'of time I'm looking for the best combination of values ​​for Aura hd because I want to prevent white spaces between text and footer without getting great results. Could you help me by recommending a combination that right? Thanks

[GeoffR]

Originally Posted by dedalos

It's a bit 'of time I'm looking for the best combination of values ​​for Aura hd because I want to prevent white spaces between text and footer without getting great results. Could you help me by recommending a combination that right? Thanks

There are some other things that might be causing the white space:

- widows/orphans settings in the book can add one or two blank lines a the bottom of some pages. You can enable the `Fix page breaks bug` patch to get rid of these blank lines.

- The book might have a bottom page margin set, you can use the Modify Epub plugin in Calibre to remove the @page margins.

These values for the custom reading footer patch should give a very small footer on the AuraHD/H2O (it should be similar to Jellby's example for the Aura), if there is any white space with these values then it is caused by something other than the footer:

replace_string = DBDC0D, `min-height: 70px;`, `min-height: 40px;`
replace_string = DBDC20, `max-height: 70px;`, `max-height: 40px;`
replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 170;`
replace_string = DBDC58, `font-size: 16px;`, `font-size: 26px;`
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom: 3px;`
replace_string = DBDC80, `margin-top: 0px;`, `margin-top: 0px;`
#
replace_string = DBDC92, `/*font-family:none;*/`, `font-family: Georgia;`

Edit: One thing you can try as a test is to open the book in full-screen mode. Full-screen mode has no footer at all, so if you can't get the text to reach the bottom of the screen then there must be something else preventing it, either orphans/widows or page margin settings in the book.

[Nick_1964]

Originally Posted by PeterT

Niuck; my reply was for Neil74 who had said



I was merely pointing out that the instructions do show how to run the patcher on a mac.

Oops, sorry

[Nick_1964]

Originally Posted by GeoffR

There are some other things that might be causing the white space:

- widows/orphans settings in the book can add one or two blank lines a the bottom of some pages. You can enable the `Fix page breaks bug` patch to get rid of these blank lines.

- The book might have a bottom page margin set, you can use the Modify Epub plugin in Calibre to remove the @page margins.

I just wish that they (with they I ment ebook makers) take out all hardcoded margins,and let the device do this,all devices are capable of doing this perfect itself,but with every new book I buy, I still have to edit it because they want to give the epub exactly the same look as the book, with the footer patch we try to enable as much as possible space for txt but with a margin left and richt,upper and lower of 10 px it is like you are looking trough a window.

Dear GeoffR,may I ask again a question:
I have enabled the `Fix page breaks bug` patch, but in my Calibre settings for conversion there is still (in extra options .css) a rule with the following line: body {line-height: 1.2; widows: 1; orphans: 1;} because someone recommended it once in the past at conversion.
Can I remove this line when the `Fix page breaks bug` patch is enabled ??

[GeoffR]

Originally Posted by Nick_1964

I have enabled the `Fix page breaks bug` patch, but in my Calibre settings for conversion there is still (in extra options .css) a rule with the following line: body {line-height: 1.2; widows: 1; orphans: 1;} because someone recommended it once in the past at conversion.
Can I remove this line when the `Fix page breaks bug` patch is enabled ??

Yes, with the `Fix page breaks bug` patch enabled the epub reader will ignore any orphans/widows settings in the book, and treat it as if orphans:1; widows:1; was set.

[Nick_1964]

Originally Posted by GeoffR

Yes, with the `Fix page breaks bug` patch enabled the epub reader will ignore any orphans/widows settings in the book, and treat it as if orphans:1; widows:1; was set.

Poor Orphans and Widows are all ignored now thank you for the clear explaining !

[dedalos]

Originally Posted by GeoffR

There are some other things that might be causing the white space:

- widows/orphans settings in the book can add one or two blank lines a the bottom of some pages. You can enable the `Fix page breaks bug` patch to get rid of these blank lines.

- The book might have a bottom page margin set, you can use the Modify Epub plugin in Calibre to remove the @page margins.

These values for the custom reading footer patch should give a very small footer on the AuraHD/H2O (it should be similar to Jellby's example for the Aura), if there is any white space with these values then it is caused by something other than the footer:

replace_string = DBDC0D, `min-height: 70px;`, `min-height: 40px;`
replace_string = DBDC20, `max-height: 70px;`, `max-height: 40px;`
replace_string = DBDC3D, `footerMargin: 105;`, `footerMargin: 170;`
replace_string = DBDC58, `font-size: 16px;`, `font-size: 26px;`
replace_string = DBDC6A, `padding-bottom: 0px;`, `padding-bottom: 3px;`
replace_string = DBDC80, `margin-top: 0px;`, `margin-top: 0px;`
#
replace_string = DBDC92, `/*font-family:none;*/`, `font-family: Georgia;`

Edit: One thing you can try as a test is to open the book in full-screen mode. Full-screen mode has no footer at all, so if you can't get the text to reach the bottom of the screen then there must be something else preventing it, either orphans/widows or page margin settings in the book.

Where I can find the patch fix break page bug? In my libnickel file there isn't

[Jellby]

Originally Posted by Nick_1964

I just wish that they (with they I ment ebook makers) take out all hardcoded margins,and let the device do this,all devices are capable of doing this perfect itself

I wish the bold part was true. But no, I have a Kobo which can change margins but not render in landscape, and a Cybook that can render in landscape but cannot change margins

[Nick_1964]

Originally Posted by dedalos

Where I can find the patch fix break page bug? In my libnickel file there isn't

The patch is devided in 3 parts.
The one u need is in the librmsdk.so.1.0.0.patch file.

Originally Posted by Jellby

I wish the bold part was true. But no, I have a Kobo which can change margins but not render in landscape, and a Cybook that can render in landscape but cannot change margins

And both can't tell the story so you don't have to read it but you know what I mean
Never tried mine in landscape btw..

[dedalos]

I must copy it in libnickel or I activate it where it stay with changing no with yes?