kepubify - A standalone tool to convert ePubs into Kobo ePubs

[geek1011]

Originally Posted by Akbar

My Aura One could finally see the file .kepub converted using the latest version. I prefer to use this software since I get "error connecting device" message in Calibre from time to time. Thank you.

No problem!

Feel free to ask me if you want more documentation, features, or have any problems!

[geek1011]

I have redesigned the site and improved the documentation: https://geek1011.github.io/kepubify/

[JIPG-reader]

Thank you for your program. I tried it before without success, but now it works well in windows
I have converted several epubs smoothly (and very quick, by the way ), and they show perfect in the KOBO H2O Ed2!

[Semwize]

I tried to convert the entire Books folder (> 600 books). It took about 10 minutes

[geek1011]

Originally Posted by Semwize

I tried to convert the entire Books folder (> 600 books). It took about 10 minutes

Yes. My benchmarks were about 1200 various books in 468 secs (about 2.5 books per second. With calibre, it took 4 hours, which is about 4 books a minute (.06 books a second). If I only used my smaller books, kepubify was about the same, and calibre was about 3x faster (.19 books a second).

[geek1011]

Originally Posted by Semwize

I tried to convert the entire Books folder (> 600 books). It took about 10 minutes

And for your PM about pop up footnotes, they only work in Epub 3 books, with the right class on the link.

[Question Mark]

Works very well. Many thanks.

[jackie_w]

Originally Posted by geek1011

And for your PM about pop up footnotes, they only work in Epub 3 books, with the right class on the link.

Obviously I don't know what was in your PM but pop-up footnotes are supposed to work OK in all kepubs using standard <a> tags even if the source epub is epub2. It became a problem for some kepubs in fw 4.0.7523. See this short discussion thread.

The source epub can be fixed quite easily using the calibre Editor (one book at a time) but, as you're not accessing calibre functions for various reasons, you may choose to incorporate your own "auto-fix" during the format-shift to kepub once you understand the underlying problem.

Caveat, any auto-fix would probably slow down the kepub creation process.

[geek1011]

Originally Posted by jackie_w

Obviously I don't know what was in your PM but pop-up footnotes are supposed to work OK in all kepubs using standard <a> tags even if the source epub is epub2. It became a problem for some kepubs in fw 4.0.7523. See this short discussion thread.

The source epub can be fixed quite easily using the calibre Editor (one book at a time) but, as you're not accessing calibre functions for various reasons, you may choose to incorporate your own "auto-fix" during the format-shift to kepub once you understand the underlying problem.

Caveat, any auto-fix would probably slow down the kepub creation process.

So I guess I misunderstood that part. I had a look at the thread you posted, and it seems to make sense. I will test it, and if it works, I'll see what I can do about incorporating the process into kepubify. I think I'll be able to do it with no noticeable speed decrease.

[geek1011]

I've released a new version. There are no changes you should notice, except a very small speed increase. This version was mostly about cleaning up the code, and rewriting the hacky parts.

[davidfor]

Originally Posted by geek1011

Yes. My benchmarks were about 1200 various books in 468 secs (about 2.5 books per second. With calibre, it took 4 hours, which is about 4 books a minute (.06 books a second). If I only used my smaller books, kepubify was about the same, and calibre was about 3x faster (.19 books a second).

For curiosity, was the calibre benchmark done with the conversion or the extended driver? I rarely convert/send more than a couple of books at a time, so the time taken has never bothered me. But, I would expect the driver method to be faster than a full conversion. The driver method also includes copying the result to the device. Did your test include that for kepubify?

[geek1011]

Originally Posted by davidfor

For curiosity, was the calibre benchmark done with the conversion or the extended driver? I rarely convert/send more than a couple of books at a time, so the time taken has never bothered me. But, I would expect the driver method to be faster than a full conversion. The driver method also includes copying the result to the device. Did your test include that for kepubify?

The test did not include copying to the device. I used the conversion method.

I have also tried using the new kepubify batch conversion to send directly to the device and compared it to the driver. kepubify is about half the speed, and calibre is a bit more than twice the speed. It took calibre 1.5 hours, and it took kepubify 910 seconds.

[JIPG-reader]

Originally Posted by geek1011

I've released a new version. There are no changes you should notice, except a very small speed increase. This version was mostly about cleaning up the code, and rewriting the hacky parts.

Is it possible in the windows version to have the conversion log readable when it finishes? (e.g. up to a key is pressed, the DOS window closes so quick ...!)

[geek1011]

Originally Posted by JIPG-reader

Is it possible in the windows version to have the conversion log readable when it finishes? (e.g. up to a key is pressed, the DOS window closes so quick ...!)

I already have a 0.5s delay. That should be enough time to take a screenshot.

Alternatively, you can start kepubify from a command prompt window.

[Semwize]

geek1011, will you add pop-up footnotes?