Kobo future firmware feature request thread

Originally Posted by davidfor

I think you need to define what you mean by that.

Kobo needs the capabilities akin to koreader. koreader is pretty much everything a PDF reader should be, however, the vast majority of Kobo users will never use it.

I've personally known half a dozen people who have chosen other devices purely because of how bad Kobo's native PDF reader is. I consider this bad business on Kobo's part, which is a shame because they're the only company with any innovation these days...

[Rev. Bob]

I'd like to see two small enhancements to the "details" view of a book in the library, specifically in how it handles the OPF's <dc:description> field:

1. Boldface works, but italics don't. Why?
2. In the rest of the library interface, swiping up/down means the same as left/right - that is to say, both pairs translate to forward/back. But...not here. Again, why?

I'd think those would be pretty easy fixes.

[davidfor]

Originally Posted by Rev. Bob

I'd like to see two small enhancements to the "details" view of a book in the library, specifically in how it handles the OPF's <dc:description> field:

1. Boldface works, but italics don't. Why?

I can't see a good reason either.

2. In the rest of the library interface, swiping up/down means the same as left/right - that is to say, both pairs translate to forward/back. But...not here. Again, why?

It is a text area, not a list. Horizontal swipes and taps are what all the other text areas respond to.

[Rev. Bob]

Originally Posted by davidfor

It is a text area, not a list. Horizontal swipes and taps are what all the other text areas respond to.

All the same, the UI should be consistent. If swiping up/down works in some contexts, it should work in all of them. I notice this case because it occurs in a context where I can swipe up and down to navigate the list, then I look at details and expect up/down to continue working the same way.

I'd be just as happy to see up/down not work at all, in any context; it would be more limited, but the UI would be consistent.

[leftright]

Kobo Glo
v3.1.1

Settings > Library > "Remove all"

I tapped remove all, Cancel and Remove sub menu popped up, I then selected Remove whereupon the Remove label went black and there was no indication/feedback of what the unit was actually doing, was it frozen, or was it just "thinking and doing" ?.

I guess that removing the entire Library is CPU intensive, but would it be possible to improve visual feedback so that there is no doubt that the the OS hasn't frozen and that it is executing the command.

[fil9998]

I would appreciate so much

- adjustable system menus fonts (6,8" screen with tiny tiny fonts is ridiculous and frustrating)
- full fonts adjustment setting even for non-kepubs
- search firs in local library and THEN on the store
- better dictionaries: "'ing" and composite verbs are NOT recognized, even in english, in other -more complex- languages simply on board dictionaries DO NOT RECOGNIZE any verb that is not in its simplest form... in other worlds dictionaries are pretty UN-usable! kindle dictionaries are so much more better!

deleting articles in pocket needs 3 or 4 "clicks"... boring... also multi selection in pocket for deleting several items in one time would be VERY appreciated.


thanks a lot

[davidfor]

Originally Posted by fil9998

- full fonts adjustment setting even for non-kepubs

The full range of font adjustments is already there for epubs. And it is probably there for everything except PDF. Or did you want the advanced adjustments for sideloaded fonts?

- search firs in local library and THEN on the store

Yes please. But, it is this way if you start the search in the library list.

- better dictionaries: "'ing" and composite verbs are NOT recognized, even in english, in other -more complex- languages simply on board dictionaries DO NOT RECOGNIZE any verb that is not in its simplest form... in other worlds dictionaries are pretty UN-usable! kindle dictionaries are so much more better!

Yes please.

[MacBady]

Oxford dictionaries
pdf-reflow

[andromakie]

[QUOTE=fil9998;2775102]I would appreciate so much

- adjustable system menus fonts (6,8" screen with tiny tiny fonts is ridiculous and frustrating)

Yes please! It would make it much easier to read. Or at least adjustable font sizes.

I also wish I could choose to display the home screen in list view instead of the tiny thumbnails. My eyes aren't great and I cannot read a single title on the home screen. The original Kobo let you see the "currently reading" in list format. Why did this have to change?

[OverHaze]

The disparity between the rendering of epubs and Kepubs remains ridicules. There is no reason at all both can't be displayed equally well with the same features. If I download a book off of Project Gutenberg and upload it to my kindle it will be treated identically to any book I have bought from Amazons store. There is no reason the same should not be true for Kobo.

[PeterT]

But unlike Kindle, there are TWO distinct engines, coded by different organizations, each interpreting a provided specification.

This is the same as the fact that web pages do not render identically in IE / Chrome / FireFox / Opera.

[DNSB]

Originally Posted by OverHaze

The disparity between the rendering of epubs and Kepubs remains ridicules. There is no reason at all both can't be displayed equally well with the same features. If I download a book off of Project Gutenberg and upload it to my kindle it will be treated identically to any book I have bought from Amazons store. There is no reason the same should not be true for Kobo.

While a Kindle uses a single renderer for all ebooks, Kobo ereaders use two different renderers. .epub ebooks are rendered by the Adobe RMDSK software which does allow compatibility with Adobe's ADEPT DRM but limits ebooks to epub2 compatibility while .kepub.epub ebooks are rendered by the ACCESS NetFront renderer which uses Kobo's proprietary DRM and enables the use of epub3 features. Epub3 features, by the way, are pretty much a necessity in the Japanese market if you are going to handle Japanese typography oddities such as furigana, text can be written top to bottom, right to left or text written using 4 different character sets while remaining standards compliant.

I would suspect when the Adobe RMDSK is close to being fully epub3 compliant (Datalogic's RMDSK 10 release has moved quite a ways towards that point though they seem to concentrate more on hyping it's hardened DRM ), Kobo will return to a single renderer.

Given the problems that various implementors have in making web pages render identically -- try looking at many web pages in IE, Firefox, Chrome, Opera, etc, you are asking a bit much to have two renderers supporting different standards give identical results.

Regards,
David

[DNSB]

Originally Posted by PeterT

But unlike Kindle, there are TWO distinct engines, coded by different organizations, each interpreting a provided specification.

And lest we forget, two different specifications.

Regards,
David

[speakingtohe]

Originally Posted by PeterT

But unlike Kindle, there are TWO distinct engines, coded by different organizations, each interpreting a provided specification.

This is the same as the fact that web pages do not render identically in IE / Chrome / FireFox / Opera.

Originally Posted by DNSB

And lest we forget, two different specifications.

Regards,
David

So you are saying this is a good thing overall or a legitimate excuse? Should not some effort be made to make it work seamlessly? Would not ease of use and smooth transitioning work in the developers favour?

Helen

[chrisridd]

Originally Posted by BatmansDouble

I'd love to see a "send to Evernote" option or at least a decent way to export highlights/notes. It would make adding to my commonplace book so much more easier.

I'll second this! Sending to Evernote would be fantastic.