Kobo Bug thread

[Lucas Malor]

Well, that's why I added it as ADE bug

[DNSB]

Originally Posted by bobb40

I've attached it, and added a comment saying so after all other text. I don't understand the ADE/Access discussion which assigns this bug to ADE; if comments of my original post confuse the issue, tell me what to alter or remove. Thanks.

The Kobo ereaders use two different renderers to display ebooks. If the ebook filetype is .kepub.epub, it will be opened with the ACCESS renderer, if the filetype is .epub, it will be opened with the Reader Mobile renderer.

Reader Mobile is an epub 2.01 compliant renderer from a code base supplied by Adobe who also are responsible for ADE. Many of the issues seen with the Kobo's RMSDK renderer also appear when the ebook is opened in ADE. The major reason I think that Kobo is still using the RMSDK is for compatibility with Adobe's ADEPT DRM management allowing borrowing books from a library and purchasing books from multiple vendors.

NetFront BookReader is an epub 3.0 compliant renderer supplied by ACCESS. Kobo uses it with their own proprietary DRM. It works quite well with epub 3 content from other vendors though Kobo does not officially support such usage. A Kobo produced .kepub.epub has several non-standard items but simply renaming an .epub to .kepub.epub will allow using the ACCESS renderer which is handy when testing.

Both renderers have bugs but different bugs. In the case of your test book, the RMSDK renderer has severe issues with displaying the pages while the ACCESS renderer displayed the pages more or less properly.

Regards,
David

[Lucas Malor]

Originally Posted by DNSB

The major reason I think that Kobo is still using the RMSDK is for compatibility with Adobe's ADEPT DRM management allowing borrowing books from a library and purchasing books from multiple vendors.

Well, I don't know RDMSK, but in theory Kobo could use ADE only with DRM epubs. Or let us choice.

[Lucas Malor]

Anyway, I tested bugs that affects wrapping. See the attached testcase.

The first two bugs are confirmed as ADE bugs. The last bug seems to happen only with PUBLUS (the kepub reader from Access). We can't know for sure, since there are bugs with the epub renderer that doesn't happen with ADE on PC. Since PUBLUS is not released publicly, I will not add a section for PUBLUS bugs.

[DNSB]

Originally Posted by Lucas Malor

Well, I don't know RDMSK, but in theory Kobo could use ADE only with DRM epubs. Or let us choice.

Reader Mobile Software Development Kit. It's what Kobo uses to read epubs on their ereaders. If you look at the About under Settings, you'll see something like "The Kobo (model) contains Reader(r) Mobile software under license from Adobe etc.

That's why I use ADE 1.7.2 on a PC or Mac to test bugs since the code base is pretty close so a bug on the Kobo shows up as the same bug on the PC 95% of the time.

Regards,
David

[Nick_1964]

Originally Posted by Lucas Malor

Well, that's why I added it as ADE bug

The two bugs I mentioned with the <font>a</font> and <span>a</span> tags what will cause a faulty linebreak when at the end of a line,are in the lastest ADE version to ! ( 2.06 )

I put 3 screenshots as attachments, red underlined are words that should be displayed as one word on a new line,but are broken at the end of the line.

[Lucas Malor]

The latest version of ADE is 3.0.something, and as I wrote above I can't reproduce the bug with it. I suppose Kobo is using an old SDK.

[Nick_1964]

Originally Posted by Lucas Malor

The latest version of ADE is 3.0.something, and as I wrote above I can't reproduce the bug with it. I suppose Kobo is using an old SDK.

Then I keep my current version of ADE, because in Sigil and Calibre the pages are displayed okay, even as in Sony prst-3, so I have something to test.
I can try to convert the book to kepub,and see whats happened..
I think myself that KOBO will not upgrade their old SDK only for sloppy books, switching to a more updated SDK will cost them extra money.

/edit converted the book with the calibre plugin epub-kepub and the wrong displayed linebreaks are gone, don't know of a kepub editor so can't really see whats in it.
I didn't renamed it,really converted it.
So definetely a old SDK for epubs.

[Lucas Malor]

Check one of my previous posts, I already created a kepub testcase.

[trinity1]

went through the last posts and I didn't see a problem I have after updating my Glo to 3.2.0 fw: my collections are totally messed up!
Ok, this is what I did it:
deleted all epubs from memory (internal and external)
hard reset (due to the fact that 3.2.0 downloaded from mobileread made my Glo really slow and not responsive to touch)
setup with kobodesktop, sync
connected Glo with Calibre (1.32)
all epubs sent to Glo with Calibre (30-40 epubs each session... It took a bit - I have 630 epubs...). Calibre touch extended plugin is NOT set to create collection folders, because I want to create them by myself.
Creation of collections onto Glo.
The order was supposed to be by alphabetical order ("Carsten Stroud BEFORE Isaac Asimov; "Charles E. Maine" BEFORE, "Roger Zelazny", etc...). Actually, I have something like "Isaac Asimov", "Carsten Stroud", "Roger Zelazny", "Charles E. Maine", and I can't recognise any order.
Is it fixable, somehow?

[Lucas Malor]

It's not a Kobo bug, you have to ask to the Calibre subforum. Probably you have to only change the "Author sort" metadata.

[trinity1]

Originally Posted by Lucas Malor

It's not a Kobo bug, you have to ask to the Calibre subforum. Probably you have to only change the "Author sort" metadata.

not sure: I'm talking about collections created DIRECTLY into kobo. Furthermore, before upgrading to 3.2.0, I followed same procedure and the collections were alphabetically ordered. I guess it has nothing to do with Calibre, since (as I said) I set up the plugin in order not to create (nor to delete) any collection folder.

... and the author metadata is coherent with authors order as I want.

Plus, the order of epubs into my Glo (when I change it, by author, by title, etc.) is ok.

[davidfor]

Originally Posted by trinity1

not sure: I'm talking about collections created DIRECTLY into kobo. Furthermore, before upgrading to 3.2.0, I followed same procedure and the collections were alphabetically ordered. I guess it has nothing to do with Calibre, since (as I said) I set up the plugin in order not to create (nor to delete) any collection folder.

... and the author metadata is coherent with authors order as I want.

Plus, the order of epubs into my Glo (when I change it, by author, by title, etc.) is ok.

The collections list should have a sort option at the top of the list. But, there is a bug and it is missing on some devices. See https://www.mobileread.com/forums/sho....php?p=2774929.

[trinity1]

Originally Posted by davidfor

The collections list should have a sort option at the top of the list. But, there is a bug and it is missing on some devices. See https://www.mobileread.com/forums/sho....php?p=2774929.

see that. I'm playing with my eReader.conf but I cannot make the trick working. As far as I could read, there is not any line concerning the bookshelf listing, and I tried to insert it into different positions into the file, but it lloks like it doesn't work for me. Probably I have to revert back to 3.1.1 (really annoying)....
BTW thanks for your help

[davidfor]

Originally Posted by trinity1

see that. I'm playing with my eReader.conf but I cannot make the trick working. As far as I could read, there is not any line concerning the bookshelf listing, and I tried to insert it into different positions into the file, but it lloks like it doesn't work for me. Probably I have to revert back to 3.1.1 (really annoying)....
BTW thanks for your help

All you need to do is add the line "LastLibrarySorter_shelfList_=sortByShelfName( )" into the "ApplicationPreferences" section of the file. Putting it at the end of the section, should do it. Make sure you are using an Unix line end aware editor. It shouldn't be needed, but a restart before or afterwards might help.