Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader > Kobo Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 08-17-2013, 06:50 AM   #31
henriquemaia
Enthusiast
henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.
 
Posts: 47
Karma: 9304
Join Date: Feb 2011
Device: kobo glo, kindle 3
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.
henriquemaia is offline   Reply With Quote
Old 08-17-2013, 07:24 AM   #32
jiminrussell
JimInRussell
jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.jiminrussell writes the songs that make the whole world sing.
 
jiminrussell's Avatar
 
Posts: 181
Karma: 40716
Join Date: Nov 2010
Location: Russell Ontario Canada
Device: kobo Aura HD, Aura, Glo & Mini
@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.
jiminrussell is offline   Reply With Quote
Old 08-17-2013, 08:53 AM   #33
treadlightly
Guru
treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.treadlightly ought to be getting tired of karma fortunes by now.
 
treadlightly's Avatar
 
Posts: 864
Karma: 3581364
Join Date: Nov 2010
Location: Ottawa, ON
Device: Kobo Glo
Quote:
Originally Posted by jiminrussell View Post
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.
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.
treadlightly is offline   Reply With Quote
Old 08-17-2013, 01:05 PM   #34
kslaght
Junior Member
kslaght began at the beginning.
 
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
kslaght is offline   Reply With Quote
Old 08-17-2013, 02:09 PM   #35
henriquemaia
Enthusiast
henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.henriquemaia can eat soup with a fork.
 
Posts: 47
Karma: 9304
Join Date: Feb 2011
Device: kobo glo, kindle 3
Quote:
Originally Posted by kslaght View Post
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
You're right, I was far from clear.

What I did was to disable the first patch.

Code:
<Patch>
patch_name = `Disable reading footer style`
patch_enable = `yes`
And customized the footer on the second patch

Code:
patch_name = `Custom reading footer style`
When I did this, it worked as expected.
henriquemaia is offline   Reply With Quote
Old 08-17-2013, 05:07 PM   #36
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 1,809
Karma: 5685462
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Aura HD, Glo, Nexus 7, iPad 3
Quote:
Originally Posted by kslaght View Post
Hi everyone

Thanks for getting this info out there, and for reformatting and coloring the config file, treadlightly.

I cannot, however, get this to work on my Glo with 2.8.1.
I copied treadlightly's config file and then changed only the 3 numbers in green to 60,60,10 (as mentioned a few times), but didn't see any results after updating. Same results with different numbers.

I then enabled the 'Disable reading footer style' patch, and it worked. I don't want to get rid of the page numbers, but at least I know my updates are being applied.

I tried using the original config file, just in case I copied it poorly, which didn't work either.

Am I missing something here? I believe I've done this all properly, but perhaps someone can provide my missing link.
I left the first patch (Disable reading footer style) set to patch-enable = no and the second patch (Custom reading footer style) set to patch-enable = yes.

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;
}`
Good luck!

Regards,
David

Last edited by DNSB; 08-17-2013 at 05:26 PM.
DNSB is offline   Reply With Quote
Old 08-17-2013, 06:13 PM   #37
ectoplasm
Addict
ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.
 
Posts: 216
Karma: 1141606
Join Date: Aug 2009
Device: Android tablet, Kobo Aura HD
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.
ectoplasm is offline   Reply With Quote
Old 08-17-2013, 06:23 PM   #38
ectoplasm
Addict
ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.
 
Posts: 216
Karma: 1141606
Join Date: Aug 2009
Device: Android tablet, Kobo Aura HD
Quote:
Originally Posted by DNSB View Post
..
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.
Okay, that part just sunk in, and I think I'm getting it now. Thanks DNSB
ectoplasm is offline   Reply With Quote
Old 08-17-2013, 06:35 PM   #39
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 1,809
Karma: 5685462
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Aura HD, Glo, Nexus 7, iPad 3
Quote:
Originally Posted by ectoplasm View Post
Okay, that part just sunk in, and I think I'm getting it now. Thanks DNSB
You're welcome.

Regards,
David
DNSB is offline   Reply With Quote
Old 08-17-2013, 09:13 PM   #40
kslaght
Junior Member
kslaght began at the beginning.
 
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
Attached Thumbnails
Click image for larger version

Name:	Kobo Glo Patcher 30 30 10.png
Views:	315
Size:	120.4 KB
ID:	109570  
kslaght is offline   Reply With Quote
Old 08-17-2013, 09:39 PM   #41
ectoplasm
Addict
ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.
 
Posts: 216
Karma: 1141606
Join Date: Aug 2009
Device: Android tablet, Kobo Aura HD
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.
ectoplasm is offline   Reply With Quote
Old 08-18-2013, 02:54 AM   #42
grucha44
Member
grucha44 began at the beginning.
 
Posts: 11
Karma: 10
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.
grucha44 is offline   Reply With Quote
Old 08-18-2013, 03:23 AM   #43
ShellShock
Guru
ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.ShellShock ought to be getting tired of karma fortunes by now.
 
ShellShock's Avatar
 
Posts: 854
Karma: 1639368
Join Date: Sep 2008
Device: Sony PRS-505 & PRS-650, Kobo Glo & Aura HD
Quote:
Originally Posted by DNSB View Post
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.
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).
ShellShock is offline   Reply With Quote
Old 08-18-2013, 10:15 AM   #44
ectoplasm
Addict
ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.ectoplasm ought to be getting tired of karma fortunes by now.
 
Posts: 216
Karma: 1141606
Join Date: Aug 2009
Device: Android tablet, Kobo Aura HD
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.
ectoplasm is offline   Reply With Quote
Old 08-18-2013, 10:33 AM   #45
PeterT
Taking a break; Fed up
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
PeterT's Avatar
 
Posts: 6,450
Karma: 42483084
Join Date: Nov 2007
Location: Toronto
Device: Wife: Touch, Arc, Vox Me: Nexus 7, Glo
Quote:
Originally Posted by ectoplasm View Post
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.
This might be a long shot, but I wonder if one could remove sections of the CSS that do not apply to your particular device? This should (in theory) help as it would ensure that the data to be compressed was less, and should more easily be storable within the original space in libnickel.so.

So for instance if the original CSS was (copying from DNSB)
Code:
[deviceCodeName="kraken"], 
[deviceCodeName="phoenix"] {
	font-size: 20px;
}

[deviceCodeName="dragon"] {
	font-size: 26px;
}
and you were just patching for a dragon class device then
Code:
[deviceCodeName="dragon"] {
	font-size: 26px;
}
should suffice.
PeterT is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

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, Freebies, and Resources (No Self-Promotion) 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


All times are GMT -4. The time now is 07:34 AM.


MobileRead.com is a privately owned, operated and funded community.