Run the GUI with a debug console, logging to the specified path. Debug output is printed to stdout and stderr. Examples: calibre-debug -export-all-calibre-data # for interactive use calibre-debug -export-all-calibre-data /path/to/empty/export/folder /path/to/library/folder1 /path/to/library2 calibre-debug -export-all-calibre-data /export/folder all # export all known libraries -fix-multiprocessing ¶

The special keyword 'all ' can be used to export all libraries. Use absolute paths for the export folder and libraries. You can also specify them as command line arguments to skip the questions. Normally, you will be asked for the export folder and the libraries to export. export-all-calibre-data ¶Įxport all calibre data (books/settings/plugins). Works with EPUB, AZW3, HTMLZ and DOCX files. Usage: -x file.epub output_dir Exports the book as a collection of HTML files and metadata, which you can edit using standard HTML editing tools. explode-book, -x ¶Įxplode the book into the specified folder. Launch the calibre 'Edit book ' tool in debug mode. For example: calibre-debug -diff file1 file2 -edit-book ¶ default-programs = (register|unregister) -diff ¶ (Un)register calibre from Windows Default Programs. debug-device-driver, -d ¶ĭebug device detection -default-programs ¶ py file), by specifying the path to the py file containing the plugin code. For example: “/some path/with spaces” ¶ -add-simple-plugin ¶Īdd a simple plugin (i.e. Whenever you pass arguments to calibre-debug that have spaces in them, enclose the arguments in quotation marks.

Calibre 6.25.0 for windows instal free