Transferring KEPUB files to Glo

BobC · 06-22-2020, 03:43 PM

Windows 8.1
Calibre 4.19
Kobo Glo 4.21.15015

I have a large library where all the books have been converted to KEPUB using the Kepub Output plug-in and I then upload them to my Kobo Glo WITHOUT using the Extended driver. This has worked fine for years.

Since the update to Calibre 4.19 I noticed that new books I uploaded could not be opened on the Glo which exited with a "Oops! this document couldn't be opened" error. At first I attributed this to a problem in the conversion process, however this is not the case.

I found a book in my library that had been converted some time ago and I had read it on the Glo. I then re-uploaded it using Calibre and found it could not be opened and returned the same error. By doing this I made sure that the problem was not with the conversion process. This suggests that the book is being corrupted in the transfer process.

The book appears to be imported by the Glo into its database when I eject the reader and appears in the listings. It does appear as a <name>.kepub.epub on the Glo and using file tools on my PC I can view the contents of the file by unzipping it and examining the structure.

Any ideas what is going on here ?

BobC

pdurrant · 06-22-2020, 04:27 PM

You might find relevant info in this thread.

BobC · 06-23-2020, 03:57 AM

Thank you for the suggestion but this is clearly a Calibre issue. I have now deleted the book from the Glo and then copied over the kepub using a file manager and renamed it from kepub to kepub.epub and the book opens just fine. The problem only occurs when the book is transferred using Calibre, where I have disabled the Kobo extended driver so it should be copied using the normal kobo driver.

There is no problem with the books themselves it is the process of transferring them using Calibre that is causing the problem.

I thought I had posted this to the Calibre forum but it seems like I made a mistake in this, It might be better if a mod could move it there rather than me re-posting and then being told not to post the same question more than once.

BobC

davidfor · 06-23-2020, 05:42 AM

Yes, it is clearly a calibre issue. Which is why@pdurrant pointed you to a thread discussing the problem you were having. It turned out the problem wasn't actually in the plugin the thread is for, but, it's understandable why people reported it there. Add to it that the extended driver and the Kepub Output plugin share a lot of code, there is a high chance that any problem for one, is also a problem with another.

But, the problem wasn't in either, it was actually in the Kepub Metadata writer plugin. The last release of this plugin was broken when writing the OPF file. It usually ended up as zero bytes. There was another problem in the extended driver and the output plugin that has been fixed. There was a release of all three plugins about two hours before your post that fixed these problems.

BobC · 06-23-2020, 10:25 AM

David,

Thanks for that - I had looked through the Extended Driver thread but it seemed not to be addressing the point I was chasing.

Your timely explanation as to what the issue was has enabled me to do an update on the metadata writer plug-in (I had looked for any plug-in updates before I posted) and it seems I was a couple of hours adrift from finding the fix.

Everything now seems back to normal.

BobC

06-22-2020, 03:43 PM	#1
BobC Guru Posts: 691 Karma: 3026110 Join Date: Dec 2008 Location: Lancashire, U.K. Device: BeBook 1, BeBook Pure, Kobo Glo, (and HD),Energy Sistem EReader Pro +	Transferring KEPUB files to Glo Windows 8.1 Calibre 4.19 Kobo Glo 4.21.15015 I have a large library where all the books have been converted to KEPUB using the Kepub Output plug-in and I then upload them to my Kobo Glo WITHOUT using the Extended driver. This has worked fine for years. Since the update to Calibre 4.19 I noticed that new books I uploaded could not be opened on the Glo which exited with a "Oops! this document couldn't be opened" error. At first I attributed this to a problem in the conversion process, however this is not the case. I found a book in my library that had been converted some time ago and I had read it on the Glo. I then re-uploaded it using Calibre and found it could not be opened and returned the same error. By doing this I made sure that the problem was not with the conversion process. This suggests that the book is being corrupted in the transfer process. The book appears to be imported by the Glo into its database when I eject the reader and appears in the listings. It does appear as a <name>.kepub.epub on the Glo and using file tools on my PC I can view the contents of the file by unzipping it and examining the structure. Any ideas what is going on here ? BobC

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kobo Glo N613 COM ERROR, Kepub only works	bhewson	Kobo Reader	2	07-19-2019 10:11 AM
[Kobo Glo] My kepub folder is empty	Samboee	Devices	1	03-27-2017 08:35 PM
Glo Using the dictionary with non .kepub-books on Glo HD	mlo	Kobo Reader	6	01-10-2016 11:40 AM
kepub files not appearing anywhere	c00ki3	Kobo Reader	3	08-29-2014 06:07 AM
Transferring files....	Jaws51	Kindle Fire	3	08-31-2012 05:35 PM

06-22-2020, 04:27 PM	#2
pdurrant The Grand Mouse 高貴的老鼠 Posts: 73,946 Karma: 315160596 Join Date: Jul 2007 Location: Norfolk, England Device: Kindle Oasis	You might find relevant info in this thread.

06-23-2020, 03:57 AM	#3
BobC Guru Posts: 691 Karma: 3026110 Join Date: Dec 2008 Location: Lancashire, U.K. Device: BeBook 1, BeBook Pure, Kobo Glo, (and HD),Energy Sistem EReader Pro +	Thank you for the suggestion but this is clearly a Calibre issue. I have now deleted the book from the Glo and then copied over the kepub using a file manager and renamed it from kepub to kepub.epub and the book opens just fine. The problem only occurs when the book is transferred using Calibre, where I have disabled the Kobo extended driver so it should be copied using the normal kobo driver. There is no problem with the books themselves it is the process of transferring them using Calibre that is causing the problem. I thought I had posted this to the Calibre forum but it seems like I made a mistake in this, It might be better if a mod could move it there rather than me re-posting and then being told not to post the same question more than once. BobC

06-23-2020, 05:42 AM	#4
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Yes, it is clearly a calibre issue. Which is why@pdurrant pointed you to a thread discussing the problem you were having. It turned out the problem wasn't actually in the plugin the thread is for, but, it's understandable why people reported it there. Add to it that the extended driver and the Kepub Output plugin share a lot of code, there is a high chance that any problem for one, is also a problem with another. But, the problem wasn't in either, it was actually in the Kepub Metadata writer plugin. The last release of this plugin was broken when writing the OPF file. It usually ended up as zero bytes. There was another problem in the extended driver and the output plugin that has been fixed. There was a release of all three plugins about two hours before your post that fixed these problems.

06-23-2020, 10:25 AM	#5
BobC Guru Posts: 691 Karma: 3026110 Join Date: Dec 2008 Location: Lancashire, U.K. Device: BeBook 1, BeBook Pure, Kobo Glo, (and HD),Energy Sistem EReader Pro +	David, Thanks for that - I had looked through the Extended Driver thread but it seemed not to be addressing the point I was chasing. Your timely explanation as to what the issue was has enabled me to do an update on the metadata writer plug-in (I had looked for any plug-in updates before I posted) and it seems I was a couple of hours adrift from finding the fix. Everything now seems back to normal. BobC

Advert

Advert