Kobo Patcher

[jackie_w]

But a typical no-technical-knowledge-required calibre conversion will put the page left/right margins in the main css file and the page top/bottom margins in a 2nd linked css file both of which will be ignored if you enable the new CSS patch.

Adding an html @page rule or Adobe xpgt file, as you suggest, requires time, effort and a little html/css know-how. I'm guessing that those who have this know-how and inclination (such as yourself) don't need this CSS patch.

[Nick_1964]

Originally Posted by jackie_w

But a typical no-technical-knowledge-required calibre conversion will put the page left/right margins in the main css file and the page top/bottom margins in a 2nd linked css file both of which will be ignored if you enable the new CSS patch.

Adding an html @page rule or Adobe xpgt file, as you suggest, requires time, effort and a little html/css know-how. I'm guessing that those who have this know-how and inclination (such as yourself) don't need this CSS patch.

Agree, and thats why I should disabled it because with sigil completelij take out the .css is much more easy, but why would I do it, just bulk adapt the epubs with calibre and I am ready for every epub, I still have to do this for my sony so the patch doesn't save me any time.
And with calibre I can make just that little adjustments that keep most of the book intact for all my readers and with the !important rule it is easy to override everything in the .css that I wanted to.

But for a person that just want plain txt and a lot of it, (and own only one reader) on his/her screen it is handy,the greatest feature of this patch is that one less experienced can enable it,while the person that wants to finetune all his books can disable it.

[DNSB]

Originally Posted by Nick_1964

With Calibre you can insert a @page rule in every HTML with margins and stuff like that, as it is not in the .css it can't be ignored.
And you can use an xpgt file in the misc directory of the book with the styles in it, that will also be ignored by the patch.
Only.. what takes more time, to adjust an ebook taking out the wrong lines in the .css file and don't use the patch, or use the patch but build an alternative way in the book so margins are not ignored.
For myself, I won't use that part of the patch, because I have more readers, so I convert all books with calibre, insert Amasis font in it, with my margins, so it works in every reader.

My personal preference is to use Sigil and modify the ebook to use my stylesheet. In that scenario, Metazoa's patch is a non starter. To me, it's using a shotgun as a flyswatter -- the fly ends up dead but the side effects are unacceptable.

Calibre works as a starting point for non-epubs but I really don't like some of what Calibre does during the conversion. On the other hand, my conversions tend to look very boring. Consistent chapter numbering, paragraph style, line and paragraph spacing, all large images given SVG wrappers, etc.

Regards,
David

[Mora]

Originally Posted by DNSB

The space around the edges are the right and left margins. You can set the CSS to reduce those margins to 0 and with the margin slider set to 0, you get pretty much edge to edge text. The top margin is pretty minimal on epubs in 2.10.0 and 3.0.0, on kepubs, it is set quite a bit larger making it rather similar to most dead tree books. At this point in time, there is no method of controlling the header size in kepubs.

Regards,
David

Im not using it for text, but for comics. So i want to use the entire screen.
Right now its looking something like this:

[treadlightly]

Originally Posted by Bonex

I think that happens because if the CSS is completely ignored then defaults apply, and if I'm not mistaken <p> paragraph tags usually have a non-zero margin around them.

IMHO this patch can cause more problems than benefits, because you completely lose all styling and formatting, and it's not some option you can tap when you need it, so I'll pass on this.

Can a line be added to kobo_extra.css to set the <p> margin back to 0?

[Nick_1964]

Originally Posted by DNSB

My personal preference is to use Sigil and modify the ebook to use my stylesheet. In that scenario, Metazoa's patch is a non starter. To me, it's using a shotgun as a flyswatter -- the fly ends up dead but the side effects are unacceptable.

Calibre works as a starting point for non-epubs but I really don't like some of what Calibre does during the conversion. On the other hand, my conversions tend to look very boring. Consistent chapter numbering, paragraph style, line and paragraph spacing, all large images given SVG wrappers, etc.

Regards,
David

Totally agree, but in the latest versions of sigil 0.7.3 and 0.7.4 the right click, copy and paste menu doesn't work anymore.
Not even after totally uninstall previous versions and manually deleting registry.
I think I am busy with tuning Calibre for over one year and now I am so far that if gives a reasonable result together with the special kobo modification plugin.
My problem is to keep it balanced between my Kobo and my girlfriends Sony, when I tweak it more then the result is fine on the Kobo, but terrible on the Sony.
But it is a total personal taste, I don't like text idents, or justify.
For the patch you can do the same with total commander because the epub is just a plain zip.
click on it,delete the css or replace by an universal hand made one, save, ready.

The presence of the patch doesn't matter to me, for some people it can be handy and therefore I am happy with it.
But I don't use it, and since I have already have to edit the epub for the Sony,I take my own preferences with it.
A patch where you can manually set items in to ignore in a .css file would be better,but then I still have to edit the epub for Sony that ignores the !important tag completely.

[dmapr]

Originally Posted by byblo

@dmapr: I've been trying the 'Ignore book TOC navpoints' patch.

Unfortunately, it does not work everytime, and when it does, the TOC is obviously missing from the book, making the patch barely useful, since it breaks the TOC navigation.

I know I'm annoying, but could Metazoa take in consideration again the david's advice :


This is the last feature that I need to be fully happy with my Glo

You're not annoying me Whether or not I'm annoying Metazoa is a different question entirely

So, before I go to him, I'd like to be able to give him some samples that he can work with. It is a bit of a guesswork on his part, since he is trying to reverse engineer things from binary code. Telling him "just make it behave like this" is not good enough since he first needs to find out where in the binary code the behaviour is.

I gave him the samples that DNSB posted in https://www.mobileread.com/forums/sho...&postcount=328, can you check to see if they exhibit the undesired effects? If not, can you post some that do?

[byblo]

Originally Posted by dmapr

I gave him the samples that DNSB posted in https://www.mobileread.com/forums/sho...&postcount=328, can you check to see if they exhibit the undesired effects? If not, can you post some that do?

Yes they seems ok for tests.

BTW, I've been taking a look in the ereader's database to see how it works. It seems a real mess.

The reason the cover is shown after reopening a book that was previously finished is because at finishing the book, the cover path is saved in the database as the current page on the first TOC entry...

For instance, after finishing a book, the main book entry will contain on its ChapterIDBookmarked the path to the very first TOC file (as usual), and on that specified entry, the adobe_location column value will contain the cover file path...

Why is the cover path saved at finishing a book but first TOC entry is used when opening a new book? Only God knows...

Regardless the method, If Metazoa can force to start from page 1 when the ReadStatus is set to 0 (without breaking the TOC and bookmarking features), he is very good at patching ^^;

[GeoffR]

Here are the three patches I use, for firmware 3.0.1 (644485e229) on Touch/Glo/AuraHD devices. Tested on my Glo.

Custom line spacing patch:

Spoiler:

<Patch>
patch_name = `My line spacing values` 
patch_enable = `yes`
# Bypass code-injected values
replace_bytes = 7493AE, 26 F6 AE EA, 00 46 00 46
replace_bytes = 7493FC, 26 F6 86 EA, 00 46 00 46
replace_bytes = 749422, 26 F6 74 EA, 00 46 00 46
replace_bytes = 749458, 26 F6 58 EA, 00 46 00 46
replace_bytes = 7494B4, 26 F6 2A EA, 00 46 00 46
# Values for replace
replace_float = 7494F8, 1.05, 0.8
replace_float = 749500, 1.07, 0.83
replace_float = 749508, 1.1,  0.865
replace_float = 749510, 1.35, 0.905
replace_float = 749518, 1.7,  0.95
replace_float = 749520, 1.8,  1.0
replace_float = 749528, 2.2,  1.05
replace_float = 749530, 2.4,  1.1
replace_float = 749538, 2.6,  1.25
replace_float = 749540, 2.8,  1.5
</Patch>

Custom font sizes patch:

Spoiler:

<Patch>
patch_name = `Custom fonts sizes`
patch_enable = `yes`
# Values for replace
replace_int = 11477E8, 12, 12
replace_int = 11477EC, 14, 16
replace_int = 11477F0, 16, 20
replace_int = 11477F4, 17, 22
replace_int = 11477F8, 18, 24
replace_int = 11477FC, 19, 25
replace_int = 1147800, 20, 26
replace_int = 1147804, 21, 27
replace_int = 1147808, 22, 28
replace_int = 114780C, 24, 29
replace_int = 1147810, 25, 30
replace_int = 1147814, 26, 31
replace_int = 1147818, 28, 32
replace_int = 114781C, 32, 33
replace_int = 1147820, 36, 34
replace_int = 1147824, 40, 35
replace_int = 1147828, 44, 36
replace_int = 114782C, 46, 38
replace_int = 1147830, 48, 40
replace_int = 1147834, 50, 42
replace_int = 1147838, 52, 44
replace_int = 114783C, 54, 48
replace_int = 1147840, 56, 52
replace_int = 1147844, 58, 58
</Patch>

Custom margins patch:

Spoiler:

<Patch>
patch_name = `Custom left & right margins`
patch_enable = `yes`
# Values for replace
replace_int = 13DEE4C, 02, 01
replace_int = 13DEE50, 04, 02
replace_int = 13DEE54, 06, 03
replace_int = 13DEE58, 08, 04
replace_int = 13DEE5C, 10, 05
replace_int = 13DEE60, 12, 06
replace_int = 13DEE64, 14, 07
replace_int = 13DEE68, 16, 08
</Patch>

[DNSB]

The slipstreamed 3.0.0 update has the Readingfooter moved to 13EA170 with the XOR pattern changed to CC. Sheeeshh....

Regards,
David

[ShellShock]

So XOR byte changed again. Why do they bother?

[Quexos]

Say PeterT why did you not add the new patches to your patch list on the very first post of this thread?

I'm just curious

[GeorgK]

Originally Posted by GeoffR

Here are the three patches I use, for firmware 3.0.1 (644485e229) on Touch/Glo/AuraHD devices. Tested on my Glo.

Is there a 'Kobo Patcher' that works w. FW 3.0.1?
I'm very interested in customizing the Kobo footer.

Regards
Georg

[Lyn2012]

I notice that the instruction for installing the patch mention a .exe file, does this mean there is no version for OSX? I have absolutely no access to a PC, (and don't wish to load Windows onto my Mac), but would really like to get rid of the large bottom space on my Aura.

[jackie_w]

Originally Posted by Lyn2012

I notice that the instruction for installing the patch mention a .exe file, does this mean there is no version for OSX? I have absolutely no access to a PC, (and don't wish to load Windows onto my Mac), but would really like to get rid of the large bottom space on my Aura.

I'm not sure whether anyone has tried the Patcher on the new Aura 6".

If you think it's safe to try it and you want to provide your customised config file, kpg.conf file, I could run the Windows part for you, if you like.