Touch Kobo Touch future firmware feature request thread

[Akerbos]

I have observed the font issue, too, but have not investigated further.

Another idea: PDFs often have generous margins all around the text. If we could cut away that useless white space, PDF documents would be much more readable without zooming in. Therefore, I suggest a feature to crop PDF files. For every document, users would be able to "draw" a box that marks the area to show. Every page would be treated the same way; maybe even two-page layouts could be detected and accounted for.

[symon79]

New feature request for the Kobo Touch: the ability to read book descriptions/previews when browsing the library on the Kobo Touch.

Originally Posted by Akerbos

I suggest a feature to crop PDF files. For every document, users would be able to "draw" a box that marks the area to show. Every page would be treated the same way; maybe even two-page layouts could be detected and accounted for.

Better yet, do it automatically. This should be trivial to implement due to how PDFs are rendered.

A more difficult, albeit useful, feature to implement would be column detection and maybe even stacking the columns so that columns can be read sequentially by flipping through them like pages.

No matter how much I love eInk devices, the slowness scrolling through PDFs drove me to pick up a Vox as well. And while I like the Vox, there are times I had to leave it at home because I forgot to recharge it.

[The Terminator]

Originally Posted by symon79

New feature request for the Kobo Touch: the ability to read book descriptions/previews when browsing the library on the Kobo Touch.

They used to have that in the Kobo-1 firmware version 1.4 but then they got rid of it in firmware 1.8 (That's the current firmware version for the Kobo-1), and they haven't ever brought it back in any models or firmware. The Kobo WiFi, Kobo Touch and Kobo apps have never had the option.

[Xennex1170]

Originally Posted by The Terminator

They used to have that in the Kobo-1 firmware version 1.4 but then they got rid of it in firmware 1.8 (That's the current firmware version for the Kobo-1), and they haven't ever brought it back in any models or firmware. The Kobo WiFi, Kobo Touch and Kobo apps have never had the option.

Perhaps they thought it took up too much memory which could better be filled with other ebooks.

[Akerbos]

Originally Posted by BWinmill

Better yet, do it automatically. This should be trivial to implement due to how PDFs are rendered.

Dangerous. I would definitely want to cut away page numbers, but should/could the machine do that automatically? And what about scanned documents?

We can already use tools like BRISS, but that's a pain to do for many documents.

A more difficult, albeit useful, feature to implement would be column detection and maybe even stacking the columns so that columns can be read sequentially by flipping through them like pages.

Yup, that would be cool.

[GvilleBridge]

As I've accumulated a large ebook collection (thanks, PG and others!) and my personal RAM seems to be getting smaller by the day, I really need the Kobo firmware to implement book taggiing. Or as someone put it hundreds of posts ago in this thread:

"2. Collections, folders, tags, whatever."

[SF&F Reader]

Originally Posted by GvilleBridge

As I've accumulated a large ebook collection (thanks, PG and others!) and my personal RAM seems to be getting smaller by the day, I really need the Kobo firmware to implement book taggiing. Or as someone put it hundreds of posts ago in this thread:

"2. Collections, folders, tags, whatever."

Hey, that was me! Way back on page 14. . .

I would consider posting an updated wish list of features, but it would look pretty much the same as it did last July (other than #4 and #6 which have been taken care of). So instead, perhaps I'll update my plea:

Originally Posted by SF&F Reader

Make it the best darn ereader you possibly can before spending any energy on an extra feature like. . .

- The web browser
- facebook integration
- a list of books you think I'd buy but I probably won't because your list is not my list.

And I think I will take this opportunity to expand on that last one a bit. I've mostly come to terms with the presence of the recommended list and the creepy cyber-stalking that kobo uses to build it. I just wish it would work. I also don't see why it is on the Home screen instead of in the store.

[Matth79]

I'll add a request FOR the browser, options to force a more readable black on white display for sites that do not render well, and for animated GIF to either not animate, or make one pass only.

[voom]

Originally Posted by Matth79

I'll add a request FOR the browser, options to force a more readable black on white display for sites that do not render well, and for animated GIF to either not animate, or make one pass only.

My +1 for that

Any animation should be inhibited as it obviously does not make much sense with current eInk displays...

[symon79]

Originally Posted by Xennex1170

Perhaps they thought it took up too much memory which could better be filled with other ebooks.

No no, the book descriptions are still in the sqlite database (in the content table) for most books (I would say 90%).

Are the Kobo devs actually reading this thread?

I think it's really a must to be able to read book descriptions (otherwise you'll have to judge a book by it's cover instead of the content [preview] before start reading it;-)).

[Akerbos]

For me, browser certainly has lowest priority. Due to the device's restrictions, browsing is probably never going to be good so why bother.
I would rather see internet connection used where it matters, e.g. dictionaries, meta data, ...

+1 for showing previews of books in library (they often contain such texts).

[voom]

I suppose it would be a good idea to report the most often asked and mentioned issues to: help@kobobooks.com and/or: http://getsatisfaction.com/kobo

As I scanned through this thread I noticed that a Kobo-Dev has answered in the thread a few times last year and most important issues have been mentioned by then. Anyway, I have compiled a quick "Top 10" at least to my eyes of most important and moste requested and mentioned features and issues... at getsatisfaction.com/kobo:

http://getsatisfaction.com/kobo/topi...ith_kobo_touch

Feel free to report your urgent request yourself if it is not in my list

[ikarus9999]

Originally Posted by voom

I suppose it would be a good idea to report the most often asked and mentioned issues to: help@kobobooks.com and/or: http://getsatisfaction.com/kobo

As I scanned through this thread I noticed that a Kobo-Dev has answered in the thread a few times last year and most important issues have been mentioned by then. Anyway, I have compiled a quick "Top 10" at least to my eyes of most important and moste requested and mentioned features and issues... at getsatisfaction.com/kobo:

http://getsatisfaction.com/kobo/topi...ith_kobo_touch

Feel free to report your urgent request yourself if it is not in my list

- Collections Support has been added in Tweaks Plugin
https://www.mobileread.com/forums/sho...97#post1949197

[Xennex1170]

Originally Posted by symon79

No no, the book descriptions are still in the sqlite database (in the content table) for most books (I would say 90%).

Are the Kobo devs actually reading this thread?

I think it's really a must to be able to read book descriptions (otherwise you'll have to judge a book by it's cover instead of the content [preview] before start reading it;-)).

Actually I meant that it would take up onboard storage space regardless if the book description was part of the book or inserted in a field in the sqlite DB. How much space would you feel is adequate to allocate to the descriptions? Note for double byte character sets each character takes up 2 bytes. (e.g. 512 characters is 1K of storage space.) Which brings up the question how much storage space is currently used for each book record in the sqlitedb?

One feature I would find useful is to be able to move sideloaded books between the KT and the inserted microSD card.