08-17-2013, 06:50 AM | #31 |
Ignorant of many things
Posts: 63
Karma: 9304
Join Date: Feb 2011
Device: Kobo Libra 2
|
I faced the same difficulties as you, kslaght. I assumed (maybe mistankingly) that the first item was to disable the customization of the footer (user's customization) and retain kobo's (firmware original's).
Last edited by henriquemaia; 08-17-2013 at 06:56 AM. |
08-17-2013, 07:24 AM | #32 |
JimInRussell
Posts: 355
Karma: 143302
Join Date: Nov 2010
Location: Russell Ontario Canada
Device: kobo Aura One, Forma, Elipsa, Sage
|
@kslaght,
I find even treadlightly's file hard to read as that one line goes on forever. Why not just change all of them to use 60 60 10 for tmin hight, tmax hight and footerMargin and see if it works for you. I have an Aura and changed the 5 5 0 in the original config file to 60 60 10 as was suggested in another post and that worked for me, I didn't change the tfont-size value in the config file. Edit: to get the full benefit I also include " p, body{ widows: 0; orphans: 0; } " as extra CSS in common options preferences section in calibre for my epubs. Last edited by jiminrussell; 08-17-2013 at 07:27 AM. |
08-17-2013, 08:53 AM | #33 |
Wizard
Posts: 1,370
Karma: 6957792
Join Date: Nov 2010
Location: Ottawa, ON
Device: Kobo H2O
|
I don't have an Aura, but if the 5 5 0 values are what changed the display for you, then that makes sense. I will change the colours in my post.
|
08-17-2013, 01:05 PM | #34 |
Junior Member
Posts: 3
Karma: 10
Join Date: Aug 2013
Device: Kobo Glo
|
jiminrussell:
Thanks for the suggestion, I hadn't considered that I might still be changing the wrong set of values after all of that double and triple checking. As for the orphans and widows, I had meant to mention that I had tried that as well. I saw the changes from that, but of course it didn't fix the footer problems. henriquemaia: I'm afraid I don't understand what you did. Did you end up fixing it? Thanks Keith |
08-17-2013, 02:09 PM | #35 | |
Ignorant of many things
Posts: 63
Karma: 9304
Join Date: Feb 2011
Device: Kobo Libra 2
|
Quote:
What I did was to disable the first patch. Code:
<Patch> patch_name = `Disable reading footer style` patch_enable = `yes` Code:
patch_name = `Custom reading footer style` |
|
08-17-2013, 05:07 PM | #36 | |
Bibliophagist
Posts: 34,537
Karma: 144552660
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
In that rather long line, you'll find the various devices referred to in two places. The first reference seems to be the factory values and I think it is being used to check that you are modifying a factory libnickel.so.1.0.0 so I would not modify it. The second reference is the one to be modified. I've included both sets here. Since I have an Aura, these are way I set the values for it: First reference: ReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 120px;\n\tmax-height: 120px;\n\tqproperty-footerMargin: 20; Second reference: ReadingFooter[deviceCodeName="dragon"] {\n\tmin-height: 60px;\n\tmax-height: 60px;\n\tqproperty-footerMargin: 10; For a Glo, you would modify the values in the second reference to kraken/phoenix. Since the Glo is lower resolution, I'd suggest trying values around 40 for the min and max height. I still haven't found what the footerMargin does so I'd suggest setting it to 10. ReadingFooter[deviceCodeName="kraken"], ReadingFooter[deviceCodeName="phoenix"] { min-height: 40px; max-height: 40px; qproperty-footerMargin: 10; } To make it easier to read the line, I copied it into my favourite text editor and replace the \n pairs with an end of line and the \t pairs with a tab character which gives a result similar to below. Code:
`ReadingFooter { min-height: 70px; max-height: 70px; qproperty-footerMargin: 40; } ReadingFooter[deviceCodeName="kraken"], ReadingFooter[deviceCodeName="phoenix"] { min-height: 82px; max-height: 82px; qproperty-footerMargin: 110; } ReadingFooter[deviceCodeName="dragon"] { min-height: 120px; max-height: 120px; qproperty-footerMargin: 20; } * { font-size: 16px; } [deviceCodeName="kraken"], [deviceCodeName="phoenix"] { font-size: 20px; } [deviceCodeName="dragon"] { font-size: 26px; } [localeName="ja_JP"] { font-family: A-OTF Gothic MB101 Pr6N; }`, `ReadingFooter { min-height: 70px; max-height: 70px; qproperty-footerMargin: 40; } ReadingFooter[deviceCodeName="kraken"], ReadingFooter[deviceCodeName="phoenix"] { min-height: 82px; max-height: 82px; qproperty-footerMargin: 110; } ReadingFooter[deviceCodeName="dragon"] { min-height: 60px; max-height: 60px; qproperty-footerMargin: 10; } * { font-size: 16px; } [deviceCodeName="kraken"], [deviceCodeName="phoenix"] { font-size: 20px; } [deviceCodeName="dragon"] { font-size: 26px; } [localeName="ja_JP"] { font-family: A-OTF Gothic MB101 Pr6N; }` Regards, David Last edited by DNSB; 08-17-2013 at 05:26 PM. |
|
08-17-2013, 06:13 PM | #37 |
Addict
Posts: 255
Karma: 1151364
Join Date: Aug 2009
Device: Aura HD and H2O
|
It's not working for me. If I change anything in the line that starts with replace_zlib, for example change the first 70px to 60px, I get an error "Data for replace in libnickel.so.1.0.0 and kpg.conf does not match!"
If I run it with the exact same original text, then it works. |
08-17-2013, 06:23 PM | #38 |
Addict
Posts: 255
Karma: 1151364
Join Date: Aug 2009
Device: Aura HD and H2O
|
Okay, that part just sunk in, and I think I'm getting it now. Thanks DNSB
|
08-17-2013, 06:35 PM | #39 |
Bibliophagist
Posts: 34,537
Karma: 144552660
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
|
08-17-2013, 09:13 PM | #40 |
Junior Member
Posts: 3
Karma: 10
Join Date: Aug 2013
Device: Kobo Glo
|
Thank You
Thanks, David, for making that much clearer. I was sure I was already changing the proper values, but I must not have been. I was able to change the right values and experimented with some different numbers. I ended up at 30, 30, 10. This leaves me with perhaps a little more than one line blank between the page numbers and the text. I found if I went any lower, the page numbers began to sink beneath the edge of the screen.
If anyone cares to see, I've attached a screenshot. Thanks again, I really appreciate the help, especially as a new member. Keith |
08-17-2013, 09:39 PM | #41 |
Addict
Posts: 255
Karma: 1151364
Join Date: Aug 2009
Device: Aura HD and H2O
|
I also have things mostly working at this point. One thing I can pass along, be careful what epub you use for testing. I think the Kobo has some quirky rendering. My test book had every para nested in a div (don't ask my why). This shouldn't have mattered, but it turns out it was causing extra space on the Kobo that I mistakenly thought was a problem with the settings in the patch, and I wasted a lot of time fiddling with settings.
Once I tried a few other books with regular paras for markup, I got results like the screen capture in post #13 of this thread. |
08-18-2013, 02:54 AM | #42 |
Member
Posts: 21
Karma: 194
Join Date: Nov 2008
Device: Cybook Gen 3
|
I've been playing with values for Aura and here they are.
I'm now using values 5/45/8 and also changed font size from 26 to 20 px. It gives all the lines of text that can fit on screen plus page number indicator on the bottom. The most important values I think are footer margin and font size, if I raised footer margin to 10 I've lost one line of text. |
08-18-2013, 03:23 AM | #43 |
Wizard
Posts: 1,176
Karma: 2431850
Join Date: Sep 2008
Device: IPad Mini 2 Retina
|
My take on this is that the first reference is for when you disable a particular patch, in which case the first reference is used to revert the binary to the original values in the firmware download (in case you had previously enabled that patch).
|
08-18-2013, 10:15 AM | #44 |
Addict
Posts: 255
Karma: 1151364
Join Date: Aug 2009
Device: Aura HD and H2O
|
I've noticed changing the dragon font-size, only some values work, like 26px, 36px, 40px, 1em. Others like 34px cause a "zlib string for replace is too large" error when running kpg.exe.
|
08-18-2013, 10:33 AM | #45 | |
Grand Sorcerer
Posts: 12,119
Karma: 73448614
Join Date: Nov 2007
Location: Toronto
Device: Nexus 7, Clara, Touch, Tolino EPOS
|
Quote:
So for instance if the original CSS was (copying from DNSB) Code:
[deviceCodeName="kraken"], [deviceCodeName="phoenix"] { font-size: 20px; } [deviceCodeName="dragon"] { font-size: 26px; } Code:
[deviceCodeName="dragon"] { font-size: 26px; } |
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Glo How to import reading Life Statistics from Kobo Touch to Kobo Glo? | the_m | Kobo Reader | 5 | 12-13-2012 03:40 PM |
$25 gift card w. purchase of Kobo Touch or Kobo Vox at Frys | sufue | Deals and Resources (No Self-Promotion or Affiliate Links) | 0 | 07-15-2012 10:39 AM |
Touch Kobo Touch defective after 3 months and Kobo Customer Support useless | shaf | Kobo Reader | 5 | 12-04-2011 05:10 PM |
Touch Kobo Touch not ejecting cleanly with Calibre OR Kobo Desktop - Windows 7 | JBlyth | Kobo Reader | 11 | 08-03-2011 05:38 PM |
Kobo Touch not disconnecting properly from Calibre OR Kobo Desktop - Windows 7 | JBlyth | Devices | 1 | 08-03-2011 06:50 AM |