Instructions for patching firmware 3.19.5613

[lkstrummer]

Thanks for the quick reply. I can't create a new patch right now, but I'll edit this later when I test your suggestion. Interestingly, I uncommented all values for all devices in 3.17.3 and the output file was created without any problems. So it looked like:

find_base_address = `ReadingFooter {\n\tmin-height: 70px;`
#
# Replacement footer height values: Touch/Mini
replace_string = 0011, `min-height: 70px;`, `min-height: 32px;`
replace_string = 0024, `max-height: 70px;`, `max-height: 32px;`
# Replacement footer height values: Glo/Aura
replace_string = 0085, `min-height: 82px;`, `min-height: 40px;`
replace_string = 0098, `max-height: 82px;`, `max-height: 40px;`
# Replacement footer height values: AuraHD/H2O/GloHD
replace_string = 00DA, `min-height: 120px;`, `min-height: 036px;`
replace_string = 00EE, `max-height: 120px;`, `max-height: 036px;`
#
#


EDIT: Thanks, Geoff. I produced the output file without error and the footer height now conforms to my tastes. A few issues other I've noticed which might be addressed by existing patches:

-in epubs text weight in advanced fonts doesn't have effect on the Publisher Default which I favor
-epub line justification also seems to have no effects across several epubs with and w/o Publisher Default font

[outlandos]

Please let me use this post to find the difference:

<Patch>
patch_name = `Custom reading footer style`
patch_enable = `yes`
# Multi-version patch: 3.19.5613 - 3.19.5613+
#
# This patch customises the following properties of the reading footer:
#
#  * Footer height (the amount of the screen reserved for the footer.)
#  * Caption font size (Caption = page number or other progress indicator)
#  * Caption top margin, which changes its vertical position within the footer.
#  * Caption font family.
#
# When editing the replacement values below, BE CAREFUL NOT TO CHANGE THE LENGTH
# OF THE REPLACEMENT STRING! If a replacement string is too long you will get
# an error when making the patch, but if one is too short then there will be no
# error, but strange things will happen to the reading footer.
#
find_base_address = `ReadingFooter {\n\tqproperty-footerMargin: 105;\n}\n\n`
replace_string = 0000, `ReadingFooter {\n\tqproperty-footerMargin: 105;\n}\n\nReadingFooter[qApp_deviceIsDragon="true"] {\n\tqproperty-footerMargin: 170;\n}`, `ReadingFooter { qproperty-footerMargin: 105; min-height: 70px; max-height: 70px; }`
#
# Example replacement footer height values: Touch/Mini
#replace_string = 001A, `footerMargin: 105;`, `footerMargin: 105;`
#replace_string = 002D, `min-height: 70px;`, `min-height: 32px;`
#replace_string = 003F, `max-height: 70px;`, `max-height: 32px;`
# Example replacement footer height values: Glo/Aura
replace_string = 001A, `footerMargin: 105;`, `footerMargin: 105;`
replace_string = 002D, `min-height: 70px;`, `min-height: 40px;`
replace_string = 003F, `max-height: 70px;`, `max-height: 40px;`
# Example replacement footer height values: AuraHD/H2O/GloHD
#replace_string = 001A, `footerMargin: 105;`, `footerMargin: 170;`
#replace_string = 002D, `min-height: 70px;`, `min-height: 52px;`
#replace_string = 003F, `max-height: 70px;`, `max-height: 52px;`
#
#
find_base_address = `#caption {\n\tfont-size: 16px;`
Replace_string = 0000, `#caption {\n\tfont-size: 16px;\n}\n\n#caption[qApp_deviceIsPhoenix="true"] {\n\tfont-size: 20px;\n}\n\n#caption[qApp_deviceIsDragon="true"] {\n\tfont-size: 26px;\n}\n\n#caption[qApp_deviceIsAlyssum="true"] {\n\tfont-size: 30px;\n}\n\n#caption[qApp_localeName="ja_JP"] {\n\tfont-family: Sans-SerifJP;\n}`, `#caption {font-size: 16px;margin-top: 00px;}\n#caption[qApp_deviceIsPhoenix="true"] {font-size: 20px;}\n#caption[qApp_deviceIsDragon="true"] {font-size: 26px;}\n#caption[qApp_deviceIsAlyssum="true"] {font-size: 30px;}\n#caption[qApp_localeName="ja_JP"] {font-family: Sans-SerifJP;}`
#
# Replacement caption font size value for Touch/Mini:
replace_string = 000A, `font-size: 16px;`, `font-size: 16px;`
# Replacement caption font size value for Glo/Aura:
replace_string = 0054, `font-size: 20px;`, `font-size: 20px;`
# Replacement caption font size value for AuraHD/H2O:
replace_string = 008C, `font-size: 26px;`, `font-size: 26px;`
# Replacement caption font size value for GloHD:
replace_string = 00C5, `font-size: 30px;`, `font-size: 30px;`
#
# Replacement caption top margin value for all devices:
# (A negative top margin moves the caption text upwards,
# further from the bezel and closer to the page content.)
#replace_string = 001A, `margin-top: 00px;`, `margin-top:-10px;`
#
# Uncomment to use a fixed replacement caption font family, for all devices:
# (You can change Avenir to another font name of your choice, but Avenir or
# Georgia are recommended because other fonts may not be loaded when the book
# is first opened and so might cause problems. Unlike other strings it is OK
# if this replacement string is a bit longer or shorter than the original.)
replace_string = 00D7, `#caption[qApp_localeName="ja_JP"] {font-family: Sans-SerifJP;}`, `#caption {font-family: Georgia;}
</Patch>

<Patch>
patch_name = `Custom reading footer style`
patch_enable = `yes`
# Multi-version patch: 3.19.5613 - 3.19.5613+
#
# This patch customises the following properties of the reading footer:
#
#  * Footer height (the amount of the screen reserved for the footer.)
#  * Caption font size (Caption = page number or other progress indicator)
#  * Caption top margin, which changes its vertical position within the footer.
#  * Caption font family.
#
# When editing the replacement values below, BE CAREFUL NOT TO CHANGE THE LENGTH
# OF THE REPLACEMENT STRING! If a replacement string is too long you will get
# an error when making the patch, but if one is too short then there will be no
# error, but strange things will happen to the reading footer.
#
find_base_address = `ReadingFooter {\n\tqproperty-footerMargin: 105;\n}\n\n`
replace_string = 0000, `ReadingFooter {\n\tqproperty-footerMargin: 105;\n}\n\nReadingFooter[qApp_deviceIsDragon="true"] {\n\tqproperty-footerMargin: 170;\n}`, `ReadingFooter { qproperty-footerMargin: 105; min-height: 70px; max-height: 70px; }`
#
# Example replacement footer height values: Touch/Mini
#replace_string = 001A, `footerMargin: 105;`, `footerMargin: 105;`
#replace_string = 002D, `min-height: 70px;`, `min-height: 32px;`
#replace_string = 003F, `max-height: 70px;`, `max-height: 32px;`
# Example replacement footer height values: Glo/Aura
replace_string = 001A, `footerMargin: 105;`, `footerMargin: 105;`
replace_string = 002D, `min-height: 70px;`, `min-height: 40px;`
replace_string = 003F, `max-height: 70px;`, `max-height: 40px;`
# Example replacement footer height values: AuraHD/H2O/GloHD
#replace_string = 001A, `footerMargin: 105;`, `footerMargin: 170;`
#replace_string = 002D, `min-height: 70px;`, `min-height: 52px;`
#replace_string = 003F, `max-height: 70px;`, `max-height: 52px;`
#
#
find_base_address = `#caption {\n\tfont-size: 16px;`
Replace_string = 0000, `#caption {\n\tfont-size: 16px;\n}\n\n#caption[qApp_deviceIsPhoenix="true"] {\n\tfont-size: 20px;\n}\n\n#caption[qApp_deviceIsDragon="true"] {\n\tfont-size: 26px;\n}\n\n#caption[qApp_deviceIsAlyssum="true"] {\n\tfont-size: 30px;\n}\n\n#caption[qApp_localeName="ja_JP"] {\n\tfont-family: Sans-SerifJP;\n}`, `#caption {font-size: 16px;margin-top: 00px;}\n#caption[qApp_deviceIsPhoenix="true"] {font-size: 20px;}\n#caption[qApp_deviceIsDragon="true"] {font-size: 26px;}\n#caption[qApp_deviceIsAlyssum="true"] {font-size: 30px;}\n#caption[qApp_localeName="ja_JP"] {font-family: Sans-SerifJP;}`
#
# Replacement caption font size value for Touch/Mini:
replace_string = 000A, `font-size: 16px;`, `font-size: 16px;`
# Replacement caption font size value for Glo/Aura:
replace_string = 0054, `font-size: 20px;`, `font-size: 20px;`
# Replacement caption font size value for AuraHD/H2O:
replace_string = 008C, `font-size: 26px;`, `font-size: 26px;`
# Replacement caption font size value for GloHD:
replace_string = 00C5, `font-size: 30px;`, `font-size: 30px;`
#
# Replacement caption top margin value for all devices:
# (A negative top margin moves the caption text upwards,
# further from the bezel and closer to the page content.)
replace_string = 001A, `margin-top: 00px;`, `margin-top:-10px;`
#
# Uncomment to use a fixed replacement caption font family, for all devices:
# (You can change Avenir to another font name of your choice, but Avenir or
# Georgia are recommended because other fonts may not be loaded when the book
# is first opened and so might cause problems. Unlike other strings it is OK
# if this replacement string is a bit longer or shorter than the original.)
#replace_string = 00D7, `#caption[qApp_localeName="ja_JP"] {font-family: Sans-SerifJP;}`, `#caption {font-family: Georgia;}
</Patch>

I still can't find what it, what did you (just now) change exactly?

[tshering]

#replace_string = 001A, `margin-top: 00px;`, `margin-top:-10px;`
#
# Uncomment to use a fixed replacement caption font family, for all devices:
# (You can change Avenir to another font name of your choice, but Avenir or
# Georgia are recommended because other fonts may not be loaded when the book
# is first opened and so might cause problems. Unlike other strings it is OK
# if this replacement string is a bit longer or shorter than the original.)
replace_string = 00D7, `#caption[qApp_localeName="ja_JP"] {font-family: Sans-SerifJP;}`, `#caption {font-family: Georgia;}

replace_string = 001A, `margin-top: 00px;`, `margin-top:-10px;`
#
# Uncomment to use a fixed replacement caption font family, for all devices:
# (You can change Avenir to another font name of your choice, but Avenir or
# Georgia are recommended because other fonts may not be loaded when the book
# is first opened and so might cause problems. Unlike other strings it is OK
# if this replacement string is a bit longer or shorter than the original.)
#replace_string = 00D7, `#caption[qApp_localeName="ja_JP"] {font-family: Sans-SerifJP;}`, `#caption {font-family: Georgia;}

[DNSB]

Originally Posted by lkstrummer

Thanks for the quick reply. I can't create a new patch right now, but I'll edit this later when I test your suggestion. Interestingly, I uncommented all values for all devices in 3.17.3 and the output file was created without any problems. So it looked like:

find_base_address = `ReadingFooter {\n\tmin-height: 70px;`
#
# Replacement footer height values: Touch/Mini
replace_string = 0011, `min-height: 70px;`, `min-height: 32px;`
replace_string = 0024, `max-height: 70px;`, `max-height: 32px;`
# Replacement footer height values: Glo/Aura
replace_string = 0085, `min-height: 82px;`, `min-height: 40px;`
replace_string = 0098, `max-height: 82px;`, `max-height: 40px;`
# Replacement footer height values: AuraHD/H2O/GloHD
replace_string = 00DA, `min-height: 120px;`, `min-height: 036px;`
replace_string = 00EE, `max-height: 120px;`, `max-height: 036px;`
#
#

Given the changes are made at different addresses, I can't see an issue from doing so. OTOH, making unnecessary changes is generally something to be avoided.

[lkstrummer]

You're right. Dumb mistake on my part to not notice that the addresses were the same in this firmware. I had taken it as granted that the different device sets were at different addresses in previous firmwares

[Nick_1964]

/edit overlooked something,please ignore.

[Nick_1964]

Originally Posted by GeoffR

I think the only way would be to completely remove them from the device, but the problem is that they are used by the UI in some places so I don't know if it is a good idea to remove them.

I haven't seen anyone else report a problem with the new fonts though, and it is easy enough for me to avoid the problem just by not using them. (Edit: I see now a few others with Touch/Glo are reporting problems with the Kobo Tsukushi Mincho font.)

This was about the new introduced font problem.
I tried it at my wifes unpatched Glo and I see the same behave..the problem is that she likes it to play with the fonts, avoiding pressing on it is offcourse the most simple,but I discovered twice that when you pick up a font near it and place your finger (s) wrong you still select it.
I don't know if it is difficult to patch it this way that it is simple not showing up on the drop down list (so you can't select it) and/or how long Kobo will send this update or replaces it by a new fixed one, so your precious time would be "spoiled" but I am afraid that we soon get the problem again if Kobo chooses to change it again... Maybe extract the old fonts from 3.17.3 is possible and just simple rename them to the new ones,or only the faulty one, and replace the new ones by the old ones that are renamed solves it ?? (I am not a programmer so excuse me if I put out rubbisch now.. )

[dr. ego]

For some reason i'm not able to produce a koboroot.tgz file. All i get in the target folder is a map called usr. What could i be doing wrong? Haven't had a problem like this with producing a patch in the past.

[GeoffR]

Originally Posted by lkstrummer

-in epubs text weight in advanced fonts doesn't have effect on the Publisher Default which I favor

I don't think there is anything that can be done about that, because "Publisher Default" is not a font. The `Freedom to advanced fonts control` enables the advanced menu button next to Publisher Default, but that is not intentional, it is just that I don't know any way to prevent it.

Edit: Note that unless the publisher has embedded a font in the book, the default will be Georgia and you can just switch to Georgia from the font menu and change the weight/sharpness from there.

-epub line justification also seems to have no effects across several epubs with and w/o Publisher Default font

There is nothing that can be done about that by patching either, it is the way the CSS cascading works in the ePub reader that the publisher always has the last say. The publisher can choose to use the default justification or to force their own choice to be used. If the publisher has chosen to force a particular justification then the only way to fix it is to edit the book and change or remove the appropriate text-align styles.

Edit: Actually I could make a patch that would force the justification for the whole book, but it would be a nuclear option and would force everything to be justified the same way (left or full justification) including images, headings, etc. and you wouldn't be able to turn it off except by removing the patch. I don't know if anyone would be interested in using that?

The KePub reader is different, it can override any publisher style, but that can be just as much of a problem because it overrides styles that it shouldn't such as centred headings etc. With KePubs too, for some things the only way to get a perfect result is to edit the book and fix the various publisher mistakes.

[GeoffR]

Originally Posted by dr. ego

For some reason i'm not able to produce a koboroot.tgz file. All i get in the target folder is a map called usr. What could i be doing wrong? Haven't had a problem like this with producing a patch in the past.

Can you post the output from when you run 3.19.5613.bat? (or ./3.19.5613.sh if you are using Linux/Mac?)

[rogerinnyc]

GeoffR, thank you as always for your work in making my H2O better than ever!

I think I remember reading previously that it's not possible -- and I didn't see it in your patch-- but for Kepubs, is there any way to change the overall size of the top margin (as opposed to where between the text and the bezel the header is located)? I like having both the headers and footers, but the overall top margin size remains a touch too large for my liking.

[GeoffR]

Originally Posted by rogerinnyc

I think I remember reading previously that it's not possible -- and I didn't see it in your patch-- but for Kepubs, is there any way to change the overall size of the top margin (as opposed to where between the text and the bezel the header is located)? I like having both the headers and footers, but the overall top margin size remains a touch too large for my liking.

No sorry, there is no patch that can change the size of the KePub header. The only options are to use the showPageHeader=false Reading setting, which removes the header text but only slightly reduces the space it occupied, or to use the FullScreenReading=true feature setting to enable full-screen mode.

Edit: And it has just been noted that the showPageHeader=false Reading setting no longer works in this firmware.

[JSWolf]

Geoff, can you make the patch in this thread for all Kobo models please?

https://www.mobileread.com/forums/sho...d.php?t=262748

[GeoffR]

Originally Posted by JSWolf

Geoff, can you make the patch in this thread for all Kobo models please?

https://www.mobileread.com/forums/sho...d.php?t=262748

It was already posted in post #9, I've made a link to it from post #2 of this thread. I think someone just needs to test it on the other devices, and let us know if it works okay.

[oren64]

Originally Posted by JSWolf

Geoff, can you make the patch in this thread for all Kobo models please?

https://www.mobileread.com/forums/sho...d.php?t=262748

I also made multi-version and post it in Index to the Metazoa here.

GeoffR can you add my patch 'Dictionary frame size', to post #2.