Kobo research team is asking for feedback on Reddit

[JSWolf]

Originally Posted by ghira

It didn't even occur to me to wish for pdfs to work better. Even wishing can only achieve so much.

Too bad it didn't occur to ask for a faster processor and more powerful battery.

[Rbneader]

Took the survey.

Honestly, at this point I think my next ereader is a Boox. They seem like the only decent option that still has a microSD card slot, and I'm not interested in any ereader that makes me have to swap files around. It's too bad because I really like my Kobo.

[ghira]

Originally Posted by JSWolf

Too bad it didn't occur to ask for a faster processor and more powerful battery.

Honestly these aren't things that have seemed like problems to me. Painfully bad formulae in maths books, yes.

[JSWolf]

Originally Posted by ghira

Honestly these aren't things that have seemed like problems to me. Painfully bad formulae in maths books, yes.

What we should have asked for is the latest version of RMSDK. That would solve your math problems with ePub.

[DNSB]

Originally Posted by JSWolf

What we should have asked for is the latest version of RMSDK. That would solve your math problems with ePub.

Does the latest version of RMSDK contain the fonts required to display MathML? I do find that using kepub with a secondary font helps but ePub on a Kobo does not support a secondary font.

[compurandom]

Originally Posted by twowheels

I fail to see how having to add another step and another device to the process makes things better.

I totally understand the frustration of an extra step. I have some things that generate epub files, and I make sure that it inserts correct metadata in them so I don't need the extra step of re-fixing it in calibre.

The kobo UI is all based on metadata in the document.
If your metadata is blank, then kobo should be using the filename anyway (does it?)
If your metadata is wrong, I don't see any solution other than using something like calibre to fix it.

[DNSB]

Originally Posted by compurandom

The kobo UI is all based on metadata in the document.
If your metadata is blank, then kobo should be using the filename anyway (does it?)

No, the metadata is used. If the metadata is screwed up, the results are less than useful. GIGO comes to mind. Please note that the main metadata used by Kobo is part of the Dublin Core metadata. If it is screwed up, epubcheck is not going to be happy with your epub and no publisher that I am aware of will accept it.

Originally Posted by compurandom

If your metadata is wrong, I don't see any solution other than using something like calibre to fix it.

I've used Sigil's metadata editor to fix up some weird issues and at times, have edited the .opf file to correct issues from &^%*)@ software that generates invalid OPF entries (some software authors simply know better than the people generating the standards what is needed and not needed).

[ghira]

Originally Posted by DNSB

Does the latest version of RMSDK contain the fonts required to display MathML?

I don't know the answer to that but the stix math font that appeared on my Sage a few versions ago has made some previously useless epubs readable.

[JSWolf]

Originally Posted by DNSB

Does the latest version of RMSDK contain the fonts required to display MathML? I do find that using kepub with a secondary font helps but ePub on a Kobo does not support a secondary font.

Yes, ADE does support MathML.

https://www.adobe.com/solutions/eboo...ase-notes.html

Changes in ADE 4.0.3

• Support is now available for navigational items like Landmarks, Pages list, Images list and Tables list.
• MathML support is now available for ADE on Windows.
• Audio and video content in the eBooks can be progressively downloaded on all platforms.
• Erasing the authorization of this computer adds one more to your number of allowed authorizations.
• An intuitive popup box for controlling media overlays.
• The Scrubber bar can be used to navigate to pages across eBooks.
• Full support for EPUB’s Fragment Identifier.
• Full support for all input types in eBooks.

[JSWolf]

Originally Posted by compurandom

I totally understand the frustration of an extra step. I have some things that generate epub files, and I make sure that it inserts correct metadata in them so I don't need the extra step of re-fixing it in calibre.

The kobo UI is all based on metadata in the document.
If your metadata is blank, then kobo should be using the filename anyway (does it?)
If your metadata is wrong, I don't see any solution other than using something like calibre to fix it.

If your metadata is blank that's something you should fix before side loading. I've never seen a purchased or borrowed eBook with blank metadata. Wrong, I have seen. But with a Kobo, you can fix it in calibre and send the fixed metadata to the Kobo.

[rantanplan]

Originally Posted by JSWolf

Too bad it didn't occur to ask for a faster processor and more powerful battery.

Why would you want to tell them how to solve this problem? Especially in a way that is not backwards compatible? The correct approach in software development is to tell them which problem to solve and then their product managers can come up with a useful solution themselves.


Gesendet von iPhone mit Tapatalk

[JSWolf]

Originally Posted by rantanplan

Why would you want to tell them how to solve this problem? Especially in a way that is not backwards compatible? The correct approach in software development is to tell them which problem to solve and then their product managers can come up with a useful solution themselves.


Gesendet von iPhone mit Tapatalk

How is a faster processor and more powerful battery not backward compatible?

[compurandom]

Originally Posted by JSWolf

If your metadata is blank that's something you should fix before side loading. I've never seen a purchased or borrowed eBook with blank metadata. Wrong, I have seen. But with a Kobo, you can fix it in calibre and send the fixed metadata to the Kobo.

Not just talking about epubs, but also PDFs.

I've just seen so many PDFs that were well formatted but with either blank metadata or title set to "Microsoft Word Document" or some equally stupid default for title and author.

[lkmiller]

Originally Posted by JSWolf

I'd prefer buttons on no side. They would make it such that the bezel on the Libra 2 could be smaller.

I like big bezels and I cannot lie.

[ghira]

I generally don't use buttons, but don't really care much if they are there or not. If other people like them, well, fine. My Aura One didn't have them, and I was ok with that. My Sage does, and I mostly ignore them. If the buttons existing helps sell enough that the model exists vs not existing, ok by me.