View Single Post
Old 04-26-2021, 05:18 PM   #17
Uncle Robin
Diligent dilettante
Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.Uncle Robin ought to be getting tired of karma fortunes by now.
 
Uncle Robin's Avatar
 
Posts: 3,661
Karma: 52758936
Join Date: Sep 2019
Location: in my mind
Device: Kobo Sage; Kobo Libra Colour
Quote:
Originally Posted by NiLuJe View Post
With Calibre, assuming a common sane for-Kobo setup, chances are you won't ever get Nickel to use the book's own metadata, @davidfor's excellent Kobo driver handles all of that for you straight from Calibre's own metadata, injecting all of it directly in Nickel's db .

(Which means the situation I explained above, where the on-device-book's OPF might be horribly (or slightly ;p) broken, would be silently fixed by the driver, as long as Nickel managed to import it in the first place).

I don't understand how it works, all I know is that I sent a dozen or so books over using "Send to device" the same way I always do, and this one (and only this one) had that message in KOReader, while working fine in Nickel. I was very slightly curious at first, hence the initial post here, but now it's amusing that I'm at risk of having spent more time in this thread than it took me to read the book.
Uncle Robin is offline   Reply With Quote