|
Seems to me that if I want e-ink, I am stuck with either ADE (which I rather hate from my PRS-505) or FBReader with missing features :-(
I wonder - just why do e-book manufactures avoid mature HTML engines and instead opt for brand new, and apparently worse, implementations? Is it simply that they won't use a DRM-less implementation?
On a related note: I have seen that a number of reader manufacturers support developing of tools for their devices. Does it mean that it would be possible to compile, say, a WebKit-based reader for them and use it instead of the default one? Has this been tried at all?
|