KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)

[pantera10684]

Originally Posted by knc1

description says that, i can open epub file with koreader, but i was not successful

[knc1]

Originally Posted by pantera10684

description says that, i can open epub file with koreader, but i was not successful

We really need more details than "did not work".

http://www.gerv.net/hacking/how-to-ask-good-questions/

[pantera10684]

Originally Posted by knc1

We really need more details than "did not work".

http://www.gerv.net/hacking/how-to-ask-good-questions/

file corrupted, excuse me

[knc1]

Originally Posted by pantera10684

file corrupted, excuse me

I was not joking, please read and follow these directions:
http://www.gerv.net/hacking/how-to-ask-good-questions/

[natto]

I compared the rendering effects on KPW1 and KPW2, and found that the current redering waveform seems not suitable for KPW2? KPW2 uses the Carta E-ink with REGAL waveform, which is not reflected in the current Koreader release.

In KPW1, the ghost is negligible and the blank space is white, which make the rendering effect great. However, in KPW2, the screen becomes blurred even after turning over 2 or 3 pages. There is significant character ghost from previous pages and the blank space is not white any more, in other words, not like it used to be as in KPW1.

I report an issue in GitHub(issue id: 550) with 2 figures which I hope could help to illustrate the different rendering effect of KPW1 and KPW2.

[Ebri]

I usually modify defaults.lua in koreader root directory, but it always get overwritten by new versions. Is there safer way to personalize koreader, but not to do it every upgrade? (Probably i missed something in the earlier posts, but i have not found it.)

Thank you!

[thomass]

Originally Posted by Ebri

Is there safer way to personalize koreader, but not to do it every upgrade?

this may help:

Originally Posted by hawhill

the global config file (settings.reader.lua, created by the first run of koreader). That is probably a more proper place to set it - it would survive an update of koreader.

[Ebri]

Thank you, should i simply copy here the relevant parts from the other config file? Will they not collide?

Thank you!

[hawhill]

I don't think that there's a good way for defaults.lua yet. It wouldn't be too hard for us to do a check for a defaults.local.lua at the end of parsing defaults.lua and include that if present, I guess, but such a thing is not there yet.

The settings.reader.lua is not parsed the same way as defaults.lua, it is not interchangeable.

[Ebri]

Thank you, maybe if i will have more time i will check the source code (though this might never come...), but i think there are more important things to do (for me a more user friendly frontlight settings would be quite welcome, or supporting more format, which requires more time and efforts anyway.)

(And DOC support saved me quite some time this week, so it is really very helpful!)

[MaxStirner]

Possible bug - Font changing in EPUB does not work smoothly. Usually to change font you have to additionally toggle style, wieight and (or) font size back and forth and only then the change takes effect.
KPW1 latest nightlies, but the "bug" is there for a long time.

[eureka]

There is an issue about implementing TTS. Just for the reference, here is a method of using stock TTS on Kindle Touch:

echo $'\033W4 hello' > /tmp/ttsUSFifo

A bit more info here.

[phoenix512]

I installed koreader. It's great except I couldn't find pan and zoom feature. zooming with fingers just increase front-light. Is there such feature in koreader?

[anton79ru]

Guys, I've been using KOReader for three weeks now and I have encountered several instances of my PDF files becoming corrupt in one of the following ways:
- several consecutive pages becoming blank;
- pages displaying large random geometrical figures instead of text;
- pages deleted (like a 27-page pdf becoming a 2-page pdf).

The application crashes pretty often, which might well be the cause. Has anyone noticed such behavior too? Is there any way to remedy this, apart from backing up the entire contents of my Kindle every now and then? Thank you.

[hawhill]

Hm. Do you run other software? Something's really wrong here.

For a start, if koreader crashes, it might leave some hint in the file "crash.log" as of why it crashed. It shouldn't really crash, though. However, the Kindle is a quite memory restricted environment, and at some point of document complexity, it might well crash, unfortunately.

Then it should open the documents mostly for reading. The newer versions *can* write to PDFs (and if they happen to crash in that very moment, it *might* lead to corruptions, I guess), but they will do so only for saving highlights. That said - I have no idea why Koreader should leave corrupted documents behind. It clearly shouldn't - for technical reasons. So that leads me back to my original question: is there other software running?