Koreader running on Kobos (all of them, hopefully!)

[ebrahimpak]

Ok everybody. I got a problem with this great Koreader application. Before that, I should appreciate all the hard work behind the scenes. It surely revlutionized my Aura HD. Once I tap the words in order to check their definitions, I got some illegible characters instead of the words' phonetic descriptions and/or their Greek or Germanic characters in their etymology section. There are some folders in the /Koreader/.../... directory seemed to be allocated for the Koreader internal fonts, but I got no idea which folder is designated to the dictionary fonts and which folder is reserved for the body-text fonts. Besides it would of great help if anybody assist me in choosing among the myriads of available fonts so as to be able to get usable phonetic descriptions.
Another question: I wonder whether it is possible to reduce the amount of artifacting. Surprisingly it only happens on some of my PDFs and not all of them. I have installed the latest versions of Koreader (for Kobo) + Fmon. In nickel one can change the refresh rate in a range between 1 to 6 pages. I prefer to be given the same amount of leeway in Koreader.

[JimMcLaren]

Originally Posted by ebrahimpak

In nickel one can change the refresh rate in a range between 1 to 6 pages. I prefer to be given the same amount of leeway in Koreader.

You can set this by editing defaults.lua. Find these lines

-- number of page turns between full screen refresh
-- default to do a full refresh on every 6 page turns
DRCOUNTMAX = 6

Change this to whatever you desire. I've set mine to 2. This post talks about using defaults.persistent.lua to keep this from being overwritten.

[ebrahimpak]

Originally Posted by JimMcLaren

You can set this by editing defaults.lua. Find these lines

-- number of page turns between full screen refresh
-- default to do a full refresh on every 6 page turns
DRCOUNTMAX = 6

Change this to whatever you desire. I've set mine to 2. This post talks about using defaults.persistent.lua to keep this from being overwritten.

Thank you very much. I'm still thinking about the dictionary font thing.

[Ken Maltby]

Originally Posted by xor_

That is what I mean. Hadn't noticed it before either, but build 398 does that on my Glo. And I'd like to adjust that time value.

Big kudos to the developers, btw. This project is coming along very nicely.

//Edit: Hmm. Could it be that the suspend was triggered by nickel still running in the background? After installing advboot, and running koreader without nickel, I haven't seen it anymore.

It could be Nickel, I start Koreader from tshering's Kobo Start Menu, and that would prevent Nickel's background functions from bothering me also.

Luck;
Ken

[xor_]

Originally Posted by Ken Maltby

It could be Nickel, I start Koreader from tshering's Kobo Start Menu, and that would prevent Nickel's background functions from bothering me also.

That's probably it then. That might also explain the short time interval: Nickel suspends the device after its normal time period. I wake it back up. Nickel still hasn't received an input event, and shuts it right back down.
It would also explain why I couldn't find a variable to adjust in koreader.

[Ken Maltby]

Originally Posted by xor_

That's probably it then. That might also explain the short time interval: Nickel suspends the device after its normal time period. I wake it back up. Nickel still hasn't received an input event, and shuts it right back down.
It would also explain why I couldn't find a variable to adjust in koreader.

As a feature, it might make some sense for Nickel as it has more background processes that could be using power, even when no pages are being turned. Not so for Koreader, when Nickel is not used to launch it. (It doesn't have a database to maintain or Google Analitics to report to, nor is it running browser support (Hindenberg) all the time.) So, while a user inactivity shutdown might make sense if the Kobo software is running, it is not needed for just e-ink reading.

Luck;
Ken

[Ken Maltby]

Originally Posted by Ken Maltby

This could be looked at as something the Koreader team should look into, to make the file handling features they added to File Manager functional on Kobo devices.

That the scripts can be modified, by those with the need, is something on a use at your own risk basis. It need not be addressed in KSM at all. But if you wanted to it could be an optional way to start Koreader, perhaps "Start Koreader (with SD r/w)" and have it call a modified koreader_kobo.sh. But it seems to me that it is an issue that the Koreader team should be fixing, when they get time.

Luck;
Ken

I just tried the 398 Android app and you can't delete files from the "removable" card either. Don't know if it is the same problem or if the OS has that card as read only.

Luck;
Ken

[ebrahimpak]

It's strange that Koreader could handle the PDF images so well, but the epub images shown very pallid and whitish. I checked many epubs and it seems Koreader handles them the same way. Any workarounds guys?

[WS64]

Originally Posted by ebrahimpak

It's strange that Koreader could handle the PDF images so well, but the epub images shown very pallid and whitish. I checked many epubs and it seems Koreader handles them the same way. Any workarounds guys?

In case you are referring to GIFs only I have created an issue at GitHub already (#671).
In case you also mean PNG or JPG please post an example.

[paola]

apologies guys, could you please tell me which is the most stable of the recent nightly build (for my 6" Aura)? I haven't updated for a couple of months now.

[NiLuJe]

Unless something you rely on is broken (and without an already open issue about it), I'd recommend forgoing any notion of 'stable' release, and simply using the latest nightly available.

(Warning: I'm a *huge* fan of rolling releases, so, err, I'm a bit biased here ;p).

[Ken Maltby]

Originally Posted by ebrahimpak

It's strange that Koreader could handle the PDF images so well, but the epub images shown very pallid and whitish. I checked many epubs and it seems Koreader handles them the same way. Any workarounds guys?

I don't see that with Koreader in epubs or pdfs. It is likely dependent on the ebooks more than the reader.

I used Sigil to make a test .epub and added a .jpg file (a cover file I had on hand.) Then I made a screenshot in Koreader and converted the .pam file to the .jpg below.

You can see that it opened in the cr3 engine not the MuPDF based renderer.

Luck;
Ken

[trekk]

@paola: The latest nightly works fine on my Aura and seems to be very stable. There might be some problems I don't notice, because I use tshering's Kobo Start Menu and therefore avoid nickel!

[paola]

Originally Posted by trekk

@paola: The latest nightly works fine on my Aura and seems to be very stable. There might be some problems I don't notice, because I use tshering's Kobo Start Menu and therefore avoid nickel!

thanks Trekk, good enough for me then :-)

@NiLuJe: same for me with the Mini, but as the Aura does not have an SD card, I live in the dread of bricking it!

[ebrahimpak]

Originally Posted by Ken Maltby

I don't see that with Koreader in epubs or pdfs. It is likely dependent on the ebooks more than the reader.

I used Sigil to make a test .epub and added a .jpg file (a cover file I had on hand.) Then I made a screenshot in Koreader and converted the .pam file to the .jpg below.

You can see that it opened in the cr3 engine not the MuPDF based renderer.

Luck;
Ken

Yes, but that's jpeg. I'm talking about the embeded gif images in epub. Koreader can't show them correctly. Is there a way to circumvent the issue, apart from decompressing the epub, changing the images' file format and rebundling the epub package?