View Single Post
Old 09-13-2014, 09:57 AM   #13
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by violent23 View Post
Maybe the reviewer should have tested all of the features of the device because if he had he would have run into a lot of bugs including the problem with annotations and bookmarks. These are core features and any competent reviewer would have tested them.

Beyond that I don't really expect a Techcrunch review to find the embedded font issue nor the cut off fonts, no italics and bold on some fonts in .epub or the widow and orphan issues when using .epubs as he most likely never even tested .epubs on the device or really delved as deep as some of us enthusiasts have into the firmware of said device. Not that it is an excuse to not find these problems as it really is his job.
Personally, I would expect a reviewer to see the font problems before the annotation problems. Part of that is visibility, and part is that I consider the display of the book a much more important function than recording annotations. When I saw that the Kobo devices could highlight text and store annotations, my thought was, "That's a nice extra function".

And if you think the reason they didn't notice the font issues was because they didn't read epubs, then that would also explain why they didn't see any annotations problems. I can't think of a bug in the annotations handling that is not an epub related bug. In fact, the bug that Anak referred to only happens if you annotate an epub that is stored on the main memory and close and reopen it.
davidfor is offline   Reply With Quote