Thread: BeBook review
View Single Post
Old 08-25-2009, 01:48 PM   #15
tompe
Grand Sorcerer
tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.
 
Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
Quote:
Originally Posted by Dave_S View Post
I
A parser should never just throw up it's hands and run home to mama when it comes to a formatting command that it does not understand, but that is what I have found the BeBook firmware to do. Incorrect rendering in that case would be a better action than total catastrophic failure. It has NEVER happened to me when running OpenInkpot firmware on the BeBook, so the BeBook hardware seems OK.
You have this problem in the Cybook Gen3 reader also. I totally agree with your argument and my next reader will be a reader where I can run open source programs like OpenInkpot or where I can fix problems myself. Hopefully the txtr reader will satisfy these demands.
tompe is offline   Reply With Quote