It's possible that my problem arose because I didn't take the precaution of storing all my KOReader books in a 'hidden directory' so that the Kobo apps couldn't see them. It happened each time I loaded/configured KOReader then connected to calibre. At that time I did get problems with my Kobo database getting corrupted. The Kobo standard PDF reader trails a long way behind what I experienced on my Sony eink devices.įull disclosure, it's about 18 months since I tried KOReader and things may have changed a lot since then. On the other hand, KOReader is much better for PDFs than the standard Kobo app is, but still not as good as a medium-sized tablet with a decent PDF app would be. BTW I don't believe the Kobo font thickening would be used inside KOReader, but I'm happy to be told otherwise. If rendering an epub like your Sony would have rendered it is important I think the Kobo standard ADE renderer is likely to suit you better - fixing the epub css predictably fixes the epub rendering for me. However, I'm guessing that your library isn't like this because you've already fixed the source epubs to suit your tastes. If you have an Android device you can easily try it for free. ĬoolReader is very configurable and can bring some kind of respectability to a library full of horribly formatted epubs. What sort of bugs/flaws are there due to using the CREngine? What advantages does it have in terms of rendering correctly? Does it hyphenate? Can I customize the font sizes and line height? Does it work with Kobo's font optimization so once I have used it to tweak a font, it will render the These are just personal opinions/observations. No full-text indexing (some people consider that a feature, especially those with some thousands of documents on their readers). Or FB2 format, rudimentary DOC, HTML support. Simple things, like built-in night mode, complex things, like page-layout optical recognition based PDF reflow (using k2pdfopt internally). I guess the strength of it lies in other places as ePub rendering (though it does that well enough for quite a lot of people). So you can expect it to fail in the same places. It uses CREngine for that, which is the rendering engine behind CoolReader. That said - the reader does not implement ePub rendering on its own. Some things are plain configuration things. shows with your documents and bothers you, is dependent on the documents and personal taste. It probably boils down to personal This reader "casually ignores" quite a lot of stuff. Thanks for the Maybe a tad bit more configurability. That certainly needs further investigation. And if we're unlucky, it's some bad interaction with nickel (the native framework). Koreader doesn't touch anything beside its own files, so I can pretty sure exclude a direct modification by Koreader here. Hm, that thing about pocket is strange indeed. Yes, v2014-04 didn't even know that a H2O exists (did it at the time?) :-) The new stable, as well as current nightlies (well, those that are not broken during development) should work on H2O. My bad - I instinctively read v2014-11, since we just (as in, a few hours ago) released that. kobo after koreader installation that the file kobo nf was been modified while installing start menu and Koreader, and some text had disappeared, like the section. New facts 19h26 : I find out in the back-up of. kobo, and pocket works well again : I can find my new articles. The library synchronize well (it seems to), but not pocket. I tried earlier the Calibre Companion and active wi-fi with Koreader, but I didn't test pocket before that. I tried to unconnect, reconnect, reboot, check wi-fi, check pocket. I find other people who have the same result (just google it).īut I just find out that there is a problem with the nightly version : pocket can't synchronize. And then with the nightly version : it works. Two installations to be sure with the stable version. Freeze, can't reboot, so I have to reset. I did all that very carefully, step by step, with the explanations found here (start menu) and there in github. Did you use the version from Github downloads or OTA update? Did you reboot and/or reinstall? Does it just freeze (not react to any input, I guess?) or reboot, too? Hm, are you sure about that? I think we have had positive feedback for the H2O.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |