Quote:
Originally Posted by mclien
According to GPL it's not just border to...
Another reason, why my next reader surely isn't a PB.
To my font problem: Just noticed that I get diffrent fonts in Adobe and fbreader. Is that to happen with embedded fonts? (i don't think so. To me more likely a bug in FB, what leads back to qariwa55.
So again I stand with the question what actually will be my next reader...
|
They DID list the source of components that use GPL-ed code. How do you think the third-party FBReader180 came to life? Some clever hacker took that source of the default FBReader and improved it.
There is even Linux terminal for PocketBook devices that you can use to look around inside live system. It was developed during competition that was sponsored by PocketBook company.
Just have a look here:
https://www.mobileread.com/forums/sho...46#post1834646
You download the offcial SDK and you can compile your own version of programs included on PocketBook.
They (the PocketBook company) are
NOT perfect, and it took them awfully long time to publish sources, and they haven't published sources of proprietary stuff that was developed without GPL components, but it is still WAAAAAAY more then the vast majority of e-ink reader manufacturers.
Have a look around. I challenge you. Find another manufacturer that provides an SDK in meaningful form.
I challenge you. Download GPLed code that Sony has provided on their site to satisfy legal requirements and try to do something with it. Download code from Amazon, Kobo, or other manufacturers.