Question about how kobo touch driver works

hleo12 · 07-24-2014, 02:22 PM

I just have some general questions. (And I beg you guys, I can understand some technical terms, but if it's about some code or such, then my brain won't be able to handle it.)

Okay, here we go...

Earlier, I converted two PDFs, using Calibre, to ePubs. After messing around with Sigil to fix those broken lines, I saved them. Then, when I sent them to my device (I just click on Send to Device since it's configured to only send ePubs and KePubs.

The Touch Extended Driver is enabled, along with the option to automatically output the file to kepub.epub format.

The plugin has worked marvelously everytime I send books to my Glo. But this time, it only converted one and sent the other as a plain old ePub.

I tried just sending the failed one and it's still sent as an ePub.

I also tried sending a random ePub I found, just in case the plugin has gone bad, but it converted that book.

What I did was "manually" convert the book to kepub and had to press Send Specific File Type To just to have a kepub output.

I know for a fact that it's with the book, and not with the plugin, because it only affected that particular book.

I tried converting the PDF multiple times but still no go.

So, thegeneral question is: What could've have possibly caused this? Or, what are the common causes for a book not to be automatically converted?

I don't know if the book is corrupted, but it works fine with Sigil and Calibre's built-in editor.

It really made my head hurt earlier...

I hope someone can shed a light to this...

Thanks,
Harold

davidfor · 07-24-2014, 08:29 PM

When the KoboTouchExtended driver does not send a book as a kepub, it means that there is a problem with the book. It could be DRM or something unusual about the structure of the code in the book. As you have converted from PDF, it won't be DRM.

The problem with the book that the driver is seeing might not be something that affects other uses. It might be something the driver hasn't been coded for or some sort of strange characters in the book. But, there should be errors when this happens. There are a couple of options in the driver to keep sending the books if the conversion fails. I assume you have these turned on. Turning them off should show more information.

Other than that, I suggest looking at the thread for the driver. The first post has any limitations on the driver and how to report bugs.

hleo12 · 07-25-2014, 12:52 AM

Quote:

Originally Posted by davidfor

When the KoboTouchExtended driver does not send a book as a kepub, it means that there is a problem with the book. It could be DRM or something unusual about the structure of the code in the book. As you have converted from PDF, it won't be DRM.

The problem with the book that the driver is seeing might not be something that affects other uses. It might be something the driver hasn't been coded for or some sort of strange characters in the book. But, there should be errors when this happens. There are a couple of options in the driver to keep sending the books if the conversion fails. I assume you have these turned on. Turning them off should show more information.

Other than that, I suggest looking at the thread for the driver. The first post has any limitations on the driver and how to report bugs.

Thanks! I'll try it later.

07-24-2014, 02:22 PM	#1
hleo12 Guru Posts: 631 Karma: 5078890 Join Date: Feb 2014 Device: Kobo Glo (deceased), Kindle 4th, Kindle Basic 10th Generation	Question about how kobo touch driver works I just have some general questions. (And I beg you guys, I can understand some technical terms, but if it's about some code or such, then my brain won't be able to handle it.) Okay, here we go... Earlier, I converted two PDFs, using Calibre, to ePubs. After messing around with Sigil to fix those broken lines, I saved them. Then, when I sent them to my device (I just click on Send to Device since it's configured to only send ePubs and KePubs. The Touch Extended Driver is enabled, along with the option to automatically output the file to kepub.epub format. The plugin has worked marvelously everytime I send books to my Glo. But this time, it only converted one and sent the other as a plain old ePub. I tried just sending the failed one and it's still sent as an ePub. I also tried sending a random ePub I found, just in case the plugin has gone bad, but it converted that book. What I did was "manually" convert the book to kepub and had to press Send Specific File Type To just to have a kepub output. I know for a fact that it's with the book, and not with the plugin, because it only affected that particular book. I tried converting the PDF multiple times but still no go. So, thegeneral question is: What could've have possibly caused this? Or, what are the common causes for a book not to be automatically converted? I don't know if the book is corrupted, but it works fine with Sigil and Calibre's built-in editor. It really made my head hurt earlier... I hope someone can shed a light to this... Thanks, Harold

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Device Plugin] Kobo Touch Extended Driver	jgoguen	Plugins	2962	04-09-2024 12:14 AM
Touch Hacking Kobo Touch suspend usb network eink driver	tonyv	Kobo Developer's Corner	25	01-22-2014 09:04 AM
Hacking Kobo Touch suspend usb network eink driver	tonyv	Kobo Reader	0	06-26-2012 02:27 PM
Touch Kobo touch + Dropbox. It works!	4ll4n	Kobo Reader	14	05-05-2012 04:10 PM
Touch Updates to Calibre Kobo driver for Touch	timlegge	Kobo Reader	20	07-22-2011 07:05 AM

07-24-2014, 08:29 PM	#2
davidfor Grand Sorcerer Posts: 24,907 Karma: 47303748 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	When the KoboTouchExtended driver does not send a book as a kepub, it means that there is a problem with the book. It could be DRM or something unusual about the structure of the code in the book. As you have converted from PDF, it won't be DRM. The problem with the book that the driver is seeing might not be something that affects other uses. It might be something the driver hasn't been coded for or some sort of strange characters in the book. But, there should be errors when this happens. There are a couple of options in the driver to keep sending the books if the conversion fails. I assume you have these turned on. Turning them off should show more information. Other than that, I suggest looking at the thread for the driver. The first post has any limitations on the driver and how to report bugs.

Advert