Quote:
Originally Posted by newman
- - - -
(Sorry for speaking in riddles and not being specific enough, trying not to violate MR Guidelines.)
--
Looking at NetSurf (framebuffer version) it does not seem to require much less memory that Kindle's experimental WebKit browser. Each require about 60 MB of memory but pages rendered by WebKit look way better, plus it supports javascript; though NetSurf may render more swiftly.
|
As I have observed the guidelines enforcement - -
You can discuss anything, post anything **except** other people's property without permission.
Nor can you post any **direct** links to other people's IP.
**BUT** you can post links to off-site resource listings, just as long as they don't 'click-through' to IP. That is, a person has to read (ah, cut and paste) the link(s) from the listing.
That is in part a historical thing here with the owners/operators - -
In the very early days of Mobileread they had troubles over DRM'd books.
A long story short; they where innocent and intended to stay that way. Also, they intended to avoid any conflicts in the future.
Bottom line: Write up whatever needs to be written up and/or discussed - just don't post the resulting file.
and/or
Run bzdiff on the before and after files, post the resulting bzpatch file. That **should** fall under the 'fair use quote' exceptions.
A very recent thread described the generalization of TTS on 3.4.2 -
a bzpatch file for that one *.jar file change would probably be acceptable here.
Buildroot(.org) will build those tools for you, IIRC. The early Kindles have bzpatch installed on them.
- - - - -
Thanks for taking the time for checking on NetSurf - -
A solid, 'almost works' is good to keep in mind for now.
As that 2.5.8 firmware drops further and further out of date, the user demand for a replacement may eventually reach the point that the 'make it work' effort will be worthwhile.