Quote:
Originally Posted by SCION
I would buy this reasoning, except I didn't/don't experience these issues on other devices. Specifically the NOOKtouch and Sony 950. Others have no issues on their non-Kobo devices. So, if I own three eink devices, and I'm only having a problem on one of them (with the same stored content), then there's a problem with that device. From the posts in this forum it appears that many are lifelong Kobo users and haven't used anything else or their expectations are minimal and fault tolerance is high.
|
While I understand the logic, you need to understand that different device/company/OS = different implementation of rendering. I mean, you get this all the time. you used to see this a lot with Web browsers (still do to an extent) where depending on which browser you used, a web page might come up very differently, or very buggy looking. In most cases, it was because a) the standards used by the browser developer were not standard, or b) the website developer only developed it for one browser.
As a prime example in regards to the KT; a sideloaded book downloaded directly from kobobooks will work flawlessly in the KT in terms of formating. However, If I buy the same book from Amazon, de-drm it, run it through Caliber to convert it to epub, Formating options will be flakey, if not non-functional; I know, I've done it. Now, is this Kobo's problem because they can't render something that I've done outside the norm? Personally, I don't believe so.
again, just my opinion
