Instructions for patching firmware 3.18.0

[Nick_1964]

Lately in dutch books it is common that they add stupid lines to the .css with the page margins.
Like this:
@page { margin: 3.00em 1.00em 0.70em 1.00em; }
Sometimes in the beginning of the .css but also in the middle or end and much more worse, not in the .css but in every html file.
I now add the following line to
I dont understand always the fully syntax of the patches, can I patch it somewhere (3.17.3 and the other on 3.18.0) so it will always be something like this:
@page { margin: 0.00em 0.00em 0.00em 0.00em!important; } ??
I do now put this in the extra css of calibre but with directly downloaded books (mostly epub) that offcourse doesn't work.
If it is already in the patch, sorry but reading line for line does make it all look to each other,can someone point it out for me ??

[John F]

Originally Posted by NiLuJe

@idoit: The ones using Carta screens (H2O, Glo HD) definitely *should*, but for baffling reasons, Kobo (I assume) chose not to. The waveforms are not tailored for it, and the eInk driver might not be up to the job either as-is...

Was a huge disappointment when I got my H2O, to tell you the truth. That this is *still* the case on the Glo HD even more so.

Are we sure that the Glo HD isn't using Regal? I just changed the number pages turns before refresh to 20, and I didn't see any major degrading of the screen after turning many pages?

[scoky]

Originally Posted by GeoffR

When fullScreenReading=true the following is added to the built-in KePub stylesheet......

Hi GeoffR, you have done a great job! I love this patch and it makes kobo full screen reading perfect! Thanks!

[NiLuJe]

@John F: If that's in nickel, what do you have available in the "Refresh the screen every:" combobox? If it goes further than 1-6 pages *without a patch*, then, yeah, that's probably using regal.

(In which case, that's Super(TM) interesting, since we'd be doing it wrong in KOReader).

I seem to remember that this setting is presented completely differently on the Aura, but it's been quite a while since I've had one on hand.

[John F]

Originally Posted by NiLuJe

@John F: If that's in nickel, what do you have available in the "Refresh the screen every:" combobox? If it goes further than 1-6 pages *without a patch*, then, yeah, that's probably using regal.

(In which case, that's Super(TM) interesting, since we'd be doing it wrong in KOReader).

I seem to remember that this setting is presented completely differently on the Aura, but it's been quite a while since I've had one on hand.

I initially tried it without the patch and set it to 100 (oh the humanity).

I'm now using the patch and set a maximum of 20.

I'm using kepubs.

[NiLuJe]

@John F: Right, then, no, probably not. Just the Carta screen being decent on its own .

I vaguely remember asking someone for a strace log to confirm that fact, which is why I was suprised .

[GeoffR]

Originally Posted by Nick_1964

Lately in dutch books it is common that they add stupid lines to the .css with the page margins.
Like this:
@page { margin: 3.00em 1.00em 0.70em 1.00em; }
Sometimes in the beginning of the .css but also in the middle or end and much more worse, not in the .css but in every html file.
I now add the following line to
I dont understand always the fully syntax of the patches, can I patch it somewhere (3.17.3 and the other on 3.18.0) so it will always be something like this:
@page { margin: 0.00em 0.00em 0.00em 0.00em!important; } ??
I do now put this in the extra css of calibre but with directly downloaded books (mostly epub) that offcourse doesn't work.
If it is already in the patch, sorry but reading line for line does make it all look to each other,can someone point it out for me ??

The `ePub fixed/adjustable top/bottom margins` patch can do this. If you uncomment the replace_string line after the first two 'Optional replacement value' comments and set the replacement value to '0\00' then all four @page margins in ePubs will be set to zero. However I'm not sure what happens if the book has an .xpgt file with margins set in that, I always delete any .xpgt files before sideloading using the Modify ePub plugin.

(The KePub reader just ignores @page, so no need to do anything for KePubs.)

Here is the section of the patch for 3.18.0, customised to use fixed top/bottom margins of zero (the left/right margins are set to zero by default):

#
# Optional replacement value: Uncomment for a FIXED TOP MARGIN size in px,
# default 25px. Replacement value is margin size, two digits separated by \0
# (Leave commented out for an adjustable top margin.)
replace_string = B4FDDC, `%\01`, `0\00`
#
# Optional replacement value: Uncomment for a FIXED BOTTOM MARGIN size in px,
# default 00px. Replacement value is margin size, two digits separated by \0
# (Leave commented out for an adjustable bottom margin.)
replace_string = B4FDF0, `%\01`, `0\00`

Edit: You can also use the Modify ePub plugin to remove the @page and body margins, it does a good job with the @page margins, but doesn't always remove all body margins in books that have had their CSS structure flattened by a Calibre conversion.

[Nick_1964]

Originally Posted by GeoffR

The `ePub fixed/adjustable top/bottom margins` patch can do this.

[...]

Edit: You can also use the Modify ePub plugin to remove the @page and body margins, it does a good job with the @page margins, but doesn't always remove all body margins in books that have had their CSS structure flattened by a Calibre conversion.

Thanks for the example, now I know where to look for it..
in 3.17.3 I found the last part of the patch a bit strange.
Because I want to use fixed margins, I commented out the replace value of the adjustable. is that correct ??

#
# Replacement value: Sets the value of the ADJUSTABLE top/bottom margin (if any)
# to a multiple of readingLeftMargin, in pixels. Suggested values are:
# Normal reading mode: 5px (Touch/Mini), 6px (Glo/Aura), 8px (AuraHD/H2O/GloHD)
# Full-screen mode: 6px (Touch/Mini), 7px (Glo/Aura), 10px (AuraHD/H2O/GloHD)
#replace_int = 45985E, 1, 6


I found the patch for kepubs to put off hyphenation.
Is there anything to prevent to do the same with epubs ??
Hyphenation on epubs in Dutch keep going wrong..
I tried the following to add to an extra css
p {
hyphens: none !important;
}
Only to see that another one does it in the div tags...

[GeoffR]

Originally Posted by Nick_1964

Thanks for the example, now I know where to look for it..
in 3.17.3 I found the last part of the patch a bit strange.
Because I want to use fixed margins, I commented out the replace value of the adjustable. is that correct ??

#
# Replacement value: Sets the value of the ADJUSTABLE top/bottom margin (if any)
# to a multiple of readingLeftMargin, in pixels. Suggested values are:
# Normal reading mode: 5px (Touch/Mini), 6px (Glo/Aura), 8px (AuraHD/H2O/GloHD)
# Full-screen mode: 6px (Touch/Mini), 7px (Glo/Aura), 10px (AuraHD/H2O/GloHD)
#replace_int = 45985E, 1, 6

It doesn't matter, if you are not using adjustable top or bottom margin then that line will have no effect either way.

I found the patch for kepubs to put off hyphenation.
Is there anything to prevent to do the same with epubs ??
Hyphenation on epubs in Dutch keep going wrong..
I tried the following to add to an extra css
p {
hyphens: none !important;
}
Only to see that another one does it in the div tags...

No, KePub and ePub hyphenaion are completely different. If you want to turn off hyphenation altogether then adding something like this to the book's stylesheet will work for most books:

body,div,p {
 hyphens: none !important;
 adobe-hyphenate: none !important;
 -webkit-hyphens: none !important;
}

but it is always possible for the publisher to override the hyphenation settings in ePubs if they choose to, because the way !important works in ePubs is different than in KePubs. The only way to be be 100% sure is to strip all of the publisher's hyphenation styles from the ePub as well.

[Nick_1964]

Originally Posted by GeoffR

No, KePub and ePub hyphenaion are completely different. If you want to turn off hyphenation altogether then adding something like this to the book's stylesheet will work for most books:

body,div,p {
 hyphens: none !important;
 adobe-hyphenate: none !important;
 -webkit-hyphens: none !important;
}

but it is always possible for the publisher to override the hyphenation settings in ePubs if they choose to, because the way !important works in ePubs is different than in KePubs. The only way to be be 100% sure is to strip all of the publisher's hyphenation styles from the ePub as well.

Thank you, I do this already but like you said... they can override it.
Dutch hyphenation is still wrong a lot,specially when it try's to put the - behind 3 letters... sometimes like the name Brooke will be hyphenated as Bro-oke.... it is clear to me that not much publishers try their own epubs on an e-reader..every single book i have to edit..
Thank you for putting me on the road again.

[JSWolf]

Originally Posted by Nick_1964

Thank you, I do this already but like you said... they can override it.
Dutch hyphenation is still wrong a lot,specially when it try's to put the - behind 3 letters... sometimes like the name Brooke will be hyphenated as Bro-oke.... it is clear to me that not much publishers try their own epubs on an e-reader..every single book i have to edit..
Thank you for putting me on the road again.

When you see an incorrect Dutch hyphen, have a look at the dictionary and see if you can spot where the error is. It's quite possible;e the errors are coming from the hyphenation dictionary.

[Nick_1964]

Originally Posted by JSWolf

When you see an incorrect Dutch hyphen, have a look at the dictionary and see if you can spot where the error is. It's quite possible;e the errors are coming from the hyphenation dictionary.

I think it is, it happens on a lot of words that are cut off after 3 letters but I think the bug that Geoffr found a while ago is counting to..it is a bit difficult to see for me why the words are not well hyphenated... I have to dive deeper in it, or just disable it what seems to be the best..

[Percivale]

Dear owners of H2O

Can you please sugguest the optimum values for the patch in order to have as little footer and header as possible?

I am a rookie in this field and I am a liitle lost. On the other hand I would not like to experiment knowing that there is a slight risk of blocking my reader.

I will be very grateful for any help.

[Nick_1964]

Originally Posted by Percivale

Dear owners of H2O

Can you please sugguest the optimum values for the patch in order to have as little footer and header as possible?

I am a rookie in this field and I am a liitle lost. On the other hand I would not like to experiment knowing that there is a slight risk of blocking my reader.

I will be very grateful for any help.

By working with the header or footer patch you will not block your reader.. and publishers can override this, if they set the pagemargin at 1 em, the page end about one cm above your footer limit.
Here you have mine, the value for Glo HD and H@0 are almost the same.

<Patch>
patch_name = `Custom reading footer style`
patch_enable = `yes`
# Multi-version patch: 3.15.0 - 3.18.0+
#
# 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.
#
# 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\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: 035px;`
replace_string = 00EE, `max-height: 120px;`, `max-height: 035px;`
#
#
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: 33px;`
#
# 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: Avenir;}
</Patch>

[Percivale]

@Nick_1964

Thank You very much

So, If I understand it correctly, after patching the reader I can still adjust the values in some config file which will be in the reader???