View Single Post
Old 08-03-2015, 01:08 PM   #1
jgoguen
Generally Awesome Person
jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.jgoguen ought to be getting tired of karma fortunes by now.
 
Posts: 958
Karma: 2082992
Join Date: Jan 2013
Location: San Francisco Bay Area
Device: Kobo Aura, Kindle Paperwhite 2
[Conversion Input] KePub Input

THIS PLUGIN IS BEING INTERMITTENTLY DEVELOPED! FEATURE REQUESTS AND BUG REPORTS MAY TAKE A FEW DAYS TO BE REPLIED TO.

This plugin allows converting KePub files to ePub by removing the special KePub markup. All the credit for actually creating this goes to davidfor, he wrote the code, I'm just including it in the codebase for the other KePub plugins.

You are encouraged to install this plugin as well, to ensure KePub metadata is correctly processed:
Usage

To use this plugin after installing:
  • Select the book(s) you want to convert.
  • Select the EPUB output format
  • Choose your settings
  • Convert the books

Special Notes
  • This plugin requires calibre 0.1.0 or later.
  • Conversion defaults can be set in Preferences -> Output

Installation Directions

Open Preferences -> Plugins -> Get new plugins and install the 'KePub Input' plugin. You may also download the attached zip file and install the plugin manually, then restart calibre as described in the Introduction to Plugins thread.

Known Issues

Not everything works perfectly all the time. Here are some of the issues I know about that are likely to stick around for a while.

Spoiler:
Nothing for now!


Contributing

Decided you want to contribute to the development of this plugin? Awesome! If you want to contribute to the development of this plugin, you have many options:
  • Contribute code, whether for existing bug reports, for new bugs that you found, or for new features that you really want to see implemented. To contribute code, you may fork the repository and send a BitBucket pull request, or you may send me a PM here with a Mercurial patch file.
  • Submit bug reports on Github. Github bug reports are my to-do list for this plugin; any requests anywhere else are likely to get missed and forgotten. Although I'm happy to discuss the plugin here, I may still ask you to create a bug report; this is so I actually remember to investigate your request!
  • Test pre-released code from Github. Between releases, new code is committed to the Github repository and may be installed using directions provided in the README file. Based on your testing, you may submit bug reports, provide feedback, think of new feature requests, or just generally enjoy early access (and not necessarily stable code!) to upcoming versions of the plugin.
  • Translate the plugin on the plugin's Launchpad Translations page.

Submitting Bugs
Found an issue? Have a new feature request? Great, I want to hear from you! Go to the Github issue tracker and submit a new bug report. To save us all time, please make sure to include the following details:
  • What version of calibre are you running? If this is not the latest version, you will likely be asked to upgrade and confirm that the bug still exists.
  • What version of the plugin are you using? If this is not the latest version, you will likely be asked to upgrade and confirm that the bug still exists.
  • Are you able to send me a book that demonstrates the problem? Please be aware of the directions provided when submitting a new bug which specify not to upload a book to the bug report!
  • The calibre debug log showing the issue, where possible
    • To get the calibre debug log, select Preferences -> Restart in debug mode and reproduce the issue. The calibre debug log will be displayed shortly after closing calibre.

Although I'm generally perfectly happy to discuss possible issues here, any issues sent to me through any means other than the Github issue tracker (including email, PM, etc.) may be silently ignored. This is not because I don't care! It's because I have a terrible memory, the Github issue tracker is my "to-do list" for this plugin, and there's been instances where I've seen a post or PM here and promptly forgotten all about it until I happened to stumble across the post again later. If you aren't sure if you have an issue, feel free to post here and we can work together to decide if you need to make a new Github issue or not. If you are sure you have an issue, or if you have an error or exception from calibre, post a new issue. It isn't necessary to post here when you make a new issue, I get notified of all new bugs and I check the list regularly. The worst that could possibly happen on Github is the same that could happen here: I'll tell you that it's not a bug and you'll have the opportunity to convince me otherwise!

README file
The current version is always here on Github.

Version History

Spoiler:

Version 3.0.0 - 2017-10-30
Imported to BitBucket, made small bugfix and formatting changes, new translations
Version 2.7.3 - 2016-07-08
Support calibre changes for ePub 3
Version 2.7.1 - 2016-06-26
Spanish (es_ES) translation update
Version 2.7.0 - 2016-06-25
Code cleanup from new driver code, no-op functionally
Version 2.5.3 - 2015-09-30
Fix problem preventing the cover image from being set properly with unusually-set OPF IDs
Version 2.5.1 - 2015-08-05
Fix problems with file names not being converted properly
Version 2.5.0 - 2015-08-03
Initial release. Thanks davidfor!
Attached Files
File Type: zip KePub Input.zip (25.7 KB, 40980 views)

Last edited by jgoguen; 08-13-2019 at 02:09 AM.
jgoguen is offline   Reply With Quote