Quote:
Originally Posted by Godzil
Do you try to resend them a mail about this problem? Did you try the 2.0 firmware? 1.5 and 2.0 firmware don't use the same HTML renderer, and I suspect the bug you had was from the MobiSDK
|
Yes, once. I can't go on assumming more than 75% of my mails to them will be lost every time, so I assume they received it.
Nearly all of my books are in Mobi format, and I have the first Gen3 model, with 32MB of memory. I think firmware 2.0 doesn't work well on it. So I'm using firmware 1.5, and the bug is still not fixed in it.
Quote:
Originally Posted by EowynCarter
That don't prevent your reader from working right ? Because a broken screen definitively do.
I mean really need help in the sense : reader totally unusable.
|
Well, it's not what was advertised to me by Bookeen. I bought a reader that's supposed to handle basic HTML, I got one that doesn't handle it. I expect only the fact that most people don't use this particular format prevents public opinion from calling it fraud.