Quote:
Originally Posted by embryo
Well, AFAIK koreader reads the ebook's CSS also (to a certain degree), but has an 'option' to turn this off.
And the patcher that you use is not part of the reader but a great effort of people that liked the 'option' to use all of their screen for reading.
Option that the reader does not gives you.
|
Actually, with the current firmware you can use 100% of the screen for reding epubs in full-screen mode, no patch needed. A patch is only required to do the same for kepubs.
Quote:
But you see, this is the problem with the nickel approach.
You live with a ticking bomb.
If the reader needs a factory reset, the nickel re-index (for hours) the library.
If the reader connects to the PC, eventually the database will be corrupted and it will re-index (for hours) the library.
Your only hope is the backup of the database, something you have to do with every library update, is not the easiest thing to do, and its not an option of the nickel.
I don't want to know what will happen if a corruption occurs on a trip away from your PC.
|
I've had my Glo for over two years and never had a corrupted database. I have only factory reset once in the last two years and that was due to an accident when I was experimenting with a new patch. I also reset a few times when I first got the device as a result of my own ignorance, but never needed to factory reset as a result of any problem with nickel.