Calibre Manual
Calibre Manual
Calibre Manual
Release 4.21.0
Kovid Goyal
4 E-book conversion 61
5 Editing e-books 79
10 Tutorials 151
15 Glossary 341
Index 345
i
ii
calibre User Manual, Release 4.21.0
calibre is an e-book library manager. It can view, convert and catalog e-books in most of the major e-book formats.
It can also talk to many e-book reader devices. It can go out to the Internet and fetch metadata for your books. It can
download newspapers and convert them into e-books for convenient reading. It is cross platform, running on Linux,
Windows and macOS.
You’ve just started calibre. What do you do now? Before calibre can do anything with your e-books, it first has to
know about them. Drag and drop a few e-book files into calibre, or click the “Add books” button and browse for the
e-books you want to work with. Once you’ve added the books, they will show up in the main view looking something
like this:
Once you’ve admired the list of books you just added to your heart’s content, you’ll probably want to read one. In
order to do that you’ll have to convert the book to a format your reader understands. When first running calibre, the
Welcome wizard starts and will set up calibre for your reader device. Conversion is a breeze. Just select the book you
want to convert then click the “Convert books” button. Ignore all the options for now and click “OK”. The little icon
in the bottom right corner will start spinning. Once it’s finished spinning, your converted book is ready. Click the
“View” button to read the book.
If you want to read the book on your reader, connect it to the computer, wait till calibre detects it (10-20 seconds)
and then click the “Send to device” button. Once the icon stops spinning again, disconnect your reader and read
away! If you didn’t convert the book in the previous step, calibre will auto convert it to the format your reader device
understands.
To get started with more advanced usage, you should read about The Graphical User Interface (page ??). For even
more power and versatility, learn the Command Line Interface (page ??). You will find the list of Frequently Asked
Questions (page ??) useful as well.
If you have more questions, or want to discuss calibre with other users or ask for help with specific things, there are
forums and other help resources available1 .
Sections
1 https://calibre-ebook.com/help
Contents 1
calibre User Manual, Release 4.21.0
2 Contents
CHAPTER 1
The Graphical User Interface (GUI) provides access to all library management and e-book format conversion features.
The basic workflow for using calibre is to first add books to the library from your hard disk. calibre will automatically
try to read metadata from the books and add them to its internal database. Once they are in the database, you can
perform various Actions (page 4) on them that include conversion from one format to another, transfer to the reading
device, viewing on your computer, and editing metadata. The latter includes modifying the cover, description, and tags
among other details. Note that calibre creates copies of the files you add to it. Your original files are left untouched.
The interface is divided into various sections:
• Actions (page 4)
• Preferences (page 10)
• Catalogs (page 10)
• Search & sort (page 11)
• The search interface (page 11)
• Saving searches (page 14)
• Virtual libraries (page 14)
• Guessing metadata from file names (page 15)
• Book details (page 16)
• Tag browser (page 18)
• Cover grid (page 20)
• Cover browser (page 21)
• Quickview (page 21)
• Jobs (page 22)
• Keyboard shortcuts (page 22)
3
calibre User Manual, Release 4.21.0
1.1 Actions
The actions toolbar provides convenient shortcuts to commonly used actions. If you right-click the buttons, you can
perform variations on the default action. Please note that the actions toolbar will look slightly different depending on
whether you have an e-book reader attached to your computer.
The Add books action has seven variations accessed by doing a right-click on the button.
1. Add books from a single directory: Opens a file chooser dialog and allows you to specify which books in a
directory should be added. This action is context sensitive, i.e. it depends on which catalog (page 10) you have
selected. If you have selected the Library, books will be added to the library. If you have selected the e-book
reader device, the books will be uploaded to the device, and so on.
2. Add books from directories and sub-directories: Allows you to choose a directory. The directory and all its
sub-directories are scanned recursively, and any e-books found are added to the library. You can choose whether
to have calibre add all files present in a single directory to a single book record or multiple book records. calibre
assumes that each directory contains a single book. All e-book files in a directory are assumed to be the same
book in different formats. This action is the inverse of the Save to disk (page 8) action, i.e. you can Save to disk,
delete the books and re-add them in single book per directory mode, with no lost information except for the date
(this assumes you have not changed any of the setting for the Save to disk action).
3. Add multiple books from archive (ZIP/RAR): Allows you to add multiple e-books that are stored inside the
selected ZIP or RAR files. It is a convenient shortcut that avoids having to first unzip the archive and then add
the books via one of the above two options.
4. Add empty book (Book Entry with no formats): Allows you to create a blank book record. This can be used
to then manually fill out the information about a book that you may not have yet in your collection.
5. Add from ISBN: Allows you to add one or more books by entering their ISBNs.
6. Add files to selected book records: Allows you to add or update the files associated with an existing book in
your library.
7. Add an empty file to selected book records: Allows you to add an empty file of the specified format to the
selected book records.
The Add books action can read metadata from a wide variety of e-book formats. In addition, it tries to guess metadata
from the filename. See the Guessing metadata from file names (page 15) section, to learn how to configure this.
To add an additional format for an existing book you can do any of three things:
1. Drag and drop the file onto the Book details panel on the right side of the main window
2. Right click the Add books button and choose Add files to selected books.
3. Click the Add books button in the top right area of the Edit metadata dialog, accessed by the Edit metadata
(page 5) action.
The Edit metadata action has four variations which can be accessed by doing a right-click on
the button.
1. Edit metadata individually: Allows you to edit the metadata of books one-by-one with the option of fetching
metadata, including covers, from the Internet. It also allows you to add or remove particular e-book formats
from a book.
2. Edit metadata in bulk: Allows you to edit common metadata fields for large numbers of books simultaneously.
It operates on all the books you have selected in the Library view (page 11).
3. Download metadata and covers: Downloads metadata and covers (if available) for the books that are selected
in the book list.
4. Merge book records: Gives you the capability of merging the metadata and formats of two or more book
records. You can choose to either delete or keep the records that were not clicked first.
For more details see Editing e-book metadata (page 125).
E-books can be converted from a number of formats into whatever format your e-book reader
prefers. Many e-books available for purchase will be protected by Digital Rights Management (page ??) (DRM)
1.1. Actions 5
calibre User Manual, Release 4.21.0
technology. calibre will not convert these e-books. It is easy to remove the DRM from many formats, but as this may
be illegal, you will have to find tools to liberate your books yourself and then use calibre to convert them.
For most people, conversion should be a simple one-click affair. If you want to learn more about the conversion
process, see E-book conversion (page 61).
The Convert books action has three variations, accessed by doing a right-click on the button.
1. Convert individually: Allows you to specify conversion options to customize the conversion of each selected
e-book.
2. Bulk convert: Allows you to specify options only once to convert a number of e-books in bulk.
3. Create a catalog of the books in your calibre library: Allows you to generate a complete listing of the books
in your library, including all metadata, in several formats such as XML, CSV, BiBTeX, EPUB and MOBI. The
catalog will contain all the books currently showing in the library view. This allows you to use the search
features to limit the books to be catalogued. In addition, if you select multiple books using the mouse, only
those books will be added to the catalog. If you generate the catalog in an e-book format such as EPUB, MOBI
or AZW3, the next time you connect your e-book reader the catalog will be automatically sent to the device.
For more information on how catalogs work, read the Creating AZW3 • EPUB • MOBI catalogs (page 220).
1.1.4 View
The View action displays the book in an e-book viewer program. calibre has a built-in viewer for
many e-book formats. For other formats it uses the default operating system application. You can configure which
formats should open with the internal viewer via Preferences→Interface→Behavior. If a book has more than one
format, you can view a particular format by doing a right-click on the button.
The Send to device action has eight variations, accessed by doing a right-click on the button.
1. Send to main memory: The selected books are transferred to the main memory of the e-book reader.
2. Send to card (A): The selected books are transferred to the storage card (A) on the e-book reader.
3. Send to card (B): The selected books are transferred to the storage card (B) on the e-book reader.
4. Send specific format to: The selected books are transferred to the selected storage location on the device, in
the format that you specify.
5. Eject device: Detaches the device from calibre.
6. Set default send to device action: Allows you to specify which of the options, 1 through 5 above or 7 below,
will be the default action when you click the main button.
7. Send and delete from library: The selected books are transferred to the selected storage location on the device
and then deleted from the Library.
8. Fetch Annotations (experimental): Transfers annotations you may have made on an e-book on your device to
the comments metadata of the book in the calibre library.
You can control the file name and folder structure of files sent to the device by setting up a template in
Preferences→Import/export→Sending books to devices. Also see The calibre template language (page 159).
The Fetch news action downloads news from various websites and converts it into an e-book that
can be read on your e-book reader. Normally, the newly created e-book is added to your e-book library, but if an
e-book reader is connected at the time the download finishes, the news is also uploaded to the reader automatically.
The Fetch news action uses simple recipes (10-15 lines of code) for each news site. To learn how to create recipes for
your own news sources, see Adding your favorite news website (page 25).
The Fetch news action has three variations, accessed by doing a right-click on the button.
1. Schedule news download: Allows you to schedule the download of your selected news sources from a list of
hundreds available. Scheduling can be set individually for each news source you select and the scheduling is
flexible allowing you to select specific days of the week or a frequency of days between downloads.
2. Add a custom news source: Allows you to create a simple recipe for downloading news from a custom news
site that you wish to access. Creating the recipe can be as simple as specifying an RSS news feed URL, or you
can be more prescriptive by creating Python-based code for the task. For more information see Adding your
favorite news website (page 25).
3. Download all scheduled news sources: Causes calibre to immediately begin downloading all news sources that
you have scheduled.
1.1.7 Library
The Library action allows you to create, switch between, rename or remove a Library. calibre allows
you to create as many libraries as you wish. You could, for instance, create a fiction library, a non-fiction library, a
foreign language library, a project library, or any structure that suits your needs. Libraries are the highest organizational
structure within calibre. Each library has its own set of books, tags, categories and base storage location.
1. Switch/create library. . . : Allows you to; a) connect to a pre-existing calibre library at another location, b)
create an empty library at a new location or, c) move the current library to a newly specified location.
2. Quick switch: Allows you to switch between libraries that have been registered or created within calibre.
3. Rename library: Allows you to rename a Library.
4. Pick a random book: Chooses a random book in the library for you
1.1. Actions 7
calibre User Manual, Release 4.21.0
Note: Metadata about your e-books, e.g. title, author, and tags, is stored in a single file in your calibre library
folder called metadata.db. If this file gets corrupted (a very rare event), you can lose the metadata. Fortunately, calibre
automatically backs up the metadata for every individual book in the book’s folder as an OPF file. By using the Restore
database action under Library Maintenance described above, you can have calibre rebuild the metadata.db file from
the individual OPF files for you.
You can copy or move books between different libraries (once you have more than one library setup) by right clicking
on the book and selecting the action Copy to library.
1.1.8 Device
The Device action allows you to view the books in the main memory or storage cards of your device, or
to eject the device (detach it from calibre). This icon shows up automatically on the main calibre toolbar when you
connect a supported device. You can click on it to see the books on your device. You can also drag and drop books
from your calibre library onto the icon to transfer them to your device. Conversely, you can drag and drop books from
your device onto the library icon on the toolbar to transfer books from your device to the calibre library.
The Save to disk action has five variations, accessed by doing a right-click on the button.
1. Save to disk: Saves the selected books to disk organized in directories. The directory structure looks
like:
Author_(sort)
Title
Book Files
You can control the file name and folder structure of files saved to disk by setting up a template in
Preferences→Import/export→Saving books to disk. Also see The calibre template language (page 159).
2. Save to disk in a single directory: Saves the selected books to disk in a single directory.
For 1. and 2., all available formats, as well as metadata, are stored to disk for each selected book. Metadata
is stored in an OPF file. Saved books can be re-imported to the library without any loss of information by
using the Add books (page 4) action.
3. Save only *<your preferred>* format to disk: Saves the selected books to disk in the directory
structure as shown in (1.) but only in your preferred e-book format. You can set your preferred
format in Preferences→Interface→Behaviour→Preferred output format
4. Save only *<your preferred>* format to disk in a single directory: Saves the selected books to
disk in a single directory but only in your preferred e-book format. You can set your preferred format
in Preferences→Interface→Behaviour→Preferred output format
5. Save single format to disk. . . : Saves the selected books to disk in the directory structure as shown
in (1.) but only in the format you select from the pop-out list.
1.1.10 Connect/share
The Connect/share action allows you to manually connect to a device or folder on your computer.
It also allows you to set up your calibre library for access via a web browser or email.
The Connect/share action has four variations, accessed by doing a right-click on the button.
1. Connect to folder: Allows you to connect to any folder on your computer as though it were a
device and use all the facilities calibre has for devices with that folder. Useful if your device cannot
be supported by calibre but is available as a USB disk.
2. Start Content server: Starts calibre’s built-in web server. When started, your calibre library will
be accessible via a web browser from the Internet (if you choose). You can configure how the web
server is accessed by setting preferences at Preferences→Sharing→Sharing over the net
3. Setup email based sharing of books: Allows sharing of books and news feeds by email. Af-
ter setting up email addresses for this option, calibre will send news updates and book updates to
the entered email addresses. You can configure how calibre sends email by setting preferences at
Preferences→Sharing→Sharing books by email. Once you have set up one or more email addresses,
this menu entry will be replaced by menu entries to send books to the configured email addresses.
The Remove books action deletes books permanently, so use it with care. It is context
sensitive, i.e. it depends on which catalog (page 10) you have selected. If you have selected the Library, books will be
removed from the library. If you have selected the e-book reader device, books will be removed from the device. To
remove only a particular format for a given book use the Edit metadata (page 5) action. Remove books also has five
variations which can be accessed by doing a right-click on the button.
1.1. Actions 9
calibre User Manual, Release 4.21.0
1. Remove selected books: Allows you to permanently remove all books that are selected in the book list.
2. Remove files of a specific format from selected books. . . : Allows you to permanently remove e-book files of
a specified format from books that are selected in the book list.
3. Remove all formats from selected books, except. . . : Allows you to permanently remove e-book files of any
format except a specified format from books that are selected in the book list.
4. Remove all formats from selected books: Allows you to permanently remove all e-book files from books that
are selected in the book list. Only the metadata will remain.
5. Remove covers from selected books: Allows you to permanently remove cover image files from books that
are selected in the book list.
6. Remove matching books from device: Allows you to remove e-book files from a connected device that match
the books that are selected in the book list.
Note: Note that when you use Remove books to delete books from your calibre library, the book record is permanently
deleted, but on Windows and macOS the files are placed into the recycle bin. This allows you to recover them if you
change your mind.
1.2 Preferences
The Preferences action allows you to change the way various aspects of calibre work. It has four
variations, accessed by doing a right-click on the button.
1. Preferences: Allows you to change the way various aspects of calibre work. Clicking the button also performs
this action.
2. Run Welcome wizard: Allows you to start the Welcome wizard which appeared the first time you started calibre.
3. Get plugins to enhance calibre: Opens a new window that shows plugins for calibre. These plugins are
developed by third parties to extend calibre’s functionality.
4. Restart in debug mode: Allows you to enable a debugging mode that can assist the calibre developers in
solving problems you encounter with the program. For most users this should remain disabled unless instructed
by a developer to enable it.
1.3 Catalogs
A catalog is a collection of books. calibre can manage two types of different catalogs:
1. Library: This is a collection of books stored in your calibre library on your computer.
2. Device: This is a collection of books stored in your e-book reader. It will be available when you connect the
reader to your computer.
Many operations, such as adding books, deleting, viewing, etc., are context sensitive. So, for example, if you click the
View button when you have the Device catalog selected, calibre will open the files on the device to view. If you have
the Library catalog selected, files in your calibre library will be opened instead.
The Search & Sort section allows you to perform several powerful actions on your book collections.
• You can sort them by title, author, date, rating, etc. by clicking on the column titles. You can also sub-sort, i.e.
sort on multiple columns. For example, if you click on the title column and then the author column, the book
will be sorted by author and then all the entries for the same author will be sorted by title.
• You can search for a particular book or set of books using the Search bar. More on that below.
• You can quickly and conveniently edit metadata by selecting the entry you want changed in the list and pressing
the E key.
• You can perform Actions (page 4) on sets of books. To select multiple books you can either:
– Keep the Ctrl key pressed and click on the books you want selected.
– Keep the Shift key pressed and click on the starting and ending book of a range of books you want
selected.
• You can configure which fields you want displayed by using the Preferences (page 10) dialog.
You can search all the metadata by entering search terms in the Search bar. Searches are case insensitive. For example:
This will match all books in your library that have Asimov and Foundation in their metadata and are available in
the LRF format. Some more examples:
Searches are by default ‘contains’. An item matches if the search string appears anywhere in the indicated metadata.
Two other kinds of searches are available: equality search and search using regular expressions2 .
Equality searches are indicated by prefixing the search string with an equals sign (=). For example, the query
tag:"=science" will match “science”, but not “science fiction” or “hard science”. Regular expression searches
are indicated by prefixing the search string with a tilde (~). Any Python-compatible regular expression3 can be used.
Note that backslashes used to escape special characters in regular expressions must be doubled because single back-
slashes will be removed during query parsing. For example, to match a literal parenthesis you must enter \\(. Regular
expression searches are ‘contains’ searches unless the expression contains anchors.
Should you need to search for a string with a leading equals or tilde, prefix the string with a backslash.
Enclose search strings with quotes (“) if the string contains parenthesis or spaces. For example, to search for
the tag Science Fiction you would need to search for tag:"=science fiction". If you search for
tag:=science fiction you will find all books with the tag ‘science’ and containing the word ‘fiction’ in any
metadata.
You can build advanced search queries easily using the Advanced search dialog accessed by clicking the button
.
Available fields for searching are: tag, title, author, publisher, series, series_index,
rating, cover, comments, format, identifiers, date, pubdate, search, size, vl
and custom columns. If a device is plugged in, the ondevice field becomes available, when searching the calibre
library view. To find the search name (actually called the lookup name) for a custom column, hover your mouse over
the column header in the library view.
The syntax for searching for dates is:
If the date is ambiguous, the current locale is used for date comparison. For example, in an mm/dd/yyyy locale
2/1/2009 is interpreted as 1 Feb 2009. In a dd/mm/yyyy locale it is interpreted as 2 Jan 2009. Some special date
strings are available. The string today translates to today’s date, whatever it is. The strings yesterday and
thismonth (or the translated equivalent in the current language) also work. In addition, the string daysago (also
translated) can be used to compare to a date some number of days ago. For example:
date:>10daysago
date:<=45daysago
To avoid potential problems with translated strings when using a non-English version of calibre, the strings _today,
_yesterday, _thismonth, and _daysago are always available. They are not translated.
You can search for books that have a format of a certain size like this:
2 https://en.wikipedia.org/wiki/Regular_expression
3 https://docs.python.org/library/re.html
Dates and numeric fields support the relational operators = (equals), > (greater than), >= (greater than or equal to), <
(less than), <= (less than or equal to), and != (not equal to). Rating fields are considered to be numeric. For example,
the search rating:>=3 will find all books rated 3 or higher.
You can search for the number of items in multiple-valued fields such as tags. These searches begin with the character
#, then use the same syntax as numeric fields. For example, to find all books with more than 4 tags use tags:#>4.
To find all books with exactly 10 tags use tags:#=10.
Series indices are searchable. For the standard series, the search name is ‘series_index’. For custom series columns,
use the column search name followed by _index. For example, to search the indices for a custom series column named
#my_series, you would use the search name #my_series_index. Series indices are numbers, so you can use
the relational operators described above.
The special field search is used for saved searches. So if you save a search with the name “My spouse’s books”
you can enter search:"My spouse's books" in the Search bar to reuse the saved search. More about saving
searches below.
The special field vl is used to search for books in a Virtual library. For example, vl:Read will find all the books in
the Read Virtual library. The search vl:Read and vl:"Science Fiction" will find all the books that are in
both the Read and Science Fiction Virtual libraries. The value following vl: must be the name of a Virtual library. If
the Virtual library name contains spaces then surround it with quotes.
You can search for the absence or presence of a field using the special “true” and “false” values. For example:
cover:false will give you all books without a cover
series:true will give you all books that belong to a series
comments:false will give you all books with an empty comment
format:false will give you all books with no actual files (empty records)
Yes/no custom columns are searchable. Searching for false, empty, or blank will find all books with undefined
values in the column. Searching for true will find all books that do not have undefined values in the column.
Searching for yes or checked will find all books with Yes in the column. Searching for no or unchecked will
find all books with No in the column. Note that the words yes, no, blank, empty, checked and unchecked
are translated; you can use either the current language’s equivalent word or the English word. The words true and
false and the special values _yes, _no, and _empty are not translated.
Hierarchical items (e.g. A.B.C) use an extended syntax to match initial parts of the hierarchy. This is done by adding
a period between the exact match indicator (=) and the text. For example, the query tags:=.A will find the tags A
and A.B, but will not find the tags AA or AA.B. The query tags:=.A.B will find the tags A.B and A.B.C, but not the
tag A.
Identifiers (e.g., ISBN, doi, lccn etc) also use an extended syntax. First, note that an identifier has the form
type:value, as in isbn:123456789. The extended syntax permits you to specify independently which type
and value to search for. Both the type and the value parts of the query can use equality, contains, or regular expression
matches. Examples:
• identifiers:true will find books with any identifier.
• identifiers:false will find books with no identifier.
• identifiers:123 will search for books with any type having a value containing 123.
• identifiers:=123456789 will search for books with any type having a value equal to 123456789.
• identifiers:=isbn: and identifiers:isbn:true will find books with a type equal to ISBN hav-
ing any value
• identifiers:=isbn:false will find books with no type equal to ISBN.
• identifiers:=isbn:123 will find books with a type equal to ISBN having a value containing 123.
• identifiers:=isbn:=123456789 will find books with a type equal to ISBN having a value equal to
123456789.
• identifiers:i:1 will find books with a type containing an i having a value containing a 1.
calibre allows you to save a frequently used search under a special name and then reuse that search with a single click.
To do this, create your search either by typing it in the Search bar or using the Tag browser. Then type the name you
would like to give to the search in the Saved Searches box next to the Search bar. Click the plus icon next to the saved
searches box to save the search.
Now you can access your saved search in the Tag browser under “Searches”. A single click will allow you to reuse
any arbitrarily complex search easily, without needing to re-create it.
A Virtual library is a way to pretend that your calibre library has only a few books instead of its full collection. This
is an excellent way to partition your large collection of books into smaller, manageable chunks. To learn how to create
and use Virtual libraries, see the tutorial: Virtual libraries (page 224).
Normally, calibre reads metadata from inside the book file. However, it can be configured to read metadata from the
file name instead, via Preferences→Import/export→Adding books→Read metadata from file contents.
You can also control how metadata is read from the filename using regular expressions (see All about using regular
expressions in calibre (page ??)). In the Adding Books section of the configuration dialog, you can specify a regular
expression that calibre will use to try and guess metadata from the names of e-book files that you add to the library.
The default regular expression is:
title - author
that is, it assumes that all characters up to the first - are the title of the book and subsequent characters are the author
of the book. For example, the filename:
will be interpreted to have the title: Foundation and Earth and author: Isaac Asimov
Tip: If the filename does not contain the hyphen, the above regular expression will fail.
The Book details display shows the cover and all the metadata for the currently selected book. It can be hidden via
the Layout button in the lower right corner of the main calibre window. The author names shown in the Book details
panel are click-able, they will by default take you to the Wikipedia page for the author. This can be customized by
right clicking on the author name and selecting Manage this author.
Similarly, if you download metadata for the book, the Book details panel will automatically show you links pointing
to the web pages for the book on amazon, worldcat, etc. from where the metadata was downloaded.
You can right click on individual e-book formats in the Book details panel to delete them, compare them to their
original versions, save them to disk, open them with an external program, etc.
You can change the cover of the book by simply drag and dropping an image onto the Book details panel. If you wish
to edit the cover image in an external program, simply right click on it and choose Open with.
You can also add e-book files to the current book by drag and dropping the files onto the Book details panel.
Double clicking the Book details panel will open it up in a separate popup window.
Finally, you can customize exactly what information is displayed in the Book details panel via
Preferences→Interface→Look & feel→Book details.
The Tag browser allows you to easily browse your collection by Author/Tags/Series/etc. If you click on any item in
the Tag browser, for example the author name Isaac Asimov, then the list of books to the right is restricted to showing
books by that author. You can click on category names as well. For example, clicking on “Series” will show you all
books in any series.
The first click on an item will restrict the list of books to those that contain or match the item. Continuing the above
example, clicking on Isaac Asimov will show books by that author. Clicking again on the item will change what is
shown, depending on whether the item has children (see sub-categories and hierarchical items below). Continuing the
Isaac Asimov example, clicking again on Isaac Asimov will restrict the list of books to those not by Isaac Asimov. A
third click will remove the restriction, showing all books. If you hold down the Ctrl or Shift keys and click on multiple
items, then restrictions based on multiple items are created. For example you could hold Ctrl and click on the tags
History and Europe for finding books on European history. The Tag browser works by constructing search expressions
that are automatically entered into the Search bar. Looking at what the Tag browser generates is a good way to learn
how to construct basic search expressions.
Items in the Tag browser have their icons partially colored. The amount of color depends on the average rating of the
books in that category. So for example if the books by Isaac Asimov have an average of four stars, the icon for Isaac
Asimov in the Tag browser will be 4/5th colored. You can hover your mouse over the icon to see the average rating.
The outer-level items in the Tag browser, such as Authors and Series, are called categories. You can create your
own categories, called User categories, which are useful for organizing items. For example, you can use the User
categories editor (click the Configure button at the lower-left of the Tag browser and choose Manage authors, series,
etc→User categories) to create a User category called Favorite Authors, then put the items for your favorites
into the category. User categories can have sub-categories. For example, the User category Favorites.Authors
is a sub-category of Favorites. You might also have Favorites.Series, in which case there will be two
sub-categories under Favorites. Sub-categories can be created by right-clicking on a User category, choosing Add
sub-category to. . . , and entering the sub-category name; or by using the User categories editor by entering names like
the Favorites example above.
You can search User categories in the same way as built-in categories, by clicking on them. There are four different searches cyc
1. “everything matching an item in the category” indicated by a single green plus sign.
2. “everything matching an item in the category or its sub-categories” indicated by two green plus signs.
3. “everything not matching an item in the category” shown by a single red minus sign.
4. “everything not matching an item in the category or its sub-categories” shown by two red minus signs.
It is also possible to create hierarchies inside some of the text categories such as tags, series, and custom columns.
These hierarchies show with the small triangle, permitting the sub-items to be hidden. To use hierarchies of items
in a category, you must first go to Preferences→Interface→Look & feel and enter the category name(s) into the
“Categories with hierarchical items” field. Once this is done, items in that category that contain periods will be shown
using the small triangle. For example, assume you create a custom column called “Genre” and indicate that it contains
hierarchical items. Once done, items such as Mystery.Thriller and Mystery.English will display as Mystery with the
small triangle next to it. Clicking on the triangle will show Thriller and English as sub-items. See Managing subgroups
of books, for example “genre” (page 151) for more information.
Hierarchical items (items with children) use the same four ‘click-on’ searches as User categories. Items that do not
have children use two of the searches: “everything matching” and “everything not matching”.
You can drag and drop items in the Tag browser onto User categories to add them to that category. If the source is
a User category, holding the shift key while dragging will move the item to the new category. You can also drag
and drop books from the book list onto items in the Tag browser; dropping a book on an item causes that item to be
automatically applied to the dropped books. For example, dragging a book onto Isaac Asimov will set the author of
that book to Isaac Asimov. Dropping it onto the tag History will add the tag History to the book’s tags.
You can easily find any item in the Tag browser by clicking the search button at the lower-right corner. In addition,
you can right click on any item and choose one of several operations. Some examples are to hide it, rename it, or open
a “Manage x” dialog that allows you to manage items of that kind. For example, the “Manage Authors” dialog allows
you to rename authors and control how their names are sorted.
You can control how items are sorted in the Tag browser via the Configure button at the lower-left of the Tag browser.
You can choose to sort by name, average rating or popularity (popularity is the number of books with an item in your
library; for example, the popularity of Isaac Asimov is the number of books in your library by Isaac Asimov).
You can have calibre display a grid of book covers instead of a list of books, if you prefer to browse your collection by
covers instead. The Cover grid is activated by clicking the Layout button in the bottom right corner of the main calibre
window. You can customize the cover sizes and the background of the Cover grid via Preferences→Interface→Look
& feel→Cover grid. You can even have calibre display any specified field under the covers, such as title or authors or
rating or a custom column of your own devising.
In addition to the Cover grid described above, you can also have calibre display covers in the single row. This is
activated via the Layout button in the lower right corner of the main window. In Preferences→Interface→Look &
feel→Cover browser you can change the number of covers displayed, and even have the Cover browser display itself
in a separate popup window.
1.13 Quickview
Sometimes you want to select a book and quickly get a list of books with the same value in some category (authors,
tags, publisher, series, etc.) as the currently selected book, but without changing the current view of the library. You
can do this with Quickview. Quickview opens either a second window or a panel in the book list showing the list of
books matching the value of interest. For example, assume you want to see a list of all the books with the one or
more of the authors of the currently-selected book. Click in the author cell you are interested in and press the ‘Q’ key
or click the Quickview icon in the Layout section of the calibre window. A window or panel will open with all the
authors for that book on the left, and all the books by the selected author on the right.
Some example Quickview usages: quickly seeing what other books:
• have some tag(s) applied to the currently selected book,
• are in the same series as the current book
• have the same values in a custom column as the current book
• are written by one of the same authors of the current book
• share values in a custom column
There are two choices for where the Quickview information appears:
1. It can open “undocked”: on top of the calibre window and will stay open until you explicitly close it.
2. It can open “docked”: as a panel in the book list section of the calibre main window.
You can move the window from docked to undocked as desired using the “Dock/Undock” button.
The Quickview panel can be left open permanently, in which case it follows movements on the book list. For example,
if you click in the calibre library view on a category column (tags, series, publisher, authors, etc.) for a book, the
Quickview window contents will change to show you in the left-hand side panel the values in that category for the
selected book (e.g., the tags for that book). The first item in that list will be selected, and Quickview will show you on
the right-hand side panel all the books in your library that use that value. Click on an different value in the left-hand
panel to see the books with that different value.
Double-click on a book in the Quickview window to select that book in the library view. This will also change the
items display in the QuickView window (the left-hand panel) to show the items in the newly-selected book.
Shift- or Ctrl- double-click on a book in the Quickview window to open the edit metadata dialog on that book in
the calibre window. The edited book will be Quickview’ed when you close the edit metadata dialog.
You can see if a column can be Quickview’ed by hovering your mouse over the column heading and looking at the
tooltip for that heading. You can also know by right-clicking on the column heading to see of the “Quickview” option
is shown in the menu, in which case choosing that Quickview option is equivalent to pressing ‘Q’ in the current cell.
Options (in Preferences→Look & feel→Quickview):
• Respect (or not) the current Virtual library. If checked then Quickview shows only books in the current Virtual
library. Default: respect Virtual libraries
• Change the Quickview window contents when the column is changed on the book list using the cursor keys.
Default: don’t follow changes made with cursor keys
• Change the column being “quickview’ed” when a cell in the Quickview window is double-clicked. Otherwise
the book is changed but the column being examined is not. Default: change the column
• Change the column being “quickview’ed” to the current column when the return key is pressed in the Quickview
panel. Otherwise the book is changed but the column being examined is not. Default: change the column
• Choose which columns are shown in the Quickview window/panel.
1.14 Jobs
The Jobs panel shows the number of currently running jobs. Jobs are tasks that run in a separate process. They include
converting e-books and talking to your reader device. You can click on the jobs panel to access the list of jobs. Once
a job has completed you can see a detailed log from that job by double-clicking it in the list. This is useful to debug
jobs that may not have completed successfully.
calibre has several keyboard shortcuts to save you time and mouse movement. These shortcuts are active in the book
list view (when you’re not editing the details of a particular book), and most of them affect the title you have selected.
The calibre E-book viewer has its own shortcuts which can be customised by clicking the Preferences button in the
viewer.
Note: Note: The calibre keyboard shortcuts do not require a modifier key (Command, Option, Control, etc.), unless
specifically noted. You only need to press the letter key, e.g. E to edit.
calibre has a powerful, flexible and easy-to-use framework for downloading news from the Internet and converting it
into an e-book. The following will show you, by means of examples, how to get news from various websites.
To gain an understanding of how to use the framework, follow the examples in the order listed below:
If your news source is simple enough, calibre may well be able to fetch it completely automatically, all you need to
do is provide the URL. calibre gathers all the information needed to download a news source into a recipe. In order to
tell calibre about a news source, you have to create a recipe for it. Let’s see some examples:
25
calibre User Manual, Release 4.21.0
The calibre blog is a blog of posts that describe many useful calibre features in a simple and accessible way for new
calibre users. In order to download this blog into an e-book, we rely on the RSS feed of the blog:
http://blog.calibre-ebook.com/feeds/posts/default
I got the RSS URL by looking under “Subscribe to” at the bottom of the blog page and choosing Posts→Atom. To
make calibre download the feeds and convert them into an e-book, you should right click the Fetch news button and
then the Add a custom news source menu item and then the New Recipe button. A dialog similar to that shown below
should open up.
First enter Calibre Blog into the Recipe title field. This will be the title of the e-book that will be created from the
articles in the above feeds.
The next two fields (Oldest article and Max. number of articles) allow you some control over how many articles
should be downloaded from each feed, and they are pretty self explanatory.
To add the feeds to the recipe, enter the feed title and the feed URL and click the Add feed button. Once you have
added the feed, simply click the Save button and you’re done! Close the dialog.
To test your new recipe, click the Fetch news button and in the Custom news sources sub-menu click calibre Blog.
After a couple of minutes, the newly downloaded e-book of blog posts will appear in the main library view (if you
have your reader connected, it will be put onto the reader instead of into the library). Select it and hit the View button
to read!
The reason this worked so well, with so little effort is that the blog provides full-content RSS feeds, i.e., the article
content is embedded in the feed itself. For most news sources that provide news in this fashion, with full-content feeds,
you don’t need any more effort to convert them to e-books. Now we will look at a news source that does not provide
full content feeds. In such feeds, the full article is a webpage and the feed only contains a link to the webpage with a
short summary of the article.
2.1.2 bbc.co.uk
When you want to perfect the download process, or download content from a particularly complex website, you can
avail yourself of all the power and flexibility of the recipe framework. In order to do that, in the Add custom news
sources dialog, simply click the Switch to Advanced mode button.
The easiest and often most productive customization is to use the print version of the online articles. The print version
typically has much less cruft and translates much more smoothly to an e-book. Let’s try to use the print version of the
articles from The BBC.
The first step is to look at the e-book we downloaded previously from bbc.co.uk (page 27). At the end of each article,
in the e-book is a little blurb telling you where the article was downloaded from. Copy and paste that URL into a
browser. Now on the article webpage look for a link that points to the “Printable version”. Click it to see the print
version of the article. It looks much neater! Now compare the two URLs. For me they were:
Article URL https://news.bbc.co.uk/2/hi/science/nature/7312016.stm
Print version URL https://newsvote.bbc.co.uk/mpapps/pagetools/print/news.bbc.co.uk/2/hi/science/
nature/7312016.stm
So it looks like to get the print version, we need to prefix every article URL with:
newsvote.bbc.co.uk/mpapps/pagetools/print/
Now in the Advanced Mode of the Custom news sources dialog, you should see something like (remember to select
The BBC recipe before switching to advanced mode):
You can see that the fields from the Basic mode have been translated to Python code in a straightforward manner. We
need to add instructions to this recipe to use the print version of the articles. All that’s needed is to add the following
two lines:
This is Python, so indentation is important. After you’ve added the lines, it should look like:
In the above, def print_version(self, url) defines a method that is called by calibre for every article.
url is the URL of the original article. What print_version does is take that url and replace it with the new URL
that points to the print version of the article. To learn about Python4 see the tutorial5 .
Now, click the Add/update recipe button and your changes will be saved. Re-download the e-book. You should have
a much improved e-book. One of the problems with the new version is that the fonts on the print version webpage are
too small. This is automatically fixed when converting to an e-book, but even after the fixing process, the font size
of the menus and navigation bar to become too large relative to the article text. To fix this, we will do some more
customization, in the next section.
In the previous section, we saw that the font size for articles from the print version of The BBC was too small. In most
websites, The BBC included, this font size is set by means of CSS stylesheets. We can disable the fetching of such
stylesheets by adding the line:
4 https://www.python.org
5 https://docs.python.org/tutorial/
no_stylesheets = True
The new version looks pretty good. If you’re a perfectionist, you’ll want to read the next section, which deals with
actually modifying the downloaded content.
calibre contains very powerful and flexible abilities when it comes to manipulating downloaded content. To show off
a couple of these, let’s look at our old friend the The BBC (page 29) recipe again. Looking at the source code (HTML)
of a couple of articles (print version), we see that they have a footer that contains no useful information, contained in
<div class="footer">
...
</div>
to the recipe. Finally, lets replace some of the CSS that we disabled earlier, with our own CSS that is suitable for
conversion to an e-book:
extra_css = '.headline {font-size: x-large;} \n .fact { padding-top: 10pt }'
With these additions, our recipe has become “production quality”, indeed it is very close to the actual recipe used by
calibre for the BBC, shown below:
##
# Title: BBC News, Sport, and Blog Calibre Recipe
# Contact: mattst - [email protected]
##
# License: GNU General Public License v3 - https://www.gnu.org/copyleft/gpl.html
# Copyright: mattst - [email protected]
##
# Written: November 2011
# Last Edited: 2011-11-19
##
'''
BBC News, Sport, and Blog Calibre Recipe
'''
def classes(classes):
q = frozenset(classes.split(' '))
return dict(attrs={
'class': lambda x: x and frozenset(x.split()).intersection(q)})
class BBCNews(BasicNewsRecipe):
#
# **** IMPORTANT USERS READ ME ****
#
# First select the feeds you want then scroll down below the feeds list
# and select the values you want for the other user preferences, like
# oldest_article and such like.
#
#
# Select the BBC rss feeds which you want in your ebook.
# Selected feed have NO '#' at their start, de-selected feeds begin with a '#'.
#
# Eg. ("News Home", "https://feeds.bbci.co.uk/... - include feed.
# Eg. #("News Home", "https://feeds.bbci.co.uk/... - do not include feed.
#
# There are 68 feeds below which constitute the bulk of the available rss
# feeds on the BBC web site. These include 5 blogs by editors and
# correspondents, 16 sports feeds, 15 'sub' regional feeds (Eg. North West
# Wales, Scotland Business), and 7 Welsh language feeds.
#
# Some of the feeds are low volume (Eg. blogs), or very low volume (Eg. Click)
# so if "oldest_article = 1.5" (only articles published in the last 36 hours)
# you may get some 'empty feeds' which will not then be included in the ebook.
#
# The 15 feeds currently selected below are simply my default ones.
#
# Note: With all 68 feeds selected, oldest_article set to 2,
# max_articles_per_feed set to 100, and simultaneous_downloads set to 10,
# the ebook creation took 29 minutes on my speedy 100 mbps net connection,
# fairly high-end desktop PC running Linux (Ubuntu Lucid-Lynx).
# More realistically with 15 feeds selected, oldest_article set to 1.5,
# max_articles_per_feed set to 100, and simultaneous_downloads set to 20,
# it took 6 minutes. If that's too slow increase 'simultaneous_downloads'.
#
# Select / de-select the feeds you want in your ebook.
(continues on next page)
# ("Newsbeat", "https://www.bbc.co.uk/newsbeat/rss.xml"),
# ("Click", "https://newsrss.bbc.co.uk/rss/newsonline_uk_edition/programmes/
˓→click_online/rss.xml"),
# ("Cricket", "https://newsrss.bbc.co.uk/rss/sportonline_uk_edition/cricket/
˓→rss.xml"),
# ("Tennis", "https://newsrss.bbc.co.uk/rss/sportonline_uk_edition/tennis/rss.
˓→xml"),
# ("Golf", "https://newsrss.bbc.co.uk/rss/sportonline_uk_edition/golf/rss.xml
˓→"),
# ("Motorsport", "https://newsrss.bbc.co.uk/rss/sportonline_uk_edition/
˓→motorsport/rss.xml"),
# ("Boxing", "https://newsrss.bbc.co.uk/rss/sportonline_uk_edition/boxing/rss.
˓→xml"),
# ("Athletics", "https://newsrss.bbc.co.uk/rss/sportonline_uk_edition/
˓→athletics/rss.xml"), (continues on next page)
# ("Cycling", "https://newsrss.bbc.co.uk/rss/sportonline_uk_edition/other_
˓→sports/cycling/rss.xml"),
# ("Gogledd-Ddwyrain", "https://feeds.bbci.co.uk/newyddion/gogledd-ddwyrain/
˓→rss.xml"),
# ("Gogledd-Orllewin", "https://feeds.bbci.co.uk/newyddion/gogledd-orllewin/
˓→rss.xml"),
# ("Canolbarth", "https://feeds.bbci.co.uk/newyddion/canolbarth/rss.xml"),
# ("De-Ddwyrain", "https://feeds.bbci.co.uk/newyddion/de-ddwyrain/rss.xml"),
# ("De-Orllewin", "https://feeds.bbci.co.uk/newyddion/de-orllewin/rss.xml"),
]
# The max number of articles which may be downloaded from each feed.
# I've never seen more than about 70 articles in a single feed in the
# BBC feeds.
#
max_articles_per_feed = 100
# The max age of articles which may be downloaded from each feed. This is
# specified in days - note fractions of days are allowed, Eg. 2.5 (2 and a
# half days). My default of 1.5 days is the last 36 hours, the point at
# which I've decided 'news' becomes 'old news', but be warned this is not
# so good for the blogs, technology, magazine, etc., and sports feeds.
# You may wish to extend this to 2-5 but watch out ebook creation time will
# increase as well. Setting this to 30 will get everything (AFAICT) as long
# as max_articles_per_feed remains set high (except for 'Click' which is
# v. low volume and its currently oldest article is 4th Feb 2011).
#
oldest_article = 1.5
# Timeout for fetching files from the server in seconds. The default of
# 120 seconds, seems somewhat excessive.
#
timeout = 30
# The format string for the date shown on the ebook's first page.
# List of all values: https://docs.python.org/library/time.html
# Default in news.py has a leading space so that's mirrored here.
# As with 'feeds' select/de-select by adding/removing the initial '#',
# only one timefmt should be selected, here's a few to choose from.
#
# [Fri, 14 Nov 2011] (Calibre default)
timefmt = ' [%a, %d %b %Y]'
# timefmt = ' [%a, %d %b %Y %H:%M]' # [Fri, 14 Nov 2011 18:30]
# timefmt = ' [%a, %d %b %Y %I:%M %p]' # [Fri, 14 Nov 2011 06:30 PM]
# timefmt = ' [%d %b %Y]' # [14 Nov 2011]
# timefmt = ' [%d %b %Y %H:%M]' # [14 Nov 2011 18.30]
# timefmt = ' [%Y-%m-%d]' # [2011-11-14]
# timefmt = ' [%Y-%m-%d-%H-%M]' # [2011-11-14-18-30]
#
# **** IMPORTANT ****
#
# DO NOT EDIT BELOW HERE UNLESS YOU KNOW WHAT YOU ARE DOING.
#
(continues on next page)
# Set tags.
tags = 'news, sport, blog'
# Sets whether a feed has full articles embedded in it. The BBC feeds do
# not.
use_embedded_content = False
# Create a custom title which fits nicely in the Kindle title list.
# Requires "import time" above class declaration, and replacing
# title with custom_title in conversion_options (right column only).
# Example of string below: "BBC News - 14 Nov 2011"
#
# custom_title = "BBC News - " + time.strftime('%d %b %Y')
# Remove various tag attributes to improve the look of the ebook pages.
remove_attributes = ['border', 'cellspacing', 'align', 'cellpadding', 'colspan',
'valign', 'vspace', 'hspace', 'alt', 'width', 'height']
# Remove the (admittedly rarely used) line breaks, "<br />", which sometimes
# cause a section of the ebook to start in an unsightly fashion or, more
# frequently, a "<br />" will muck up the formatting of a correspondant's byline.
# "<br />" and "<br clear/>" are far more frequently used on the table formatted
# style of pages, and really spoil the look of the ebook pages.
preprocess_regexps = [(re.compile(r'<br[ ]*/>', re.IGNORECASE), lambda m: ''),
(re.compile(r'<br[ ]*clear.*/>', re.IGNORECASE), lambda m: '
˓→')]
# Create regular expressions for tag keeping and removal to make the matches more
# robust against minor changes and errors in the HTML, Eg. double spaces, leading
# and trailing spaces, missing hyphens, and such like.
# Python regular expression ('re' class) page:
# https://docs.python.org/library/re.html
# ***************************************
# Regular expressions for keep_only_tags:
# ***************************************
# The BBC News HTML pages use variants of 'storybody' to denote the section of a
˓→HTML
# page which contains the main text of the article. Match storybody variants:
˓→'storybody',
# The BBC sport and 'newsbeat' (features) HTML pages use 'blq_content' to hold
˓→ the title (continues on next page)
# and date within 'story-body'. This is annoying since 'blq_content' must also be
˓→kept,
# The BBC has an alternative page design structure, which I suspect is an out-of-
˓→date
# design but which is still used in some articles, Eg. 'Click' (technology),
˓→'FastTrack'
# (travel), and in some sport pages. These alternative pages are table based
˓→(which is
# why I think they are an out-of-date design) and account for -I'm guesstimaking-
˓→less
# than 1% of all articles. They use a table class 'storycontent' to hold the
˓→article
# Keep the sections of the HTML which match the list below. The HTML page created
˓→by
# Calibre will fill <body> with those sections which are matched. Note that the
# blq_content_reg_exp must be listed before storybody_reg_exp in keep_only_tags
˓→due to
# all). If they are the other way around in keep_only_tags then blq_content_reg_
˓→exp
# ************************************
# Regular expressions for remove_tags:
# ************************************
# Regular expression to remove share-help and variant tags. The share-help class
# is used by the site for a variety of 'sharing' type links, Eg. Facebook,
˓→delicious,
# Regular expression to remove hypertabs and variant tags. This class is used to
# display a tab bar at the top of an article which allows the user to switch to
# an article (viewed on the same page) providing further info., 'in depth'
˓→analysis,
# an editorial, a correspondant's blog entry, and such like. The ability to handle
# a tab bar of this nature is currently beyond the scope of this recipe and
# possibly of Calibre itself (not sure about that - TO DO - check!).
hypertabs_reg_exp = '^.*hyper[_ -]*tabs.*$'
# Regular expression to remove social-links and variant tags. This class is used
˓→ to
# display links to a BBC bloggers main page, used in various columnist's blogs
# (Eg. Nick Robinson, Robert Preston).
social_links_reg_exp = '^.*social[_ -]*links.*$'
# Regular expression to remove quote and (multi) variant tags, Eg. 'quote',
# 'endquote', 'quote-credit', 'quote-credit-title', etc. These are usually
# removed by 'story-feature' removal (as they are usually within them), but
# not always. The quotation removed is always (AFAICT) in the article text
# as well but a 2nd copy is placed in a quote tag to draw attention to it.
# The quote class tags may or may not appear in div's.
quote_reg_exp = '^.*quote.*$'
# <div id="navigation">
# Used on sports pages to link to pages like 'tables', 'fixtures', etc.
# Used sometimes instead of "featured-content" above.
navigation_reg_exp = '^.*navigation.*$'
# Remove class 'o'. The worst named user created css class of all time. The
˓→ creator
# should immediately be fired. I've seen it used to hold nothing at all but with
# 20 or so empty lines in it. Also to hold a single link to another article.
# Whatever it was designed to do it is not wanted by this recipe. Exact
# match only.
o_reg_exp = '^o$'
# Remove 'nlp', provides heading for link lists. Requires an exact match due to
# risk of matching those letters in something needed, unless I see a variation
# of 'nlp' used at a later date.
nlp_reg_exp = '^nlp$'
# Remove 'mva', provides embedded floating content of various types. Variant 'mvb'
# has also now been seen. Requires an exact match of 'mva' or 'mvb' due to risk of
# matching those letters in something needed.
mva_or_mvb_reg_exp = '^mv[ab]$'
# Remove 'products and services' links, Eg. desktop tools, alerts, and so on.
# Eg. Class="servicev4 ukfs_services" - what a mess of a name. Have decided to
# use two reg expressions to make removing this (and variants) robust.
prods_services_01_reg_exp = '^.*servicev4.*$'
prods_services_02_reg_exp = '^.*ukfs[_ -]*services.*$'
# Remove -what I think is- some kind of navigation tools helper class, though I am
# not sure, it's called: 'blq-rst blq-new-nav'. What I do know is it pops up
# frequently and it is not wanted. Have decided to use two reg expressions to make
# removing this (and variants) robust.
blq_misc_01_reg_exp = '^.*blq[_ -]*rst.*$'
blq_misc_02_reg_exp = '^.*blq[_ -]*new[_ -]*nav.*$'
# Remove 'puffbox' - this may only appear inside 'storyextra', so it may not
# need removing - I have no clue what it does other than it contains links.
# Whatever it is - it is not part of the article and is not wanted.
puffbox_reg_exp = '^.*puffbox.*$'
remove_tags = [
classes('sharetools share-tools--no-event-tag'),
dict(name='div', attrs={'class': re.compile(story_feature_reg_exp, re.
˓→IGNORECASE)}),
# Uses url to create and return the 'printer friendly' version of the url.
# In other words the 'print this page' address of the page.
#
# There are 3 types of urls used in the BBC site's rss feeds. There is just
# 1 type for the standard news while there are 2 used for sports feed urls.
# Note: Sports urls are linked from regular news feeds (Eg. 'News Home') when
# there is a major story of interest to 'everyone'. So even if no BBC sports
# feeds are added to 'feeds' the logic of this method is still needed to avoid
# blank / missing / empty articles which have an index title and then no
# body.
def print_version(self, url):
if url.startswith("https://www.bbc.co.uk/news/world-51235105"):
self.abort_article("This article contains a gigantic coronavirus table")
return print_url
# Most BBC rss feed video only 'articles' use upper case 'VIDEO'
# as a title prefix. Just match upper case 'VIDEO', so that
# articles like 'Video game banned' won't be matched and
# removed.
if 'VIDEO' in article.title:
feed.articles.remove(article)
# Most BBC rss feed audio only 'articles' use upper case 'AUDIO'
# as a title prefix. Just match upper case 'AUDIO', so that
# articles like 'Hi-Def audio...' won't be matched and removed.
elif 'AUDIO' in article.title:
feed.articles.remove(article)
# Most BBC rss feed photo slideshow 'articles' use 'In Pictures',
# 'In pictures', and 'in pictures', somewhere in their title.
# Match any case of that phrase.
elif 'IN PICTURES' in article.title.upper():
feed.articles.remove(article)
# 'Quiz of the week' is a Flash player weekly news quiz. Match only
# the 'Quiz of the' part in anticipation of monthly and yearly
# variants. Match any case.
elif 'QUIZ OF THE' in article.title.upper():
feed.articles.remove(article)
# Remove articles with 'scorecards' in the url. These are BBC sports
# pages which just display a cricket scorecard. The pages have a mass
# of table and css entries to display the scorecards nicely. Probably
# could make them work with this recipe, but might take a whole day
# of work to sort out all the css - basically a formatting
# nightmare.
elif 'scorecards' in article.url:
feed.articles.remove(article)
return feeds
This recipe explores only the tip of the iceberg when it comes to the power of calibre. To explore more of the abilities
of calibre we’ll examine a more complex real life example in the next section.
A reasonably complex real life example that exposes more of the API of BasicNewsRecipe is the recipe for The
New York Times
import string, re
from calibre import strftime
from calibre.web.feeds.recipes import BasicNewsRecipe
from calibre.ebooks.BeautifulSoup import BeautifulSoup
class NYTimes(BasicNewsRecipe):
def get_browser(self):
br = BasicNewsRecipe.get_browser()
if self.username is not None and self.password is not None:
br.open('https://www.nytimes.com/auth/login')
br.select_form(name='login')
br['USERID'] = self.username
br['PASSWORD'] = self.password
br.submit()
return br
def parse_index(self):
soup = self.index_to_soup('https://www.nytimes.com/pages/todayspaper/index.
˓→html')
def feed_title(div):
return ''.join(div.findAll(text=True, recursive=False)).strip()
articles = {}
key = None
ans = []
for div in soup.findAll(True,
attrs={'class':['section-headline', 'story', 'story headline']}):
if ''.join(div['class']) == 'section-headline':
key = string.capwords(feed_title(div))
articles[key] = []
ans.append(key)
This sets the displayed time on the front page of the created e-book to be in the format, Day, Day_Number
Month, Year. See timefmt (page 55).
Then we see a group of directives to cleanup the downloaded HTML:
remove_tags_before = dict(name='h1')
remove_tags_after = dict(id='footer')
remove_tags = ...
These remove everything before the first <h1> tag and everything after the first tag whose id is footer. See
remove_tags (page 54), remove_tags_before (page 54), remove_tags_after (page 54).
The next interesting feature is:
needs_subscription = True
...
def get_browser(self):
...
needs_subscription = True tells calibre that this recipe needs a username and password in order to access
the content. This causes, calibre to ask for a username and password whenever you try to use this recipe. The code in
calibre.web.feeds.news.BasicNewsRecipe.get_browser() (page 48) actually does the login into
the NYT website. Once logged in, calibre will use the same, logged in, browser instance to fetch all content. See
mechanize6 to understand the code in get_browser.
The next new feature is the calibre.web.feeds.news.BasicNewsRecipe.parse_index() (page 49)
method. Its job is to go to https://www.nytimes.com/pages/todayspaper/index.html and fetch the list of articles that
appear in todays paper. While more complex than simply using RSS, the recipe creates an e-book that corresponds
very closely to the days paper. parse_index makes heavy use of BeautifulSoup7 to parse the daily paper webpage.
You can also use other, more modern parsers if you dislike BeautifulSoup. calibre comes with lxml8 and html5lib9 ,
which are the recommended parsers. To use them, replace the call to index_to_soup() with the following:
6 https://mechanize.readthedocs.io/en/latest/
7 https://www.crummy.com/software/BeautifulSoup/bs4/doc/
8 https://lxml.de/
9 https://github.com/html5lib/html5lib-python
The best way to develop new recipes is to use the command line interface. Create the recipe using your favorite Python
editor and save it to a file say myrecipe.recipe. The .recipe extension is required. You can download content
using this recipe with the command:
The command ebook-convert will download all the webpages and save them to the EPUB file myrecipe.
epub. The -vv option makes ebook-convert spit out a lot of information about what it is doing. The
ebook-convert-recipe-input --test (page 294) option makes it download only a couple of articles from
at most two feeds. In addition, ebook-convert will put the downloaded HTML into the debug/input directory,
where debug is the directory you specified in the ebook-convert --debug-pipeline (page 290) option.
Once the download is complete, you can look at the downloaded HTML by opening the file debug/input/index.
html in a browser. Once you’re satisfied that the download and preprocessing is happening correctly, you can generate
e-books in different formats as shown below:
If you’re satisfied with your recipe, and you feel there is enough demand to justify its inclusion into the set of built-in
recipes, post your recipe in the calibre recipes forum10 to share it with other calibre users.
Note: On macOS, the command line tools are inside the calibre bundle, for example, if you installed calibre in
/Applications the command line tools are in /Applications/calibre.app/Contents/MacOS/.
See also:
ebook-convert (page ??) The command line interface for all e-book conversion.
To learn more about writing advanced recipes using some of the facilities, available in BasicNewsRecipe you
should consult the following sources:
API documentation (page 47) Documentation of the BasicNewsRecipe class and all its important
methods and fields.
BasicNewsRecipe11 The source code of BasicNewsRecipe
Built-in recipes12 The source code for the built-in recipes that come with calibre
The calibre recipes forum13 Lots of knowledgeable calibre recipe writers hang out here.
10 https://www.mobileread.com/forums/forumdisplay.php?f=228
11 https://github.com/kovidgoyal/calibre/blob/master/src/calibre/web/feeds/news.py
12 https://github.com/kovidgoyal/calibre/tree/master/recipes
13 https://www.mobileread.com/forums/forumdisplay.php?f=228
The API for writing recipes is defined by the BasicNewsRecipe (page 47)
class calibre.web.feeds.news.BasicNewsRecipe(options, log, progress_reporter)
Base class that contains logic needed in all recipes. By overriding progressively more of the functionality in
this class, you can make progressively more customized/powerful recipes. For a tutorial introduction to creating
recipes, see Adding your favorite news website (page ??).
abort_article(msg=None)
Call this method inside any of the preprocess methods to abort the download for the current article. Useful
to skip articles that contain inappropriate content, such as pure video articles.
abort_recipe_processing(msg)
Causes the recipe download system to abort the download of this recipe, displaying a simple feedback
message to the user.
add_toc_thumbnail(article, src)
Call this from populate_article_metadata with the src attribute of an <img> tag from the article that is ap-
propriate for use as the thumbnail representing the article in the Table of Contents. Whether the thumbnail
is actually used is device dependent (currently only used by the Kindles). Note that the referenced image
must be one that was successfully downloaded, otherwise it will be ignored.
classmethod adeify_images(soup)
If your recipe when converted to EPUB has problems with images when viewed in Adobe Digital Editions,
call this method from within postprocess_html() (page 50).
canonicalize_internal_url(url, is_link=True)
Return a set of canonical representations of url. The default implementation uses just the server hostname
and path of the URL, ignoring any query parameters, fragments, etc. The canonical representations must
be unique across all URLs for this news source. If they are not, then internal links may be resolved
incorrectly.
Parameters is_link – Is True if the URL is coming from an internal link in an HTML file.
False if the URL is the URL used to download an article.
cleanup()
Called after all articles have been download. Use it to do any cleanup like logging out of subscription sites,
etc.
clone_browser(br)
Clone the browser br. Cloned browsers are used for multi-threaded downloads, since mechanize is not
thread safe. The default cloning routines should capture most browser customization, but if you do some-
thing exotic in your recipe, you should override this method in your recipe and clone manually.
Cloned browser instances use the same, thread-safe CookieJar by default, unless you have customized
cookie handling.
default_cover(cover_file)
Create a generic cover for recipes that don’t have a cover
download()
Download and pre-process all articles from the feeds in this recipe. This method should be called only
once on a particular Recipe instance. Calling it more than once will lead to undefined behavior. :return:
Path to index.html
extract_readable_article(html, url)
Extracts main article content from ‘html’, cleans up and returns as a (article_html, extracted_title) tuple.
Based on the original readability algorithm by Arc90.
get_article_url(article)
Override in a subclass to customize extraction of the URL that points to the content for each article.
Return the article URL. It is called with article, an object representing a parsed article from a feed. See
feedparser14 . By default it looks for the original link (for feeds syndicated via a service like feedburner or
pheedo) and if found, returns that or else returns article.link15 .
get_browser(*args, **kwargs)
Return a browser instance used to fetch documents from the web. By default it returns a mechanize16
browser instance that supports cookies, ignores robots.txt, handles refreshes and has a mozilla firefox user
agent.
If your recipe requires that you login first, override this method in your subclass. For example, the follow-
ing code is used in the New York Times recipe to login for full access:
def get_browser(self):
br = BasicNewsRecipe.get_browser(self)
if self.username is not None and self.password is not None:
br.open('https://www.nytimes.com/auth/login')
br.select_form(name='login')
br['USERID'] = self.username
br['PASSWORD'] = self.password
br.submit()
return br
get_cover_url()
Return a URL to the cover image for this issue or None. By default it returns the value of the member
self.cover_url which is normally None. If you want your recipe to download a cover for the e-book override
this method in your subclass, or set the member variable self.cover_url before this method is called.
get_extra_css()
By default returns self.extra_css. Override if you want to programmatically generate the extra_css.
get_feeds()
Return a list of RSS feeds to fetch for this profile. Each element of the list must be a 2-element tuple of the
form (title, url). If title is None or an empty string, the title from the feed is used. This method is useful if
your recipe needs to do some processing to figure out the list of feeds to download. If so, override in your
subclass.
get_masthead_title()
Override in subclass to use something other than the recipe title
get_masthead_url()
Return a URL to the masthead image for this issue or None. By default it returns the value of the member
self.masthead_url which is normally None. If you want your recipe to download a masthead for the e-book
override this method in your subclass, or set the member variable self.masthead_url before this method is
called. Masthead images are used in Kindle MOBI files.
get_obfuscated_article(url)
If you set articles_are_obfuscated this method is called with every article URL. It should return the path
to a file on the filesystem that contains the article HTML. That file is processed by the recursive HTML
fetching engine, so it can contain links to pages/images on the web.
14 https://pythonhosted.org/feedparser/
15 https://pythonhosted.org/feedparser/reference-entry-link.html
16 https://mechanize.readthedocs.io/en/latest/
This method is typically useful for sites that try to make it difficult to access article content automatically.
classmethod image_url_processor(baseurl, url)
Perform some processing on image urls (perhaps removing size restrictions for dynamically generated
images, etc.) and return the precessed URL.
index_to_soup(url_or_raw, raw=False, as_tree=False, save_raw=None)
Convenience method that takes an URL to the index page and returns a BeautifulSoup17 of it.
url_or_raw: Either a URL or the downloaded index page as a string
is_link_wanted(url, tag)
Return True if the link should be followed or False otherwise. By default, raises NotImplementedError
which causes the downloader to ignore it.
Parameters
• url – The URL to be followed
• tag – The tag from which the URL was derived
parse_feeds()
Create a list of articles from the list of feeds returned by BasicNewsRecipe.get_feeds()
(page 48). Return a list of Feed objects.
parse_index()
This method should be implemented in recipes that parse a website instead of feeds to generate a list
of articles. Typical uses are for news sources that have a “Print Edition” webpage that lists all the
articles in the current print edition. If this function is implemented, it will be used in preference to
BasicNewsRecipe.parse_feeds() (page 49).
It must return a list. Each element of the list must be a 2-element tuple of the form ('feed title',
list of articles).
Each list of articles must contain dictionaries of the form:
{
'title' : article title,
'url' : URL of print version,
'date' : The publication date of the article as a string,
'description' : A summary of the article
'content' : The full article (can be an empty string). Obsolete
do not use, instead save the content to a temporary
file and pass a file:///path/to/temp/file.html as
the URL.
}
For an example, see the recipe for downloading The Atlantic. In addition, you can add ‘author’ for the
author of the article.
If you want to abort processing for some reason and have calibre show the user a simple message instead
of an error, call abort_recipe_processing() (page 47).
populate_article_metadata(article, soup, first)
Called when each HTML page belonging to article is downloaded. Intended to be used to get article
metadata like author/summary/etc. from the parsed HTML (soup).
Parameters
• article – A object of class calibre.web.feeds.Article. If you change the
summary, remember to also change the text_summary
17 https://www.crummy.com/software/BeautifulSoup/bs4/doc
skip_ad_pages(soup)
This method is called with the source of each downloaded HTML file, before any of the cleanup attributes
like remove_tags, keep_only_tags are applied. Note that preprocess_regexps will have already been ap-
plied. It is meant to allow the recipe to skip ad pages. If the soup represents an ad page, return the HTML
of the real page. Otherwise return None.
soup: A BeautifulSoup20 instance containing the downloaded HTML.
18 https://www.crummy.com/software/BeautifulSoup/bs4/doc/
19 https://www.crummy.com/software/BeautifulSoup/bs4/doc/
20 https://www.crummy.com/software/BeautifulSoup/bs4/doc/
sort_index_by(index, weights)
Convenience method to sort the titles in index according to weights. index is sorted in place. Returns index.
index: A list of titles.
weights: A dictionary that maps weights to titles. If any titles in index are not in weights, they are assumed
to have a weight of 0.
classmethod tag_to_string(tag, use_alt=True, normalize_whitespace=True)
Convenience method to take a BeautifulSoup21 Tag and extract the text from it recursively, including any
CDATA sections and alt tag attributes. Return a possibly empty unicode string.
use_alt: If True try to use the alt attribute for tags that don’t have any textual content
tag: BeautifulSoup22 Tag
articles_are_obfuscated = False
Set to True and implement get_obfuscated_article() (page 48) to handle websites that try to
make it difficult to scrape content.
auto_cleanup = False
Automatically extract all the text from downloaded article pages. Uses the algorithms from the readability
project. Setting this to True, means that you do not have to worry about cleaning up the downloaded
HTML manually (though manual cleanup will always be superior).
auto_cleanup_keep = None
Specify elements that the auto cleanup algorithm should never remove. The syntax is a XPath expression.
For example:
center_navbar = True
If True the navigation bar is center aligned, otherwise it is left aligned
compress_news_images = False
Set this to False to ignore all scaling and compression parameters and pass images through unmodified. If
True and the other compression parameters are left at their default values, JPEG images will be scaled to
fit in the screen dimensions set by the output profile and compressed to size at most (w * h)/16 where w x
h are the scaled image dimensions.
compress_news_images_auto_size = 16
The factor used when auto compressing JPEG images. If set to None, auto compression is disabled. Oth-
erwise, the images will be reduced in size to (w * h)/compress_news_images_auto_size bytes if possible
by reducing the quality level, where w x h are the image dimensions in pixels. The minimum JPEG quality
will be 5/100 so it is possible this constraint will not be met. This parameter can be overridden by the
parameter compress_news_images_max_size which provides a fixed maximum size for images. Note that
if you enable scale_news_images_to_device then the image will first be scaled and then its quality lowered
until its size is less than (w * h)/factor where w and h are now the scaled image dimensions. In other
words, this compression happens after scaling.
compress_news_images_max_size = None
Set JPEG quality so images do not exceed the size given (in KBytes). If set, this parameter overrides auto
21 https://www.crummy.com/software/BeautifulSoup/bs4/doc/
22 https://www.crummy.com/software/BeautifulSoup/bs4/doc/
conversion_options = {
'base_font_size' : 16,
'linearize_tables' : True,
}
feeds = None
List of feeds to download. Can be either [url1, url2, ...] or [('title1', url1),
('title2', url2),...]
filter_regexps = []
List of regular expressions that determines which links to ignore. If empty it is ignored. Used only if
is_link_wanted is not implemented. For example:
filter_regexps = [r'ads\.doubleclick\.net']
default.
ignore_duplicate_articles = None
Ignore duplicates of articles that are present in more than one section. A duplicate article is an article that
has the same title and/or URL. To ignore articles with the same title, set this to:
ignore_duplicate_articles = {'title'}
ignore_duplicate_articles = {'url'}
keep_only_tags = []
Keep only the specified tags and their children. For the format for specifying a tag see
BasicNewsRecipe.remove_tags (page 54). If this list is not empty, then the <body> tag will
be emptied and re-filled with the tags that match the entries in this list. For example:
match_regexps = [r'page=[0-9]+']
element tuple. The first element of the tuple should be a compiled regular expression and the second a
callable that takes a single match object and returns a string to replace the match. For example:
preprocess_regexps = [
(re.compile(r'<!--Article ends here-->.*</body>', re.DOTALL|re.IGNORECASE),
lambda match: '</body>'),
]
remove_empty_feeds = False
If True empty feeds are removed from the output. This option has no effect if parse_index is overridden
in the sub class. It is meant only for recipes that return a list of feeds using feeds or get_feeds()
(page 48). It is also used if you use the ignore_duplicate_articles option.
remove_javascript = True
Convenient flag to strip all JavaScript tags from the downloaded HTML
remove_tags = []
List of tags to be removed. Specified tags are removed from downloaded HTML. A tag is specified as a
dictionary of the form:
{
name : 'tag name', #e.g. 'div'
attrs : a dictionary, #e.g. {'class': 'advertisment'}
}
All keys are optional. For a full explanation of the search criteria, see Beautiful Soup23 A common exam-
ple:
This will remove all <div class=”advert”> tags and all their children from the downloaded HTML.
remove_tags_after = None
Remove all tags that occur after the specified tag. For the format for specifying a tag see
BasicNewsRecipe.remove_tags (page 54). For example:
remove_tags_after = [dict(id='content')]
will remove all tags after the first element with id=”content”.
23 https://www.crummy.com/software/BeautifulSoup/bs4/doc/#searching-the-tree
remove_tags_before = None
Remove all tags that occur before the specified tag. For the format for specifying a tag see
BasicNewsRecipe.remove_tags (page 54). For example:
remove_tags_before = dict(id='content')
will remove all tags before the first element with id=”content”.
requires_version = (0, 6, 0)
Minimum calibre version needed to use this recipe
resolve_internal_links = False
If set to True then links in downloaded articles that point to other downloaded articles are changed to point
to the downloaded copy of the article rather than its original web URL. If you set this to True, you might
also need to implement canonicalize_internal_url() (page 47) to work with the URL scheme
of your particular website.
reverse_article_order = False
Reverse the order of articles in each feed
scale_news_images = None
Maximum dimensions (w,h) to scale images to. If scale_news_images_to_device is True this is set to the
device screen dimensions set by the output profile unless there is no profile set, in which case it is left at
whatever value it has been assigned (default None).
scale_news_images_to_device = True
Rescale images to fit in the device screen dimensions set by the output profile. Ignored if no output profile
is set.
simultaneous_downloads = 5
Number of simultaneous downloads. Set to 1 if the server is picky. Automatically reduced to 1 if
BasicNewsRecipe.delay (page 52) > 0
summary_length = 500
Max number of characters in the short description
template_css = u'\n .article_date {\n color: gray; font-family: monospace;\n }\n\n .a
The CSS that is used to style the templates, i.e., the navigation bars and the Tables of Contents. Rather
than overriding this variable, you should use extra_css in your recipe to customize look and feel.
timefmt = u' [%a, %d %b %Y]'
The format string for the date shown on the first page. By default: Day_Name, Day_Number Month_Name
Year
timeout = 120.0
Timeout for fetching files from server in seconds
title = u'Unknown News Source'
The title to use for the e-book
use_embedded_content = None
Normally we try to guess if a feed has full articles embedded in it based on the length of the embedded
content. If None, then the default guessing is used. If True then the we always assume the feeds has
embedded content and if False we always assume the feed does not have embedded content.
calibre includes a built-in E-book viewer that can view all the major e-book formats. The E-book viewer is highly
customizable and has many advanced features.
You can view any of the books in your calibre library by selecting the book and pressing the View button. This will
open up the book in the E-book viewer. You can also launch the E-book viewer by itself from the Start menu in
Windows. On macOS, you can pin it to the dock and launch it from there. On Linux you can use its launcher in the
desktop menus or run the command ebook-viewer.
57
calibre User Manual, Release 4.21.0
3.2.1 Bookmarks
When you are in the middle of a book and close the viewer, it will remember where you stopped reading and return
there the next time you open the book. You can also set bookmarks in the book by using the Bookmarks button in the
viewer controls or pressing ctrl+b. When viewing EPUB format books, these bookmarks are actually saved in the
EPUB file itself. You can add bookmarks, then send the file to a friend. When they open the file, they will be able to
see your bookmarks. You can turn off this behavior in the Miscellaneous section of the viewer preferences.
If the book you are reading defines a Table of Contents, you can access it by pressing the Table of Contents button.
This will bring up a list of sections in the book. You can click on any of them to jump to that portion of the book.
E-books, unlike paper books, have no concept of pages. You can refer to precise locations in e-books using the Go
to→Location functionality in the viewer controls.
You can use this location information to unambiguously refer to parts of the books when discussing it with friends or
referring to it in other works. You can enter these locations under Go to→Location in the viewer controls.
If you click on links inside the e-book to take you to different parts of the book, such as an endnote, you can use the
Back and Forward buttons in the top left corner of the viewer controls. These buttons behave just like those in a web
browser.
calibre also has a very handy Reference mode. You can turn it on by clicking the Reference mode button in the viewer
controls. Once you do this, every mouse over a paragraph, calibre will display a unique number made up of the section
and paragraph numbers.
You can use this number to unambiguously refer to parts of the books when discussing it with friends or referring to it
in other works. You can enter these numbers in the Go to function to navigate to a particular reference location.
You can change font sizes on the fly by using Font size in the viewer controls or Ctrl++ or Ctrl+- or holding the
Ctrl key and using the mouse wheel.
You can look up the meaning of words in the current book by opening the Lookup/search word panel via the viewer
controls. Then simply double click on any word and its definition will be displayed in the Lookup panel.
You can select text and images by dragging the content with your mouse and then right clicking and selecting Copy to
copy to the clipboard. The copied material can be pasted into another application as plain text and images.
You can zoom in to show an image at full size in a separate window by either double clicking or long tapping on it.
You can also right click on it and choose View image.
Some books have very wide content that content be broken up at page boundaries. For example tables or <pre> tags.
In such cases, you should switch the viewer to flow mode by pressing Ctrl+m to read this content. Alternately, you
can also add the following CSS to the Styles section of the viewer preferences to force the viewer to break up lines of
text in <pre> tags:
24 https://www.mobileread.com/forums/showthread.php?t=51500
E-book conversion
calibre has a conversion system that is designed to be very easy to use. Normally, you just add a book to calibre, click
convert and calibre will try hard to generate output that is as close as possible to the input. However, calibre accepts
a very large number of input formats, not all of which are as suitable as others for conversion to e-books. In the case
of such input formats, or if you just want greater control over the conversion system, calibre has a lot of options to
fine tune the conversion process. Note however that calibre’s conversion system is not a substitute for a full blown
e-book editor. To edit e-books, I recommend first converting them to EPUB or AZW3 using calibre and then using the
Edit book feature to get them into perfect shape. You can then use the edited e-book as input for conversion into other
formats in calibre.
This document will refer mainly to the conversion settings as found in the conversion dialog, pictured below. All
these settings are also available via command line interface to conversion, documented at ebook-convert (page ??). In
calibre, you can obtain help on any individual setting by holding your mouse over it, a tooltip will appear describing
the setting.
61
calibre User Manual, Release 4.21.0
Contents
4.1 Introduction
The first thing to understand about the conversion system is that it is designed as a pipeline. Schematically, it looks
like this:
The input format is first converted to XHTML by the appropriate Input plugin. This HTML is then transformed. In
the last step, the processed XHTML is converted to the specified output format by the appropriate Output plugin. The
results of the conversion can vary greatly, based on the input format. Some formats convert much better than others.
A list of the best source formats for conversion is available here (page 130).
The transforms that act on the XHTML output are where all the work happens. There are various transforms, for
example, to insert book metadata as a page at the start of the book, to detect chapter headings and automatically create
a Table of Contents, to proportionally adjust font sizes, et cetera. It is important to remember that all the transforms
act on the XHTML output by the Input plugin, not on the input file itself. So, for example, if you ask calibre to
convert an RTF file to EPUB, it will first be converted to XHTML internally, the various transforms will be applied
to the XHTML and then the Output plugin will create the EPUB file, automatically generating all metadata, Table of
Contents, et cetera.
4.1. Introduction 63
calibre User Manual, Release 4.21.0
You can see this process in action by using the debug option . Just specify the path to a directory for
the debug output. During conversion, calibre will place the XHTML generated by the various stages of the conversion
pipeline in different sub-directories. The four sub-directories are:
If you want to edit the input document a little before having calibre convert it, the best thing to do is edit the files in
the input sub-directory, then zip it up, and use the ZIP file as the input format for subsequent conversions. To do this
use the Edit meta information dialog to add the ZIP file as a format for the book and then, in the top left corner of the
conversion dialog, select ZIP as the input format.
This document will deal mainly with the various transforms that operate on the intermediate XHTML and how to
control them. At the end are some tips specific to each input/output format.
Contents
This group of options controls various aspects of the look and feel of the converted e-book.
4.2.1 Fonts
One of the nicest features of the e-reading experience is the ability to easily adjust font sizes to suit individual needs
and lighting conditions. calibre has sophisticated algorithms to ensure that all the books it outputs have a consistent
font sizes, no matter what font sizes are specified in the input document.
The base font size of a document is the most common font size in that document, i.e., the size of the bulk of text
in that document. When you specify a Base font size, calibre automatically rescales all font sizes in the document
proportionately, so that the most common font size becomes the specified base font size and other font sizes are
rescaled appropriately. By choosing a larger base font size, you can make the fonts in the document larger and vice
versa. When you set the base font size, for best results, you should also set the font size key.
Normally, calibre will automatically choose a base font size appropriate to the output profile you have chosen (see
Page setup (page 67)). However, you can override this here in case the default is not suitable for you.
The Font size key option lets you control how non-base font sizes are rescaled. The font rescaling algorithm works
using a font size key, which is simply a comma-separated list of font sizes. The font size key tells calibre how many
“steps” bigger or smaller a given font size should be compared to the base font size. The idea is that there should
be a limited number of font sizes in a document. For example, one size for the body text, a couple of sizes for
different levels of headings and a couple of sizes for super/sub scripts and footnotes. The font size key allows calibre
to compartmentalize the font sizes in the input documents into separate “bins” corresponding to the different logical
font sizes.
Let’s illustrate with an example. Suppose the source document we are converting was produced by someone with
excellent eyesight and has a base font size of 8pt. That means the bulk of the text in the document is sized at 8pts,
while headings are somewhat larger (say 10 and 12pt) and footnotes somewhat smaller at 6pt. Now if we use the
following settings:
The output document will have a base font size of 12pt, headings of 14 and 16pt and footnotes of 8pt. Now suppose
we want to make the largest heading size stand out more and make the footnotes a little larger as well. To achieve this,
the font key should be changed to:
The largest headings will now become 18pt, while the footnotes will become 9pt. You can play with these settings
to try and figure out what would be optimum for you by using the font rescaling wizard, which can be accessed by
clicking the little button next to the Font size key setting.
All the font size rescaling in the conversion can also be disabled here, if you would like to preserve the font sizes in
the input document.
A related setting is Line height. Line height controls the vertical height of lines. By default, (a line height of 0), no
manipulation of line heights is performed. If you specify a non-default value, line heights will be set in all locations
that don’t specify their own line heights. However, this is something of a blunt weapon and should be used sparingly.
If you want to adjust the line heights for some section of the input, it’s better to use the Extra CSS (page 66).
In this section you can also tell calibre to embed any referenced fonts into the book. This will allow the fonts to work
on reader devices even if they are not available on the device.
4.2.2 Text
Text can be either justified or not. Justified text has extra spaces between words to give a smooth right margin. Some
people prefer justified text, others do not. Normally, calibre will preserve the justification in the original document. If
you want to override it you can use the Text justification option in this section.
You can also tell calibre to Smarten punctuation which will replace plain quotes, dashes and ellipses with their typo-
graphically correct alternatives. Note that this algorithm is not perfect so it is worth reviewing the results. The reverse,
namely, Unsmarted punctuation is also available.
Finally, there is Input character encoding. Older documents sometimes don’t specify their character encoding. When
converted, this can result in non-English characters or special characters like smart quotes being corrupted. calibre
tries to auto-detect the character encoding of the source document, but it does not always succeed. You can force it to
assume a particular character encoding by using this setting. cp1252 is a common encoding for documents produced
using Windows software. You should also read How do I convert my file containing non-English characters, or smart
quotes? (page 130) for more on encoding issues.
4.2.3 Layout
Normally, paragraphs in XHTML are rendered with a blank line between them and no leading text indent. calibre has
a couple of options to control this. Remove spacing between paragraphs forcefully ensure that all paragraphs have no
inter paragraph spacing. It also sets the text indent to 1.5em (can be changed) to mark the start of every paragraph.
Insert blank line does the opposite, guaranteeing that there is exactly one blank line between each pair of paragraphs.
Both these options are very comprehensive, removing spacing, or inserting it for all paragraphs (technically <p> and
<div> tags). This is so that you can just set the option and be sure that it performs as advertised, irrespective of how
messy the input file is. The one exception is when the input file uses hard line breaks to implement inter-paragraph
spacing.
If you want to remove the spacing between all paragraphs, except a select few, don’t use these options. Instead add the
following CSS code to Extra CSS (page 66):
Then, in your source document, mark the paragraphs that need spacing with class=”spacious”. If your input document
is not in HTML, use the Debug option, described in the Introduction to get HTML (use the input sub-directory).
Another useful options is Linearize tables. Some badly designed documents use tables to control the layout of text
on the page. When converted these documents often have text that runs off the page and other artifacts. This option
will extract the content from the tables and present it in a linear fashion. Note that this option linearizes all tables,
so only use it if you are sure the input document does not use tables for legitimate purposes, like presenting tabular
information.
4.2.4 Styling
The Extra CSS option allows you to specify arbitrary CSS that will be applied to all HTML files in the input. This
CSS is applied with very high priority and so should override most CSS present in the input document itself. You
can use this setting to fine tune the presentation/layout of your document. For example, if you want all paragraphs of
class endnote to be right aligned, just add:
p { text-indent: 5mm; }
Extra CSS is a very powerful option, but you do need an understanding of how CSS works to use it to its full potential.
You can use the debug pipeline option described above to see what CSS is present in your input document.
A simpler option is to use Filter style information. This allows you to remove all CSS properties of the specified types
from the document. For example, you can use it to remove all colors or fonts.
This is the most powerful styling related facility. You can use it to define rules that change styles based on various
conditions. For example you can use it to change all green colors to blue, or remove all bold styling from the text or
color all headings a certain color, etc.
The Page setup options are for controlling screen layout, like margins and screen sizes. There are options to setup page
margins, which will be used by the output plugin, if the selected output format supports page margins. In addition,
you should choose an Input profile and an output profile. Both sets of profiles basically deal with how to interpret
measurements in the input/output documents, screen sizes and default font rescaling keys.
If you know that the file you are converting was intended to be used on a particular device/software platform, choose
the corresponding input profile, otherwise just choose the default input profile. If you know the files you are producing
are meant for a particular device type, choose the corresponding output profile. In particular, for MOBI output files,
you should choose the Kindle, for LIT the Microsoft Reader and for EPUB the Sony Reader. In the case of EPUB,
the Sony Reader profile will result in EPUB files that will work everywhere. However, it has some side effects, like
inserting artificial section breaks to keep internal components below the size threshold, needed for SONY devices. In
particular for the iPhone/Android phones, choose the SONY output profile. If you know your EPUB files will not be
read on a SONY or similar device, use the default output profile. If you are producing MOBI files that are not intended
for the Kindle, choose the Mobipocket books output profile.
The output profile also controls the screen size. This will cause, for example, images to be auto-resized to be fit to the
screen in some output formats. So choose a profile of a device that has a screen size similar to your device.
Heuristic processing provides a variety of functions which can be used to try and detect and correct common problems
in poorly formatted input documents. Use these functions if your input document suffers from poor formatting.
Because these functions rely on common patterns, be aware that in some cases an option may lead to worse results,
so use with care. As an example, several of these options will remove all non-breaking-space entities, or may include
false positive matches relating to the function.
Enable heuristic processing This option activates calibre’s Heuristic processing stage of the conversion pipeline.
This must be enabled in order for various sub-functions to be applied
Unwrap lines Enabling this option will cause calibre to attempt to detect and correct hard line breaks that exist within
a document using punctuation clues and line length. calibre will first attempt to detect whether hard line breaks
exist, if they do not appear to exist calibre will not attempt to unwrap lines. The line-unwrap factor can be
reduced if you want to ‘force’ calibre to unwrap lines.
Line-unwrap factor This option controls the algorithm calibre uses to remove hard line breaks. For example, if the
value of this option is 0.4, that means calibre will remove hard line breaks from the end of lines whose lengths
are less than the length of 40% of all lines in the document. If your document only has a few line breaks which
need correction, then this value should be reduced to somewhere between 0.1 and 0.2.
Detect and markup unformatted chapter headings and sub headings If your document does not have chapter head-
ings and titles formatted differently from the rest of the text, calibre can use this option to attempt detection
them and surround them with heading tags. <h2> tags are used for chapter headings; <h3> tags are used for any
titles that are detected.
This function will not create a TOC, but in many cases it will cause calibre’s default chapter detection settings
to correctly detect chapters and build a TOC. Adjust the XPath under Structure detection if a TOC is not au-
tomatically created. If there are no other headings used in the document then setting “//h:h2” under Structure
detection would be the easiest way to create a TOC for the document.
The inserted headings are not formatted, to apply formatting use the Extra CSS option under the Look and Feel
conversion settings. For example, to center heading tags, use the following:
Renumber sequences of <h1> or <h2> tags Some publishers format chapter headings using multiple <h1> or <h2>
tags sequentially. calibre’s default conversion settings will cause such titles to be split into two pieces. This
option will re-number the heading tags to prevent splitting.
Delete blank lines between paragraphs This option will cause calibre to analyze blank lines included within the doc-
ument. If every paragraph is interleaved with a blank line, then calibre will remove all those blank paragraphs.
Sequences of multiple blank lines will be considered scene breaks and retained as a single paragraph. This op-
tion differs from the ‘Remove Paragraph Spacing’ option under ‘Look and Feel’ in that it actually modifies the
HTML content, while the other option modifies the document styles. This option can also remove paragraphs
which were inserted using calibre’s ‘Insert blank line’ option.
Ensure scene breaks are consistently formatted With this option calibre will attempt to detect common scene-break
markers and ensure that they are center aligned. ‘Soft’ scene break markers, i.e. scene breaks only defined by
extra white space, are styled to ensure that they will not be displayed in conjunction with page breaks.
Replace scene breaks If this option is configured then calibre will replace scene break markers it finds with the re-
placement text specified by the user. Please note that some ornamental characters may not be supported across
all reading devices.
In general you should avoid using HTML tags, calibre will discard any tags and use pre-defined markup. <hr
/> tags, i.e. horizontal rules, and <img> tags are exceptions. Horizontal rules can optionally be specified
with styles, if you choose to add your own style be sure to include the ‘width’ setting, otherwise the style
information will be discarded. Image tags can used, but calibre does not provide the ability to add the image
during conversion, this must be done after the fact using the ‘Edit book’ feature.
Example image tag (place the image within an ‘Images’ folder inside the EPUB after conversion):
<img style=”width:10%” src=”../Images/scenebreak.png” />
Example horizontal rule with styles: <hr style=”width:20%;padding-top: 1px;border-top: 2px
ridge black;border-bottom: 2px groove black;”/>
Remove unnecessary hyphens calibre will analyze all hyphenated content in the document when this option is en-
abled. The document itself is used as a dictionary for analysis. This allows calibre to accurately remove hyphens
for any words in the document in any language, along with made-up and obscure scientific words. The primary
drawback is words appearing only a single time in the document will not be changed. Analysis happens in
two passes, the first pass analyzes line endings. Lines are only unwrapped if the word exists with or without a
hyphen in the document. The second pass analyzes all hyphenated words throughout the document, hyphens are
removed if the word exists elsewhere in the document without a match.
Italicize common words and patterns When enabled, calibre will look for common words and patterns that denote
italics and italicize them. Examples are common text conventions such as ~word~ or phrases that should gener-
ally be italicized, e.g. latin phrases like ‘etc.’ or ‘et cetera’.
Replace entity indents with CSS indents Some documents use a convention of defining text indents using non-
breaking space entities. When this option is enabled calibre will attempt to detect this sort of formatting and
convert them to a 3% text indent using CSS.
These options are useful primarily for conversion of PDF documents or OCR conversions, though they can also be
used to fix many document specific problems. As an example, some conversions can leaves behind page headers and
footers in the text. These options use regular expressions to try and detect headers, footers, or other arbitrary text
and remove or replace them. Remember that they operate on the intermediate XHTML produced by the conversion
pipeline. There is a wizard to help you customize the regular expressions for your document. Click the magic wand
beside the expression box, and click the ‘Test’ button after composing your search expression. Successful matches
will be highlighted in Yellow.
The search works by using a Python regular expression. All matched text is simply removed from the document or
replaced using the replacement pattern. The replacement pattern is optional, if left blank then text matching the search
pattern will be deleted from the document. You can learn more about regular expressions and their syntax at All about
using regular expressions in calibre (page 192).
Structure detection involves calibre trying its best to detect structural elements in the input document, when they are
not properly specified. For example, chapters, page breaks, headers, footers, etc. As you can imagine, this process
varies widely from book to book. Fortunately, calibre has very powerful options to control this. With power comes
complexity, but if once you take the time to learn the complexity, you will find it well worth the effort.
calibre has two sets of options for chapter detection and inserting page breaks. This can sometimes be slightly
confusing, as by default, calibre will insert page breaks before detected chapters as well as the locations detected by
the page breaks option. The reason for this is that there are often location where page breaks should be inserted that are
not chapter boundaries. Also, detected chapters can be optionally inserted into the auto generated Table of Contents.
calibre uses XPath, a powerful language to allow the user to specify chapter boundaries/page breaks. XPath can seem
a little daunting to use at first, fortunately, there is a XPath tutorial (page 157) in the User Manual. Remember that
Structure detection operates on the intermediate XHTML produced by the conversion pipeline. Use the debug option
described in the Introduction (page 63) to figure out the appropriate settings for your book. There is also a button for
a XPath wizard to help with the generation of simple XPath expressions.
By default, calibre uses the following expression for chapter detection:
This expression is rather complex, because it tries to handle a number of common cases simultaneously. What it means
is that calibre will assume chapters start at either <h1> or <h2> tags that have any of the words (chapter, book, section
or part) in them or that have the class=”chapter” attribute.
A related option is Chapter mark, which allows you to control what calibre does when it detects a chapter. By default,
it will insert a page break before the chapter. You can have it insert a ruled line instead of, or in addition to the page
break. You can also have it do nothing.
The default setting for detecting page breaks is:
//*[name()='h1' or name()='h2']
which means that calibre will insert page breaks before every <h1> and <h2> tag by default.
Note: The default expressions may change depending on the input format you are converting.
4.6.2 Miscellaneous
single page with all this metadata and insert it into the converted e-book, typically just after the cover. Think of
it as a way to create your own customised book jacket.
Remove first image Sometimes, the source document you are converting includes the cover as part of the book, instead
of as a separate cover. If you also specify a cover in calibre, then the converted book will have two covers. This
option will simply remove the first image from the source document, thereby ensuring that the converted book
has only one cover, the one specified in calibre.
When the input document has a Table of Contents in its metadata, calibre will just use that. However, a number of
older formats either do not support a metadata based Table of Contents, or individual documents do not have one.
In these cases, the options in this section can help you automatically generate a Table of Contents in the converted
e-book, based on the actual content in the input document.
Note: Using these options can be a little challenging to get exactly right. If you prefer creating/editing the Table
of Contents by hand, convert to the EPUB or AZW3 formats and select the checkbox at the bottom of the Table of
Contents section of the conversion dialog that says Manually fine-tune the Table of Contents after conversion. This
will launch the ToC Editor tool after the conversion. It allows you to create entries in the Table of Contents by simply
clicking the place in the book where you want the entry to point. You can also use the ToC Editor by itself, without
doing a conversion. Go to Preferences→Interface→Toolbars and add the ToC Editor to the main toolbar. Then just
select the book you want to edit and click the ToC Editor button.
The first option is Force use of auto-generated Table of Contents. By checking this option you can have calibre override
any Table of Contents found in the metadata of the input document with the auto generated one.
The default way that the creation of the auto generated Table of Contents works is that, calibre will first try to add any
detected chapters to the generated table of contents. You can learn how to customize the detection of chapters in the
Structure detection (page 69) section above. If you do not want to include detected chapters in the generated table of
contents, check the Do not add detected chapters option.
If less than the Chapter threshold number of chapters were detected, calibre will then add any hyperlinks it finds in the
input document to the Table of Contents. This often works well many input documents include a hyperlinked Table of
Contents right at the start. The Number of links option can be used to control this behavior. If set to zero, no links are
added. If set to a number greater than zero, at most that number of links is added.
calibre will automatically filter duplicates from the generated Table of Contents. However, if there are some additional
undesirable entries, you can filter them using the TOC Filter option. This is a regular expression that will match the
title of entries in the generated table of contents. Whenever a match is found, it will be removed. For example, to
remove all entries titles “Next” or “Previous” use:
Next|Previous
The Level 1,2,3 TOC options allow you to create a sophisticated multi-level Table of Contents. They are XPath
expressions that match tags in the intermediate XHTML produced by the conversion pipeline. See the Introduction
(page 63) for how to get access to this XHTML. Also read the XPath tutorial (page 157), to learn how to construct
XPath expressions. Next to each option is a button that launches a wizard to help with the creation of basic XPath
expressions. The following simple example illustrates how to use these options.
Suppose you have an input document that results in XHTML that look like this:
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Sample document</title>
(continues on next page)
This will result in an automatically generated two level Table of Contents that looks like:
Chapter 1
Section 1.1
Section 1.2
Chapter 2
Section 2.1
Warning: Not all output formats support a multi level Table of Contents. You should first try with EPUB output.
If that works, then try your format of choice.
4.8 Using images as chapter titles when converting HTML input doc-
uments
Suppose you want to use an image as your chapter title, but still want calibre to be able to automatically generate a
Table of Contents for you from the chapter titles. Use the following HTML markup to achieve this
<html>
<body>
<h2>Chapter 1</h2>
<p>chapter 1 text...</p>
<h2 title="Chapter 2"><img src="chapter2.jpg" /></h2>
<p>chapter 2 text...</p>
</body>
</html>
Set the Level 1 TOC setting to //h:h2. Then, for chapter two, calibre will take the title from the value of the title
attribute on the <h2> tag, since the tag has no text.
4.8. Using images as chapter titles when converting HTML input documents 71
calibre User Manual, Release 4.21.0
4.9 Using tag attributes to supply the text for entries in the Table of
Contents
If you have particularly long chapter titles and want shortened versions in the Table of Contents, you can use the title
attribute to achieve this, for example:
<html>
<body>
<h2 title="Chapter 1">Chapter 1: Some very long title</h2>
<p>chapter 1 text...</p>
<h2 title="Chapter 2">Chapter 2: Some other very long title</h2>
<p>chapter 2 text...</p>
</body>
</html>
Set the Level 1 TOC setting to //h:h2/@title. Then calibre will take the title from the value of the title attribute
on the <h2> tags, instead of using the text inside the tag. Note the trailing /@title on the XPath expression, you
can use this form to tell calibre to get the text from any attribute you like.
There are two places where conversion options can be set in calibre. The first is in Preferences->Conversion. These
settings are the defaults for the conversion options. Whenever you try to convert a new book, the settings set here will
be used by default.
You can also change settings in the conversion dialog for each book conversion. When you convert a book, calibre
remembers the settings you used for that book, so that if you convert it again, the saved settings for the individual book
will take precedence over the defaults set in Preferences. You can restore the individual settings to defaults by using
the Restore defaults button in the individual book conversion dialog. You can remove the saved settings for a group of
books by selecting all the books and then clicking the Edit metadata button to bring up the bulk metadata edit dialog,
near the bottom of the dialog is an option to remove stored conversion settings.
When you bulk convert a set of books, settings are taken in the following order (last one wins):
• From the defaults set in Preferences->Conversion
• From the saved conversion settings for each book being converted (if any). This can be turned off by the option
in the top left corner of the Bulk conversion dialog.
• From the settings set in the Bulk conversion dialog
Note that the final settings for each book in a Bulk conversion will be saved and re-used if the book is converted again.
Since the highest priority in Bulk Conversion is given to the settings in the Bulk conversion dialog, these will override
any book specific settings. So you should only bulk convert books together that need similar settings. The exceptions
are metadata and input format specific settings. Since the Bulk conversion dialog does not have settings for these two
categories, they will be taken from book specific settings (if any) or the defaults.
Note: You can see the actual settings used during any conversion by clicking the rotating icon in the lower right
corner and then double clicking the individual conversion job. This will bring up a conversion log that will contain the
actual settings used, near the top.
Here you will find tips specific to the conversion of particular formats. Options specific to particular format, whether
input or output are available in the conversion dialog under their own section, for example TXT input or EPUB output.
calibre can automatically convert .docx files created by Microsoft Word 2007 and newer. Just add the file to calibre
and click convert.
Note: There is a demo .docx file25 that demonstrates the capabilities of the calibre conversion engine. Just download
it and convert it to EPUB or AZW3 to see what calibre can do.
calibre will automatically generate a Table of Contents based on headings if you mark your headings with the
Heading 1, Heading 2, etc. styles in Microsoft Word. Open the output e-book in the calibre E-book viewer
and click the Table of Contents button to view the generated Table of Contents.
For older .doc files, you can save the document as HTML with Microsoft Word and then convert the resulting HTML
file with calibre. When saving as HTML, be sure to use the “Save as Web Page, Filtered” option as this will produce
clean HTML that will convert well. Note that Word produces really messy HTML, converting it can take a long time,
so be patient. If you have a newer version of Word available, you can directly save it as docx as well.
Another alternative is to use the free OpenOffice. Open your .doc file in OpenOffice and save it in OpenOffice’s format
.odt. calibre can directly convert .odt files.
TXT documents have no well defined way to specify formatting like bold, italics, etc, or document structure like
paragraphs, headings, sections and so on, but there are a variety of conventions commonly used. By default calibre
attempts automatic detection of the correct formatting and markup based on those conventions.
TXT input supports a number of options to differentiate how paragraphs are detected.
Paragraph style: Auto Analyzes the text file and attempts to automatically determine how paragraphs
are defined. This option will generally work fine, if you achieve undesirable results try one of the
manual options.
Paragraph style: Block Assumes one or more blank lines are a paragraph boundary:
This is the
second paragraph.
25 https://calibre-ebook.com/downloads/demos/demo.docx
Paragraph style: Print Assumes that every paragraph starts with an indent (either a tab or 2+ spaces).
Paragraphs end when the next line that starts with an indent is reached:
This is the
first.
This is the second.
This is the
third.
Paragraph style: Unformatted Assumes that the document has no formatting, but does use hard line
breaks. Punctuation and median line length are used to attempt to re-create paragraphs.
Formatting style: Auto Attempts to detect the type of formatting markup being used. If no markup is
used then heuristic formatting will be applied.
Formatting style: Heuristic Analyzes the document for common chapter headings, scene breaks, and
italicized words and applies the appropriate HTML markup during conversion.
Formatting style: Markdown calibre also supports running TXT input though a transformation prepro-
cessor known as Markdown. Markdown allows for basic formatting to be added to TXT documents,
such as bold, italics, section headings, tables, lists, a Table of Contents, etc. Marking chapter head-
ings with a leading # and setting the chapter XPath detection expression to “//h:h1” is the easiest
way to have a proper table of contents generated from a TXT document. You can learn more about
the Markdown syntax at daringfireball26 .
Formatting style: None Applies no special formatting to the text, the document is converted to HTML
with no other changes.
PDF documents are one of the worst formats to convert from. They are a fixed page size and text placement format.
Meaning, it is very difficult to determine where one paragraph ends and another begins. calibre will try to unwrap
paragraphs using a configurable, Line Un-Wrapping Factor. This is a scale used to determine the length at which a
line should be unwrapped. Valid values are a decimal between 0 and 1. The default is 0.45, just under the median line
length. Lower this value to include more text in the unwrapping. Increase to include less. You can adjust this value in
the conversion settings under PDF Input.
Also, they often have headers and footers as part of the document that will become included with the text. Use the
Search and Replace panel to remove headers and footers to mitigate this issue. If the headers and footers are not
removed from the text it can throw off the paragraph unwrapping. To learn how to use the header and footer removal
options, read All about using regular expressions in calibre (page 192).
Some limitations of PDF input are:
• Complex, multi-column, and image based documents are not supported.
• Extraction of vector images and tables from within the document is also not supported.
• Some PDFs use special glyphs to represent ll or ff or fi, etc. Conversion of these may or may not work depending
on just how they are represented internally in the PDF.
• Links and Tables of Contents are not supported
• PDFs that use embedded non-unicode fonts to represent non-English characters will result in garbled output for
those characters
26 https://daringfireball.net/projects/markdown/syntax
• Some PDFs are made up of photographs of the page with OCRed text behind them. In such cases calibre uses
the OCRed text, which can be very different from what you see when you view the PDF file
• PDFs that are used to display complex text, like right to left languages and math typesetting will not convert
correctly
To re-iterate PDF is a really, really bad format to use as input. If you absolutely must use PDF, then be prepared for
an output ranging anywhere from decent to unusable, depending on the input PDF.
A comic book collection is a .cbc file. A .cbc file is a ZIP file that contains other CBZ/CBR files. In addition the .cbc
file must contain a simple text file called comics.txt, encoded in UTF-8. The comics.txt file must contain a list of the
comics files inside the .cbc file, in the form filename:title, as shown below:
one.cbz:Chapter One
two.cbz:Chapter Two
three.cbz:Chapter Three
calibre will automatically convert this .cbc file into a e-book with a Table of Contents pointing to each entry in
comics.txt.
Various advanced formatting for EPUB files is demonstrated in this demo file27 . The file was created from hand coded
HTML using calibre and is meant to be used as a template for your own EPUB creation efforts.
The source HTML it was created from is available demo.zip28 . The settings used to create the EPUB from the ZIP file
are:
ebook-convert demo.zip .epub -vv --authors "Kovid Goyal" --language en --level1-toc '/
˓→/*[@class="title"]' --disable-font-rescaling --page-breaks-before / --no-default-
˓→epub-cover
Note that because this file explores the potential of EPUB, most of the advanced formatting is not going to work on
readers less capable than calibre’s built-in EPUB viewer.
calibre can directly convert ODT (OpenDocument Text) files. You should use styles to format your document and
minimize the use of direct formatting. When inserting images into your document you need to anchor them to the
paragraph, images anchored to a page will all end up in the front of the conversion.
To enable automatic detection of chapters, you need to mark them with the build-in styles called ‘Heading 1’, ‘Heading
2’, . . . , ‘Heading 6’ (‘Heading 1’ equates to the HTML tag <h1>, ‘Heading 2’ to <h2> etc). When you convert in
calibre you can enter which style you used into the ‘Detect chapters at’ box. Example:
27 https://calibre-ebook.com/downloads/demos/demo.epub
28 https://calibre-ebook.com/downloads/demos/demo.zip
• If you mark Chapters with style ‘Heading 2’, you have to set the ‘Detect chapters at’ box to //h:h2
• For a nested TOC with Sections marked with ‘Heading 2’ and the Chapters marked with ‘Heading 3’ you need
to enter //h:h2|//h:h3. On the Convert - TOC page set the ‘Level 1 TOC’ box to //h:h2 and the ‘Level
2 TOC’ box to //h:h3.
Well-known document properties (Title, Keywords, Description, Creator) are recognized and calibre will use the first
image (not to small, and with good aspect-ratio) as the cover image.
There is also an advanced property conversion mode, which is activated by setting the custom property opf.
metadata (‘Yes or No’ type) to Yes in your ODT document (File->Properties->Custom Properties). If this property
is detected by calibre, the following custom properties are recognized (opf.authors overrides document creator):
opf.titlesort
opf.authors
opf.authorsort
opf.publisher
opf.pubdate
opf.isbn
opf.language
opf.series
opf.seriesindex
In addition to this, you can specify the picture to use as the cover by naming it opf.cover (right click, Picture-
>Options->Name) in the ODT. If no picture with this name is found, the ‘smart’ method is used. As the cover
detection might result in double covers in certain output formats, the process will remove the paragraph (only if the
only content is the cover!) from the document. But this works only with the named picture!
To disable cover detection you can set the custom property opf.nocover (‘Yes or No’ type) to Yes in advanced
mode.
The first, most important, setting to decide on when converting to PDF is the page size. By default, calibre uses a
page size of “U.S. Letter”. You can change this to another standard page size or a completely custom size in the PDF
Output section of the conversion dialog. If you are generating a PDF to be used on a specific device, you can turn on
the option to use the page size from the output profile instead. So if your output profile is set to Kindle, calibre will
create a PDF with page size suitable for viewing on the small kindle screen.
You can insert arbitrary headers and footers on each page of the PDF by specifying header and footer templates.
Templates are just snippets of HTML code that get rendered in the header and footer locations. For example, to
display page numbers centered at the bottom of every page, in green, use the following footer template:
calibre will automatically replace _PAGENUM_ with the current page number. You can even put different content on
even and odd pages, for example the following header template will show the title on odd pages and the author on even
pages:
calibre will automatically replace _TITLE_ and _AUTHOR_ with the title and author of the document being con-
verted. Setting justify-content to flex-end will cause the text to be right aligned.
You can also display text at the left and right edges and change the font size, as demonstrated with this header template:
This will display the title at the left and the author at the right, in a font size smaller than the main text.
You can also use the current section in templates, as shown below:
<header><div>_SECTION_</div></header>
_SECTION_ is replaced by whatever the name of the current section is. These names are taken from the metadata
Table of Contents in the document (the PDF Outline). If the document has no table of contents then it will be replaced
by empty text. If a single PDF page has multiple sections, the first section on the page will be used. Similarly, there is
a variable named _TOP_LEVEL_SECTION_ that can be used to get the name of the current top-level section.
You can even use JavaScript inside the header and footer templates, for example, the following template will cause
page numbers to start at 4 instead of 1:
<footer>
<div></div>
<script>document.currentScript.parentNode.querySelector("div").innerHTML = "" + (_
˓→PAGENUM_ + 3)</script>
</footer>
Note: When adding headers and footers make sure you set the page top and bottom margins to large enough values,
under the PDF Output section of the conversion dialog.
You can also insert a printable Table of Contents at the end of the PDF that lists the page numbers for every section.
This is very useful if you intend to print out the PDF to paper. If you wish to use the PDF on an electronic device, then
the PDF Outline provides this functionality and is generated by default.
You can customize the look of the generated Table of contents by using the Extra CSS conversion setting under the
Look & feel part of the conversion dialog. The default css used is listed below, simply copy it and make whatever
changes you like.
.calibre-pdf-toc .level-0 {
font-size: larger;
}
If you are converting an EPUB or AZW3 file with multiple individual HTML files inside it and you want to change
the page margins for a particular HTML file you can add the following style block to the HTML file using the calibre
editor:
<style>
@page {
margin-left: 10pt;
margin-right: 10pt;
margin-top: 10pt;
margin-bottom: 10pt;
}
</style>
Then, in the PDF output section of the conversion dialog, turn on the option to Use page margins from the document
being converted. Now all pages generated from this HTML file will have 10pt margins.
Editing e-books
calibre has an integrated e-book editor that can be used to edit books in the EPUB and AZW3 (Kindle) formats. The
editor shows you the HTML and CSS that is used internally inside the book files, with a live preview that updates as
you make changes. It also contains various automated tools to perform common cleanup and fixing tasks.
You can use this editor by right clicking on any book in calibre and selecting Edit book.
79
calibre User Manual, Release 4.21.0
Contents
When you first open a book with the Edit book tool, you will be presented with a list of files on the left. These are the
individual HTML files, stylesheets, images, etc. that make up the content of the book. Simply double click on a file
to start editing it. Note that if you want to do anything more sophisticated than making a few small tweaks, you will
need to know HTML Tutorial30 and CSS Tutorial31 .
As you make changes to the HTML or CSS in the editor, the changes will be previewed, live, in the preview panel to
the right. When you are happy with how the changes you have made look, click the Save button or use File→Save to
save your changes into the e-book.
One useful feature is Checkpoints. Before you embark on some ambitious set of edits, you can create a checkpoint. The
checkpoint will preserve the current state of your book, then if in the future you decide you don’t like the changes you
have made to you can go back to the state when you created the checkpoint. To create a checkpoint, use Edit→Create
checkpoint. Checkpoints will also be automatically created for you whenever you run any automated tool like global
search and replace. The checkpointing functionality is in addition to the normal undo/redo mechanism when editing
individual files. Checkpoints are useful for when changes are spread over multiple files in the book.
That is the basic work flow for editing books – Open a file, make changes, preview and save. The rest of this manual
will discuss the various tools and features present to allow you to perform specific tasks efficiently.
29 https://calibre-ebook.com/demo#tutorials
30 http://html.net/tutorials/html/
31 http://html.net/tutorials/css/
The File browser gives you an overview of the various files inside the book you are editing. The files are arranged by
category, with text (HTML) files at the top, followed by stylesheet (CSS) files, images and so on. Simply double click
on a file to start editing it. Editing is supported for HTML, CSS and image files. The order of text files is the same
order that they would be displayed in, if you were reading the book. All other files are arranged alphabetically.
By hovering your mouse over an entry, you can see its size, and also, at the bottom of the screen, the full path to the
file inside the book. Note that files inside e-books are compressed, so the size of the final book is not the sum of the
individual file sizes.
Many files have special meaning, in the book. These will typically have an icon next to their names, indicating the
special meaning. For example, in the picture to the left, you can see that the files cover_image.jpg and titlepage.xhtml
have the icon of a cover next to them, this indicates they are the book cover image and titlepage. Similarly, the
content.opf file has a metadata icon next to it, indicating the book metadata is present in it and the toc.ncx file has a T
icon next to it, indicating it is the Table of Contents.
You can perform many actions on individual files, by right clicking them.
You can rename an individual file by right clicking it and selecting Rename. Renaming a file automatically updates all
links and references to it throughout the book. So all you have to do is provide the new name, calibre will take care of
the rest.
You can also bulk rename many files at once. This is useful if you want the files to have some simple name pattern.
For example you might want to rename all the HTML files to have names Chapter-1.html, Chapter-2.html and so on.
Select the files you want bulk renamed by holding down the Shift or Ctrl key and clicking the files. Then right click
and select Bulk rename. Enter a prefix and what number you would like the automatic numbering to start at, click OK
and you are done. The bulk rename dialog also lets you rename files by the order they appear in the book instead of
the order you selected them in, useful, for instance to rename all images by the order they appear.
Finally, you can bulk change the file extension for all selected files. Select multiple files, as above, and right click and
choose Change the file extension for the selected files.
Sometimes, you may want to merge two HTML files or two CSS files together. It can sometimes be useful to have
everything in a single file. Be wary, though, putting a lot of content into a single file will cause performance problems
when viewing the book in a typical e-book reader.
To merge multiple files together, select them by holding the Ctrl key and clicking on them (make sure you only select
files of one type, either all HTML files or all CSS files and so on). Then right click and select merge. That’s all,
calibre will merge the files, automatically taking care of migrating all links and references to the merged files. Note
that merging files can sometimes cause text styling to change, since the individual files could have used different
stylesheets.
You can re-arrange the order in which text (HTML) files are opened when reading the book by simply dragging and
dropping them in the Files browser. For the technically inclined, this is called re-ordering the book spine. Note that
you have to drop the items between other items, not on top of them, this can be a little fiddly until you get used to it.
E-books typically have a cover image. This image is indicated in the File browser by the icon of a brown book next
to the image name. If you want to designate some other image as the cover, you can do so by right clicking on the file
and choosing Mark as cover.
In addition, EPUB files has the concept of a titlepage. A title page is a HTML file that acts as the title page/cover for
the book. You can mark an HTML file as the titlepage when editing EPUBs by right-clicking. Be careful that the file
you mark contains only the cover information. If it contains other content, such as the first chapter, then that content
will be lost if the user ever converts the EPUB file in calibre to another format. This is because when converting,
calibre assumes that the marked title page contains only the cover and no other content.
You can delete files by either right clicking on them or by selecting them and pressing the Delete key. Deleting a file
removes all references to the file from the OPF file, saving you that chore. However, references in other places are not
removed, you can use the Check Book tool to easily find and remove/replace them.
You can export a file from inside the book to somewhere else on your computer. This is useful if you want to work on
the file in isolation, with specialised tools. To do this, simply right click on the file and choose Export.
Once you are done working on the exported file, you can re-import it into the book, by right clicking on the file again
and choosing Replace with file. . . which will allow you to replace the file in the book with the previously exported
file.
You can also copy files between multiple editor instances. Select the files you want to copy in the File browser, then
right click and choose, Copy selected files to another editor instance. Then, in the other editor instance, right click in
the File browser and choose Paste file from other editor instance.
You can add a new image, font, stylesheet, etc. from your computer into the book by clicking File→New file. This
lets you either import a file by clicking the Import resource file button or create a new blank HTML file or stylesheet
by simply entering the file name into the box for the new file.
You can also import multiple files into the book at once using File->Import files into book.
You can easily replace existing files in the book, by right clicking on the file and choosing replace. This will automat-
ically update all links and references, in case the replacement file has a different name than the file being replaced.
As a convenience, you can select multiple HTML files in the File browser, right click and choose Link stylesheets to
have calibre automatically insert the <link> tags for those stylesheets into all the selected HTML files.
Edit book has a very powerful search and replace interface that allows you to search and replace text in the current file,
across all files and even in a marked region of the current file. You can search using a normal search or using regular
expressions. To learn how to use regular expressions for advanced searching, see All about using regular expressions
in calibre (page 192).
Start the search and replace via the Search→Find/replace menu entry (you must be editing an HTML or CSS file).
Type the text you want to find into the Find box and its replacement into the Replace box. You can the click the
appropriate buttons to Find the next match, replace the current match and replace all matches.
Using the drop downs at the bottom of the box, you can have the search operate over the current file, all text files,
all style files or all files. You can also choose the search mode to be a normal (string) search or a regular expression
search.
You can count all the matches for a search expression via Search→Count all. The count will run over whatever
files/regions you have selected in the dropdown box.
You can also go to a specific line in the currently open editor via Search→Go to line.
Note: Remember, to harness the full power of search and replace, you will need to use regular expressions. See All
about using regular expressions in calibre (page 192).
You can save frequently used search/replace expressions (including function mode expressions) and reuse them mul-
tiple times. To save a search simply right click in the Find box and select Save current search.
You can bring up the saved searches via Search→Saved searches. This will present you with a list of search and
replace expressions that you can apply. You can even select multiple entries in the list by holding down the Ctrl Key
while clicking so as to run multiple search and replace expressions in a single operation.
Function mode allows you to write arbitrarily powerful Python functions that are run on every Find/replace. You can
do pretty much any text manipulation you like in function mode. For more information, see Function mode for Search
& replace in the Editor (page ??).
There is also a dedicated tool for searching for text, ignoring any HTML tags in between. For example, if the book has
the HTML Empahisis on a <i>word</i>. you can search for on a word and it will be found even though
there is an <i> tag in the middle. Use this tool via the Search→Search ignoring HTML markup menu item.
Edit book has various tools to help with common tasks. These are accessed via the Tools menu.
There is a dedicated tool to ease editing of the Table of Contents. Launch it with Tools→Table of Contents→Edit
Table of Contents.
The Edit Table of Contents tool shows you the current Table of Contents (if any) on the left. Simply double click on
any entry to change its text. You can also re-arrange entries by drag and drop or by using the buttons to the right.
For books that do not have a pre-existing Table of Contents, the tool gives you various options to auto-generate a Table
of Contents from the text. You can generate from the headings in the document, from links, from individual files and
so on.
You can edit individual entries by clicking on them and then clicking the Change the location this entry points to
button. This will open up a mini-preview of the book, simply move the mouse cursor over the book view panel, and
click where you want the entry to point to. A thick green line will show you the location. Click OK once you are
happy with the location.
The Check Book tool searches your book for problems that could prevent it working as intended on actual reader
devices. Activate it via Tools→Check Book.
Any problems found are reported in a nice, easy to use list. Clicking any entry in the list shows you some help about
that error as well as giving you the option to auto-fix that error, if the error can be fixed automatically. You can also
double click the error to open the location of the error in an editor, so you can fix it yourself.
Some of the checks performed are:
• Malformed HTML markup. Any HTML markup that does not parse as well-formed XML is reported. Correct-
ing it will ensure that your markup works as intended in all contexts. calibre can also auto-fix these errors, but
auto-fixing can sometimes have unexpected effects, so use with care. As always, a checkpoint is created before
auto-fixing so you can easily revert all changes. Auto-fixing works by parsing the markup using the HTML5
algorithm, which is highly fault tolerant and then converting to well formed XML.
• Malformed or unknown CSS styles. Any CSS that is not valid or that has properties not defined in the CSS
2.1 standard (plus a few from CSS 3) are reported. CSS is checked in all stylesheets, inline style attributes and
<style> tags in HTML files.
• Broken links. Links that point to files inside the book that are missing are reported.
• Unreferenced files. Files in the book that are not referenced by any other file or are not in the spine are reported.
• Various common problems in OPF files such as duplicate spine or manifest items, broken idrefs or meta cover
tags, missing required sections and so on.
• Various compatibility checks for known problems that can cause the book to malfunction on reader devices.
You can easily add a cover to the book via Tools→Add cover. This allows you to either choose an existing image in
the book as the cover or import a new image into the book and make it the cover. When editing EPUB files, the HTML
wrapper for the cover is automatically generated. If an existing cover in the book is found, it is replaced. The tool also
automatically takes care of correctly marking the cover files as covers in the OPF.
Accessed via Tools→Embed reference fonts, this tool finds all fonts referenced in the book and if they are not already
embedded, searches your computer for them and embeds them into the book, if found. Please make sure that you have
the necessary copyrights for embedding commercially licensed fonts, before doing this.
Accessed via Tools→Subset embedded fonts, this tool reduces all the fonts in the book to only contain glyphs for the
text actually present in the book. This commonly reduces the size of the font files by ~ 50%. However, be aware that
once the fonts are subset, if you add new text whose characters are not previously present in the subset font, the font
will not work for the new text. So do this only as the last step in your workflow.
Convert plain text dashes, ellipsis, quotes, multiple hyphens, etc. into their typographically correct equivalents. Note
that the algorithm can sometimes generate incorrect results, especially when single quotes at the start of contractions
are involved. Accessed via Tools→Smarten punctuation.
Create rules to transform the styling of the book. For example, create a rule to convert all red text to green or to double
the font size of all text in the book or make text of a certain font family italic, etc.
Creating the rules is simple, the rules follow a natural language format, that looks like:
• If the property color is red change it to green
• If the property font-size is any value multiply the value by 2
Accessed via Tools→Transform styles.
Remove all unused CSS rules from stylesheets and <style> tags. Some books created from production templates can
have a large number of extra CSS rules that don’t match any actual content. These extra rules can slow down readers
that need to process them all. Accessed via Tools→Remove unused CSS.
This tool simply converts HTML that cannot be parsed as XML into well-formed XML. It is very common in e-books
to have non-well-formed XML, so this tool simply automates the process of fixing such HTML. The tool works by
parsing the HTML using the HTML5 algorithm (the algorithm used in all modern browsers) and then converting the
result into XML. Be aware that auto-fixing can sometimes have counter-intuitive results. If you prefer, you can use
the Check Book tool discussed above to find and manually correct problems in the HTML. Accessed via Tools→Fix
HTML.
This tool is used to auto-format all HTML and CSS files so that they “look pretty”. The code is auto-indented so that
it lines up nicely, blank lines are inserted where appropriate and so on. Note that beautifying also auto-fixes broken
HTML/CSS. Therefore, if you don’t want any auto-fixing to be performed, first use the Check Book tool to correct all
problems and only then run beautify. Accessed via Tools→Beautify all files.
Note: In HTML any text can have significant whitespace, via the CSS white-space directive. Therefore, beautification
could potentially change the rendering of the HTML. To avoid this as far as possible, the beautify algorithm only
beautifies block level tags that contain other block level tags. So, for example, text inside a <p> tag will not have
its whitespace changed. But a <body> tag that contains only other <p> and <div> tags will be beautified. This can
sometimes mean that a particular file will not be affected by beautify as it has no suitable block level tags. In such
cases you can try different beautification tools, that are less careful, for example: HTML Tidy32 .
Normally in e-books, the Table of Contents is separate from the main text and is typically accessed via a special Table
of Contents button/menu in the e-book reading device. You can also have calibre automatically generate an inline
Table of Contents that becomes part of the text of the book. It is generated based on the currently defined Table of
Contents.
If you use this tool multiple times, each invocation will cause the previously created inline Table of Contents to be
replaced. The tool can be accessed via Tools→Table of Contents→Insert inline Table of Contents.
This tool is used to set semantics in EPUB files. Semantics are simply, links in the OPF file that identify certain
locations in the book as having special meaning. You can use them to identify the foreword, dedication, cover, table
of contents, etc. Simply choose the type of semantic information you want to specify and then select the location in
the book the link should point to. This tool can be accessed via Tools→Set semantics.
32 https://infohound.net/tidy/
This tool can be used to easily remove specified CSS style properties from the entire book. You can tell it what
properties you want removed, for example, color, background-color, line-height and it will remove
them from everywhere they occur — stylesheets, <style> tags and inline style attributes. After removing the
style information, a summary of all the changes made is displayed so you can see exactly what was changed. The tool
can be accessed via Tools→Filter style information.
This tool can be used to upgrade the book’s internals, if possible. For instance it will upgrade EPUB 2 books to EPUB
3 books. The tool can be accessed via Upgrade book internals.
5.5 Checkpoints
Checkpoints are a way to mark the current state of the book as “special”. You can then go on to do whatever changes
you want to the book and if you don’t like the results, return to the checkpointed state. Checkpoints are automatically
created every time you run any of the automated tools described in the previous section.
You can create a checkpoint via Edit→Create checkpoint. And go back to a previous checkpoint with Edit→Revert to
...
The check pointing functionality is in addition to the normal Undo/redo mechanism when editing individual files.
Checkpoints are particularly useful for when changes are spread over multiple files in the book or when you wish to
be able to revert a large group of related changes as a whole.
You can see a list of available checkpoints via View→Checkpoints. You can compare the current state of the book
to a specified checkpoint using the Comparing e-books (page 121) tool – by selecting the checkpoint of interest and
clicking the Compare button. The Revert to button restores the book to the selected checkpoint, undoing all changes
since that checkpoint was created.
5.5. Checkpoints 91
calibre User Manual, Release 4.21.0
The File preview gives you an overview of the various files inside The live preview panel shows you the changes
you are making live (with a second or two of delay). As you edit HTML or CSS files, the preview panel is updated
automatically to reflect your changes. As you move the cursor around in the editor, the preview panel will track its
location, showing you the corresponding location in the book. Clicking in the preview panel, will cause the cursor in
the editor to be positioned over the element you clicked. If you click a link pointing to another file in the book, that
file will be opened in the edit and the preview panel, automatically.
You can turn off the automatic syncing of position and live preview of changes – by buttons under the preview panel.
The live update of the preview panel only happens when you are not actively typing in the editor, so as not to be
distracting or slow you down, waiting for the preview to render.
The preview panel shows you how the text will look when viewed. However, the preview panel is not a substitute
for actually testing your book an actual reader device. It is both more, and less capable than an actual reader. It will
tolerate errors and sloppy markup much better than most reader devices. It will also not show you page margins, page
breaks and embedded fonts that use font name aliasing. Use the preview panel while you are working on the book, but
once you are done, review it in an actual reader device or software emulator.
Note: The preview panel does not support embedded fonts if the name of the font inside the font file does not match
the name in the CSS @font-face rule. You can use the Check Book tool to quickly find and fix any such problem fonts.
One, perhaps non-obvious, use of the preview panel is to split long HTML files. While viewing the file you want to
split, click the Split mode button under the preview panel . Then simply move your mouse to the place where
you want to split the file and click. A thick green line will show you exactly where the split will happen as you move
your mouse. Once you have found the location you want, simply click and the split will be performed.
Splitting the file will automatically update all links and references that pointed into the bottom half of the file and will
open the newly split file in an editor.
You can also split a single HTML file at multiple locations automatically, by right clicking inside the file in the editor
and choosing Split at multiple locations. This will allow you to easily split a large file at all heading tags or all tags
having a certain class and so on.
The Live CSS panel shows you all the style rules that apply to the tag you are currently editing. The name of tag, along
with its line number in the editor are displayed, followed by a list of matching style rules.
It is a great way to quickly see which style rules apply to any tag. The view also has clickable links (in blue), which
take you directly to the location where the style was defined, in case you wish to make any changes to the style rules.
Style rules that apply directly to the tag, as well as rules that are inherited from parent tags are shown.
The panel also shows you what the finally calculated styles for the tag are. Properties in the list that are superseded by
higher priority rules are shown with a line through them.
You can enable the Live CSS panel via View→Live CSS.
There are a few more tools that can be useful while you edit the book.
The Table of Contents view shows you the current table of contents in the book. Double clicking on any entry opens
the place that entry points to in an editor. You can right click to edit the Table of Contents, refresh the view or
expand/collapse all items. Access this view via View→Table of Contents.
Words are shown with the number of times they occur in the book and the language the word belongs to. Language
information is taken from the books metadata and from lang attributes in the HTML files. This allows the spell
checker to work well even with books that contain text in multiple languages. For example, in the following HTML
extract, the word color will be checked using American English and the word colour using British English:
Note: You can double click a word to highlight the next occurrence of that word in the editor. This is useful if you
wish to manually edit the word, or see what context it is in.
To change a word, simply double click one of the suggested alternative spellings on the right, or type in your own
corrected spelling and click the Change selected word to button. This will replace all occurrences of the word in the
book. You can also right click on a word in the main word list to change the word conveniently from the right click
menu.
You can have the spelling checker ignore a word for the current session by clicking the Ignore button. You can also
add a word to the user dictionary by clicking the Add to dictionary button. The spelling checker supports multiple user
dictionaries, so you can select the dictionary you want the word added to.
You can also have the spelling checker display all the words in your book, not just the incorrectly spelled ones. This is
useful to see what words are most common in your book and to run a simple search and replace on individual words.
Note: If you make any changes to the book by editing files while the spell check tool is open, you should click the
Refresh button in the Spell check tool. If you do not do this and continue to use the Spell check tool, you could lose
the changes you have made in the editor.
The spelling checker comes with builtin dictionaries for the English and Spanish languages. You can install your
own dictionaries via Preferences→Editor→Manage spelling dictionaries. The spell checker can use dictionaries from
the LibreOffice program (in the .oxt format). You can download these dictionaries from The LibreOffice Extensions
repository33 .
You can insert characters that are difficult to type by using the Edit→Insert special character tool. This shows you all
unicode characters, simply click on the character you want to type. If you hold Ctrl while clicking, the window will
close itself after inserting the selected character. This tool can be used to insert special characters into the main text or
into any other area of the user interface, such as the Search and replace tool.
Because there are a lot of characters, you can define your own Favorite characters, that will be shown first. Simply
right click on a character to mark it as favorite. You can also right click on a character in favorites to remove it from
favorites. Finally, you can re-arrange the order of characters in favorites by clicking the Re-arrange favorites button
and then drag and dropping the characters in favorites around.
You can also directly type in special characters using the keyboard. To do this, you type the unicode code for the
character (in hexadecimal) and then press the Alt+X key which will convert the previously typed code into the cor-
responding character. For example, to type ÿ you would type ff and then Alt+X. To type a non-breaking space you
would use a0 and then Alt+X, to type the horizontal ellipsis you would use 2026 and Alt+X and so on.
Finally, you can type in special characters by using HTML named entities. For example, typing will be
replaced by a non breaking space when you type the semi-colon. The replacement happens only when typing the
semi-colon.
This view shows you the HTML coding and CSS that applies to the current element of interest. You open it by right
clicking a location in the preview panel and choosing Inspect. It allows you to see the HTML coding for that element
and more importantly, the CSS styles that apply to it. You can even dynamically edit the styles and see what effect
your changes have instantly. Note that editing the styles does not actually make changes to the book contents, it only
allows for quick experimentation. The ability to live edit inside the Inspector is under development.
33 https://extensions.libreoffice.org/extension-center?getCategories=Dictionary&getCompatibility=any&sort_on=positive_ratings
You can use this tool to check all links in your book that point to external websites. The tool will try to visit every
externally linked website, and if the visit fails, it will report all broken links in a convenient format for you to fix.
You can use this tool to automatically download any images/stylesheets/etc. in the book that are not bundled with the
book (i.e. they have URLs pointing to a location on the internet). The tool will find all such resources and automatically
download them, add them to the book and replace all references to them to use the downloaded files.
Often when editing EPUB files that you get from somewhere, you will find that the files inside the EPUB are arranged
haphazardly, in different sub-folders. This tool allows you to automatically move all files into sub-folders based on
their types. Access it via Tools→Arrange into folders. Note that this tool only changes how the files are arranged
inside the EPUB, it does not change how they are displayed in the File browser.
The editor includes the ability to import files in some other e-book formats directly as a new EPUB, without going
through a full conversion. This is particularly useful to directly create EPUB files from your own hand-edited HTML
files. You can do this via File→Import an HTML or DOCX file as a new book.
The Search & replace tool in the editor support a function mode. In this mode, you can combine regular expressions
(see All about using regular expressions in calibre (page ??)) with arbitrarily powerful Python functions to do all sorts
of advanced text processing.
In the standard regexp mode for search and replace, you specify both a regular expression to search for as well as a
template that is used to replace all found matches. In function mode, instead of using a fixed template, you specify an
arbitrary function, in the Python programming language34 . This allows you to do lots of things that are not possible
with simple templates.
Techniques for using function mode and the syntax will be described by means of examples, showing you how to
create functions to perform progressively more complex tasks.
Here, we will leverage one of the builtin functions in the editor to automatically change the case of all text inside
heading tags to title case:
34 https://docs.python.org
For the function, simply choose the Title-case text (ignore tags) builtin function. The will change titles that look like:
<h1>some TITLE</h1> to <h1>Some Title</h1>. It will work even if there are other HTML tags inside
the heading tags.
The real power of function mode comes from being able to create your own functions to process text in arbitrary ways.
The Smarten Punctuation tool in the editor leaves individual hyphens alone, so you can use the this function to replace
them with em-dashes.
To create a new function, simply click the Create/edit button to create a new function and copy the Python code from
below.
Every Search & replace custom function must have a unique name and consist of a Python function named replace,
that accepts all the arguments shown above. For the moment, we wont worry about all the different arguments to
replace() function. Just focus on the match argument. It represents a match when running a search and replace.
Its full documentation in available here35 . match.group() simply returns all the matched text and all we do is
replace hyphens in that text with em-dashes, first replacing double hyphens and then single hyphens.
Use this function with the find regular expression:
>[^<>]+<
And it will replace all hyphens with em-dashes, but only in actual text and not inside HTML tag definitions.
The power of function mode - using a spelling dictionary to fix mis-hyphenated words
Often, e-books created from scans of printed books contain mis-hyphenated words – words that were split at the end
of the line on the printed page. We will write a simple function to automatically find and fix such words.
import regex
from calibre import replace_entities
from calibre import prepare_string_for_xml
def replace_word(wmatch):
# Try to remove the hyphen and replace the words if the resulting
# hyphen free word is recognized by the dictionary
without_hyphen = wmatch.group(1) + wmatch.group(2)
if dictionaries.recognized(without_hyphen):
return without_hyphen
return wmatch.group()
Use this function with the same find expression as before, namely:
>[^<>]+<
And it will magically fix all mis-hyphenated words in the text of the book. The main trick is to use one of the useful
extra arguments to the replace function, dictionaries. This refers to the dictionaries the editor itself uses to spell
check text in the book. What this function does is look for words separated by a hyphen, remove the hyphen and
check if the dictionary recognizes the composite word, if it does, the original words are replaced by the hyphen free
composite word.
Note that one limitation of this technique is it will only work for mono-lingual books, because, by default,
dictionaries.recognized() uses the main language of the book.
Now we will see something a little different. Suppose your HTML file has many sections, each with a heading in an
<h2> tag that looks like <h2>Some text</h2>. You can create a custom function that will automatically number
these headings with consecutive section numbers, so that they look like <h2>1. Some text</h2>.
# Ensure that when running over multiple files, the files are processed
# in the order in which they appear in the book
replace.file_order = 'spine'
(?s)(<h2[^<>]*>)(.+?</h2>)
Place the cursor at the top of the file and click Replace all.
This function uses another of the useful extra arguments to replace(): the number argument. When doing a
Replace All number is automatically incremented for every successive match.
Another new feature is the use of replace.file_order – setting that to 'spine' means that if this search is
run on multiple HTML files, the files are processed in the order in which they appear in the book. See Choose file
order when running on multiple HTML files (page 105) for details.
Finally, lets try something a little more ambitious. Suppose your book has headings in h1 and h2 tags that look
like <h1 id="someid">Some Text</h1>. We will auto-generate an HTML Table of Contents based on these
headings. Create the custom function below:
if match is None:
# All matches found, output the resulting Table of Contents.
# The argument metadata is the metadata of the book being edited
if 'toc' in data:
toc = data['toc']
root = TOC()
for (file_name, tag_name, anchor, text) in toc:
parent = root.children[-1] if tag_name == 'h2' and root.children else
˓→root
print (xml2str(toc))
else:
print ('No headings to build ToC from found')
else:
# Add an entry corresponding to this match to the Table of Contents
if 'toc' not in data:
# The entries are stored in the data object, which will persist
# for all invocations of this function during a 'Replace All' operation
data['toc'] = []
tag_name, anchor, text = match.group(1), replace_entities(match.group(2)),
˓→replace_entities(match.group(3))
# Ensure that we are called once after the last match is found so we can
# output the ToC
replace.call_after_last_match = True
# Ensure that when running over multiple files, this function is called,
# the files are processed in the order in which they appear in the book
replace.file_order = 'spine'
Run the search on All text files and at the end of the search, a window will popup with “Debug output from your
function” which will have the HTML Table of Contents, ready to be pasted into toc.html.
The function above is heavily commented, so it should be easy to follow. The key new feature is the use of another
useful extra argument to the replace() function, the data object. The data object is a Python dict that persists
between all successive invocations of replace() during a single Replace All operation.
Another new feature is the use of call_after_last_match – setting that to True on the replace() function
means that the editor will call replace() one extra time after all matches have been found. For this extra call, the
match object will be None.
This was just a demonstration to show you the power of function mode, if you really needed to generate a Table of Con-
tents from headings in your book, you would be better off using the dedicated Table of Contents tool in Tools→Table
of Contents.
All function mode functions must be Python functions named replace, with the following signature:
return a_string
When a find/replace is run, for every match that is found, the replace() function will be called, it must return the
replacement string for that match. If no replacements are to be done, it should return match.group() which is the
original string. The various arguments to the replace() function are documented below.
The match argument represents the currently found match. It is a Python Match object36 . Its most useful method is
group() which can be used to get the matched text corresponding to individual capture groups in the search regular
expression.
The number argument is the number of the current match. When you run Replace All, every successive match will
cause replace() to be called with an increasing number. The first match has number 1.
This is the filename of the file in which the current match was found. When searching inside marked text, the
file_name is empty. The file_name is in canonical form, a path relative to the root of the book, using / as
the path separator.
This represents the metadata of the current book, such as title, authors, language, etc. It is an object of class calibre.
ebooks.metadata.book.base.Metadata (page 184). Useful attributes include, title, authors (a list of
authors) and language (the language code).
This represents the collection of dictionaries used for spell checking the current book. Its most useful method is
dictionaries.recognized(word) which will return True if the passed in word is recognized by the dictio-
nary for the current book’s language.
36 https://docs.python.org/library/re.html#match-objects
This a simple Python dict. When you run Replace all, every successive match will cause replace() to be called
with the same dict as data. You can thus use it to store arbitrary data between invocations of replace() during a
Replace all operation.
The functions argument gives you access to all other user defined functions. This is useful for code re-use. You
can define utility functions in one place and re-use them in all your other functions. For example, suppose you create
a function name My Function like this:
def utility():
# do something
...
Then, in another function, you can access the utility() function like this:
You can also use the functions object to store persistent data, that can be re-used by other functions. For example, you
could have one function that when run with Replace All collects some data and another function that uses it when it is
run afterwards. Consider the following two functions:
# Function One
persistent_data = {}
...
persistent_data['something'] = 'some data'
# Function Two
def replace(match, number, file_name, metadata, dictionaries, data, functions, *args,
˓→**kwargs):
You can debug the functions you create by using the standard print() function from Python. The output of print
will be displayed in a popup window after the Find/replace has completed. You saw an example of using print()
to output an entire table of contents above.
When you run a Replace all on multiple HTML files, the order in which the files are processes depends on what files
you have open for editing. You can force the search to process files in the order in which the appear by setting the
file_order attribute on your function, like this:
...
replace.file_order = 'spine'
file_order accepts two values, spine and spine-reverse which cause the search to process multiple files in
the order they appear in the book, either forwards or backwards, respectively.
Having your function called an extra time after the last match is found
Sometimes, as in the auto generate table of contents example above, it is useful to have your function called an extra
time after the last match is found. You can do this by setting the call_after_last_match attribute on your
function, like this:
...
replace.call_after_last_match = True
When running search and replace on marked text, it is sometimes useful to append so text to the end of the marked
text. You can do that by setting the append_final_output_to_marked attribute on your function (note that
you also need to set call_after_last_match), like this:
...
return 'some text to append'
replace.call_after_last_match = True
replace.append_final_output_to_marked = True
You can also suppress the result dialog (which can slow down the repeated application of a search/replace on many
blocks of text) by setting the suppress_result_dialog attribute on your function, like this:
...
replace.suppress_result_dialog = True
More examples
More useful examples, contributed by calibre users, can be found in the calibre Editor forum37 .
Snippets
The calibre editor supports snippets. A snippet is a piece of text that is either re-used often or contains a lot of
redundant text. The editor allows you to insert a snippet with only a few key strokes. For example, suppose you
often find yourself inserting link tags when editing HTML files, then you can simply type <a in the editor and press
Control+J. The editor will expand it to:
<a href="filename"></a>
Not only that, the word filename will be selected, with the cursor placed over it, so that you can easily type in the
real filename, using the editor’s nifty Auto-complete (page 111) feature. And once you are done typing the filename,
press Control+J again and the cursor will jump to the position in between the <a> tags so you can easily type in
the text for the link.
The snippets system in the editor is very sophisticated, there are a few built-in snippets and you can create your own
to suit your editing style.
The following discussion of the built-in snippets should help illustrate the power of the snippets system.
Note: You can also use snippets in the text entry fields in the Search & replace panel, however, placeholders (using
Control+J to jump around) will not work.
The built-in snippets are described below. Note that you can override them by creating your own snippets with the
same trigger text.
The first built-in snippet, and the simplest is used to insert filler text into a document. The filler text is taken from De
finibus bonorum et malorum38 a philosophical work by Cicero (translated to English). To use it simply type Lorem
in an HTML file and press Control+J. It will be replaced by a couple of paragraphs of filler.
The definition of this snippet is very simple, the trigger text is defined as Lorem and the template is defined simply as
the literal text to be inserted. You can easily customize it to use your favorite form of filler text.
Now let’s look at a simple example of the powerful concept of placeholders. Say you want to insert the self-closing
tag <hr/>. Just type <>, and press Control+J, the editor will expand the snippet to:
<|/>
37 https://www.mobileread.com/forums/showthread.php?t=237181
38 https://en.wikipedia.org/wiki/De_finibus_bonorum_et_malorum
Here, the | symbol represents the current cursor position. You can then type hr and press Control+J to move the
cursor to after the end of the tag. This snippet is defined as:
Trigger: <>
Template: <$1/>$2
Placeholders are simply the dollar ($) sign followed by a number. When the snippet is expanded by pressing
Control+J the cursor is positioned at the first placeholder (the placeholder with the lowest number). When you
press Control+J again the cursor jumps to the next placeholder (the placeholder with the next higher number).
HTML link tags all share a common structure. They have an href attribute and some text between the opening and
closing tags. A snippet to make typing them more efficient will introduce us to some more features of placeholders.
To use this snippet, simply type <a and press Control+J. The editor will expand this to:
<a href="filename|"></a>
Not only that, the word filename will be selected, with the cursor placed over it, so that you can easily type in the
real filename, using the editor’s nifty Auto-complete (page 111) feature. And once you are done typing the filename,
press Control+J again and the cursor will jump to the position in between the <a> tags so you can easily type in
the text for the link. After you are done typing the text, press Control+J again to jump to the point after the closing
tag. This snippet is defined as:
Trigger: <a
Template: <a href="${1:filename}">${2*}</a>$3
There are a couple of new features here. First the $1 placeholder has become more complex. It now includes some
default text (the word filename). If a placeholder contains default text, the default text is substituted for the place-
holder when the snippet is expanded. Also when you jump to a placeholder with default text using Control+J, the
default text is selected. In this way, you can use default text to act as a reminder to you to fill in important parts of the
template. You can specify default text for a placeholder by using the syntax: ${<number>:default text}.
The other new feature is that the second placeholder has an asterisk after it (${2*}). This means that any text that
was selected before expanding the template is substituted for the placeholder. To see this in action, select some text in
the editor, press Control+J, type <a and press Control+J again, the template will be expanded to:
This is very similar to inserting an HTML link, as we saw above. It allows you to quickly input an <img
src="filename" alt="description" /> tag and jump between the src and alt attributes:
Trigger: <i
Template: <img src="${1:filename}" alt="${2*:description}" />$3
This allows you to insert an arbitrary full HTML tag (or wrap previously selected text in the tag). To use it, simply
type << and press Control+J. The editor will expand it to:
<|></>
Type the tag name, for example: span and press Control+J, that will result in:
<span>|</span>
You will note that the closing tag has been automatically filled with span. This is achieved with yet another feature
of placeholders, mirroring. Mirroring simply means that if you specify the sample placeholder more than once in a
template, the second and all later positions will be automatically filled in with whatever you type in the first position,
when you press Control+J. The definition for this snippet is:
Trigger: <<
Template: <$1>${2*}</$1>$3
As you can see, the first placeholder ($1) has been specified twice, the second time in the closing tag, which will
simply copy whatever you type in the opening tag.
This is very similar to the insert arbitrary tag example above, except that it assumes that you want to specify a class
for the tag:
Trigger: <c
Template: <$1 class="${2:classname}">${3*}</$1>$4
This will allow you to first type the tag name, press Control+J, type the class name, press Control+J type the
contents of the tag and press Control+J one last time to jump out of the tag. The closing tag will be auto-filled.
Snippets really shine because you can create your own to suit your editing style. To create your own snippets go to
Edit→Preferences→Editor settings→Manage snippets in the editor. This will pop-up an easy to use dialog to help
you create your own snippets. Simply click the Add snippet button and you will see a dialog that looks like:
First give your snippet a name, something descriptive, to help identify the snippet in the future. Then specify the
trigger. A trigger is simply the text that you have to type in the editor before pressing Control+J in order to expand
the snippet.
Then specify the snippet template. You should start with one of the example above and modify it to suit your needs.
Finally, specify which file types you want the snippet to be active for. This way you can have multiple snippets with
the same trigger text that work differently in different file types.
The next step is to test your newly created snippet. Use the Test box at the bottom. Type in the trigger text and press
Control+J to expand the snippet and jump between placeholders.
The editor includes a nice Reports tool (via Tools→Reports) that shows summaries of the files, images, links, words,
characters and styles used in the book. Every line in the report is hot-linked. Double clicking a line jumps to the place
in the book where that item is used or defined (as appropriate). For example, in the Links view, you can double click
entries the Source column to jump to where the link is defined and entries in the Target column to jump to where the
link points.
The calibre HTML editor is very powerful. It has many features that make editing of HTML (and CSS) easier.
The HTML editor has very sophisticated syntax highlighting. Features include:
• The text inside bold, italic and heading tags is made bold/italic
• As you move your cursor through the HTML, the matching HTML tags are highlighted, and you can jump to
the opening or closing tag with the keyboard shortcuts Ctrl+{ and Ctrl+}. Similarly, you can select the
contents of a tag with Ctrl+Alt+T.
• Invalid HTML is highlighted with a red underline
• Spelling errors in the text inside HTML tags and attributes such as title are highlighted. The spell checking is
language aware, based on the value of the lang attribute of the current tag and the overall book language.
• CSS embedded inside <style> tags is highlighted
• Special characters that can be hard to distinguish such as non-breaking spaces, different types of hyphens, etc.
are highlighted.
• Links to other files in <a> tags, <img> and <link> tags all have the filenames highlighted. If the filename
they point to does not exist, the filename is marked with a red underline.
You can right click on an HTML tag name or a CSS property name to get help for that tag or property.
You can also hold down the Ctrl key and click on any filename inside a link tag to open that file in the editor automat-
ically.
5.9.3 Auto-complete
When editing an e-book, one of the most tedious tasks is creating links to other files inside the book, or to CSS
stylesheets, or images. You have to figure out the correct filename and relative path to the file. The editor has auto-
complete to make that easier.
As you type a filename, the editor automatically pops up suggestions. Simply use the Tab key to select the correct file
name. The editor even offers suggestions for links pointing to an anchor inside another HTML file. After you type
the # character, the editor will show you a list of all anchors in the target file, with a small snippet of text to help you
choose the right anchor.
Note that unlike most other completion systems, the editor’s completion system uses subsequence matching. This
means that you can type just two or three letters from anywhere in the filename to complete the filename. For example,
say you want the filename ../images/arrow1.png, you can simply type ia1 and press Tab to complete the
filename. When searching for matches, the completion system prioritizes letters that are at the start of a word, or
immediately after a path separator. Once you get used to this system, you will find it saves you a lot of time and effort.
5.9.4 Snippets
The calibre editor supports snippets. A snippet is a piece of text that is either re-used often or contains a lot of
redundant text. The editor allows you to insert a snippet with only a few key strokes. The snippets are very powerful,
with many features, such as placeholders you can jump between, automatic mirroring of repeated text and so on. For
more information, see Snippets (page ??).
The calibre Content server allows you to access your calibre libraries and read books directly in a browser on your
favorite mobile phone or tablet device. As a result, you do not need to install any dedicated book reading/management
apps on your phone. Just use the browser. The server downloads and stores the book you are reading in an off-line
cache so that you can read it even when there is no internet connection.
Contents
To start the server, click the Connect/share button and choose Start Content server. You might get a message from
your computer’s firewall or anti-virus program asking if it is OK to allow access to calibre.exe. Click the Allow
or OK button. Then open a browser (preferably Chrome or Firefox) in your computer and type in the following address:
http://127.0.0.1:8080
113
calibre User Manual, Release 4.21.0
This will open a page in the browser showing you your calibre libraries, click on any one and browse the books in it.
Click on a book, and it will show you all the metadata about the book, along with buttons to Read book and Download
book. Click the Read book button to start reading the book.
Note: The address used above http://127.0.0.1:8080 will only work on the computer that is running calibre.
To access the server from other computers/phones/tablets/etc. you will need to do a little more work, as described in
the next section.
There are two types of remote device access that you will typically need. The first, simpler kind is from within your
home network. If you are running calibre on a computer on your home network and you have also connected your
other devices to the same home network, then you should be easily able to access the server on those devices.
After starting the server in calibre as described above, click the Connect/share button again. Instead of the Start
Content server action, you should see a Stop Content server action instead. To the right of this action will be listed an
IP address and port number. These look like a bunch of numbers separated by periods. For example:
These numbers tell you what address to use to connect to the server in your devices. Following the example above, the
address becomes:
http://192.168.1.5:8080
The first part of the address is always http:// the next part is the IP address, which is the numbers before the
comma and finally we have the port number which must be added to the IP address with a colon (:). If you are lucky,
that should be all you need and you will be looking at the calibre libraries on your device. If not, read on.
If you are unable to access the server from your device, try the following steps:
1. Check that the server is running by opening the address http://127.0.0.1:8080 in a browser running on
the same computer as the server.
2. Check that your firewall/anti-virus is allowing connections to your computer on the port 8080 and to the calibre
program. The easiest way to eliminate the firewall/anti-virus as the source of problems is to temporarily turn
them both off and then try connecting. You should first disconnect from the internet, before turning off the
firewall, to keep your computer safe.
3. Check that your device and computer are on the same network. This means they should both be connected to the
same wireless router. In particular neither should be using a cellular or ISP provided direct-WiFi connection.
4. If you have non-standard networking setup, it might be that the IP address shown on the Connect/share menu is
incorrect. In such a case you will have to figure out what the correct IP address to use is, yourself. Unfortunately,
given the infinite diversity of network configurations possible, it is not possible to give you a roadmap for doing
so.
5. If you have setup a username and password, first try it without that to see if it is causing issues. Some e-
ink devices have browsers that do not handle authentication. You can sometimes workaround this by includ-
ing the username and password in the URL, for example: http://username:[email protected].
2:8080.
6. If you are stuck, you can always ask for help in the calibre user forums39 .
Warning: Before doing this you should turn on username/password protection in the server, otherwise anyone
in the world will be able to access your books. Go to Preferences→Sharing→Sharing over the net and enable the
option to Require username and password to access the content server.
While the particular details on setting up internet access vary depending on the network configuration and type of
computer you are using, the basic schema is as follows.
1. Find out the external IP address of the computer you are going to run the server on. You can do that by visiting
the site What is my IP address40 in a browser running on the computer.
2. If the computer is behind a router, enable port forwarding on the router to forward the port 8080 (or whatever
port you choose to run the calibre Content server on) to the computer.
3. Make sure the calibre server is allowed through any firewalls/anti-virus programs on your computer.
4. Now you should be able to access the server on any internet-connected device using the IP address you found in
the first step. For example, if the IP address you found was 123.123.123.123 and the port you are using for
the calibre server is 8080, the address to use on your device becomes: http://123.123.123.123:8080.
5. Optionally, use a service like no-ip41 to setup an easy to remember address to use instead of the IP address you
found in the first step.
Note: For maximum security, you should also enable HTTPS on the content server. You can either do so directly in
the server by providing the path to the HTTPS certificate to use in the advanced configuration options for the server,
or you can setup a reverse proxy as described below, to use an existing HTTPS setup.
The server interface is a simplified version of the main calibre interface, optimised for use with touch screens. The
home screen shows you books you are currently reading as well as allowing to choose a calibre library you want to
browse. The server in calibre gives you access to all your libraries, not just a single one, as before.
The server book list is a simple grid of covers. Tap on a cover to see the detailed metadata for a book, or to read the
book. If you prefer a more detailed list, you can change the default view by clicking the three vertical dots in the top
right corner.
39 https://www.mobileread.com/forums/forumdisplay.php?f=166
40 https://www.whatismyip.com/
41 https://www.noip.com/free
Sorting and searching of the book list should be familiar to calibre users. They can be accessed by clicking their icons
in the top right area. They both work exactly the same as in the main calibre program. The search page even allows
you to construct search queries by clicking on authors/tags/etc., just as you can using the Tag browser in the main
program.
A much loved feature of the main program, Virtual libraries is present in the server interface as well. Click the three
vertical dots in the top right corner to choose a Virtual library.
You can read any book in your calibre library by simply tapping on it and then tapping the Read book button. The
books reader is very simple to operate. You can both tap and swipe to turn pages. Swiping up/down skips between
chapters. Tapping the top quarter of the screen gets you the detailed controls and viewer preferences.
If you leave the Content server running, you can even open the same book on multiple devices and it will remember
your last read position. If it does not you can force a sync by tapping in the top quarter and choosing Sync.
Note: On initial release, the book reader is fully functional but is missing some more advanced features from the main
calibre viewer, such as popup footnotes, bookmarks and annotations in general. These will be added in due course. In
fact, the browser reader is designed to eventually replace the main viewer, once it matures.
The new calibre server makes lots of use of advanced HTML 5 and CSS 3 features. As such it requires an up-to-date
browser to use. It has been tested on Android Chrome and iOS Safari as well as Chrome and Firefox on the desktop.
It is known not to work with Internet Explorer and Microsoft Edge (hopefully Edge will start working when Microsoft
gets around to implementing a few missing standards).
The server is careful to use functionality that has either been already standardised or is on the standards track. As such
if it does not currently work with your favorite browser, it probably will once that browser has caught up.
If you are using a particularly old or limited browser or you don’t like to run JavaScript, you can use the mobile view,
by simply adding /mobile to the the server address.
Note: On iOS, Apple allows only a single browser engine, so Firefox, Chrome and Safari are all actually the same
browser under the hood. The new server interface requires iOS 10.3.2 or newer. On Android, the server has been
tested with Chrome version 58 and newer.
Browser makers have been trying to force people to use SSL by disabling advanced features in their browsers for plain
HTTP connections. One such casualty is offline support. So you may need to enable HTTPS on the server to get
offline support working. In addition, in Firefox on Android, you will need to type about:config and search for
browser.tabs.useCache and toggle it to true.
The calibre program has a nice section in Preferences to allow you to manage user accounts for the server. However,
if you want to run the standalone server and cannot run the main calibre program on the same computer/user account,
you can also manage users using just the command-line.
You can manage user accounts using the --manage-users option to the standalone calibre-server program.
Suppose you want to store the user database in the directory /srv/calibre, then you create it by running:
Just follow the prompts to create user accounts, set their permission, etc. Once you are done, you can run the server
as:
It will use the user accounts you created in the previous step.
Here, we will show you how to integrate the calibre Content server into another server. The most common reason for
this is to make use of SSL or to serve the calibre library as part of a larger site. The basic technique is to run the calibre
server and setup a reverse proxy to it from the main server.
A reverse proxy is when your normal server accepts incoming requests and passes them onto the calibre server. It then
reads the response from the calibre server and forwards it to the client. This means that you can simply run the calibre
server as normal without trying to integrate it closely with your main server.
The simplest configuration is to dedicate a full virtual host to the calibre server. In this case, run the calibre server as:
calibre-server
Now setup the virtual host in your main server, for example, for nginx:
server {
listen [::]:80;
server_name myserver.example.com;
location / {
proxy_pass http://127.0.0.1:8080;
}
}
<VirtualHost *:80>
ServerName myserver.example.com
AllowEncodedSlashes On
(continues on next page)
If you do not want to dedicate a full virtual host to calibre, you can have it use a URL prefix. Start the calibre server
as:
The key parameter here is --url-prefix /calibre. This causes the Content server to serve all URLs prefixed
by /calibre. To see this in action, visit http://localhost:8080/calibre in your browser. You should
see the normal Content server website, but now it will run under /calibre.
With nginx, the required configuration is:
For Apache, first enable the proxy modules in Apache, by adding the following to httpd.conf:
The exact technique for enabling the proxy modules will vary depending on your Apache installation. Once you have
the proxy modules enabled, add the following rules to httpd.conf (or if you are using virtual hosts to the conf file
for the virtual host in question):
AllowEncodedSlashes On
RewriteEngine on
RewriteRule ^/calibre/(.*) http://127.0.0.1:8080/calibre/$1 [proxy]
RedirectMatch permanent ^/calibre$ /calibre/
That’s all, you will now be able to access the calibre Content server under the /calibre URL in your main server.
The above rules pass all requests under /calibre to the calibre server running on port 8080 and thanks to the
--url-prefix option above, the calibre server handles them transparently.
Note: When using a reverse proxy, you should tell the calibre Content server to only listen on localhost, by using
--listen-on 127.0.0.1. That way, the server will only listen for connections coming from the same computer,
i.e. from the reverse proxy.
Note: If you have setup SSL for your main server, you should tell the calibre server to use basic authentication instead
of digest authentication, as it is faster. To do so, pass the --auth-mode=basic option to calibre-server.
6.7 Creating a service for the calibre server on a modern Linux sys-
tem
You can easily create a service to run calibre at boot on a modern (systemd42 ) based Linux system. Just create the file
/etc/systemd/system/calibre-server.service with the contents shown below:
[Unit]
Description=calibre content server
After=network.target
[Service]
Type=simple
User=mylinuxuser
Group=mylinuxgroup
ExecStart=/opt/calibre/calibre-server "/path/to/calibre library directory"
[Install]
WantedBy=multi-user.target
Change mylinuxuser and mylinuxgroup to whatever user and group you want the server to run as. This should
be the same user and group that own the files in the calibre library directory. Note that it is generally not a good idea to
run the server as root. Also change the path to the calibre library directory to suit your system. You can add multiple
libraries if needed. See the help for the calibre-server command.
Now run:
Note: The calibre server does not need a running X server, but it does need the X libraries installed as some compo-
nents it uses link against them.
Note: The calibre server also supports systemd socket activation, so you can use that, if needed, as well.
42 https://www.freedesktop.org/wiki/Software/systemd/
6.7. Creating a service for the calibre server on a modern Linux system 119
calibre User Manual, Release 4.21.0
Comparing e-books
calibre includes an integrated e-book comparison tool that can be used to see what has changed inside an e-book after
editing or converting it. It can compare books in the EPUB and AZW3 formats.
To use it, either open the e-book in the tool for Editing e-books (page 79) and then click File→Compare to other book
or use the Book details (page 16) panel. If you do a conversion from EPUB to EPUB, the original EPUB file will be
saved as ORIGINAL_EPUB. Simply right click on the ORIGINAL_EPUB entry in the Book details panel and choose
Compare to EPUB format.
The comparison tool that opens will look like the screenshot below. It shows you the differences in text, styles and
images in the chosen books.
121
calibre User Manual, Release 4.21.0
As can be seen in the screenshot above, the comparison view shows the differences between the two books side by
side. Only the differences, with a few lines of context around them are shown. This makes it easy to see at a glance
only what was changed inside a large document like a book.
Added text is shown with a green background, removed text with a red background and changed text with a blue
background.
The line numbers of all changed text are show at the sides, making it easy to go to a particular change in the editor.
When you open the comparison tool from within the editor, you can also double click on a line in the right panel to go
to that line in the editor automatically.
One useful technique when comparing books is to tell the comparison tool to beautify the text and style files before
calculating differences. This can often result in cleaner and easier to follow differences. To do this, click the Options
button in the bottom right and choose Beautify files before comparing. Note that beautifying can sometimes have
undesired effects, as it can cause invalid markup to be altered to make it valid. You can also change the number of
lines of context shown around differences via the Options button.
You can search for any text in the differences via the Search bar at the bottom. You will need to specify which panel
to search, the Left or the Right.
The comparison tool is most useful when you have two versions of the same book and you want to see what is different
between them. To that end, there are several ways to launch the tool.
Open the first file in the Editing e-books (page 79) tool. Now click File→Compare to another book and choose the
second file (it must be in the same format as the first). The comparison view will open with the file being edited on the
right and the second file on the left.
When you do a conversion in calibre from a FMT to itself, the original file is saved as ORIGINAL_FMT. You can see
what was changed by the conversion, by right clicking on the ORIGINAL_FMT entry in the Book details (page 16)
panel in the main calibre window and selecting Compare to FMT. The comparison view will open with ORIGI-
NAL_FMT on the left and FMT on the right.
7.2.3 Comparing a checkpoint to the current state of the book while editing
The Editing e-books (page 79) tool has a very useful feature, called Checkpoints (page 91). This allows you to save
the current state of the book as a named checkpoint, to which you can revert if you do not like the changes you have
made since creating the checkpoint. Checkpoints are also created automatically when you perform various automated
actions in the editor. You can see the list of checkpoints by going to View→Checkpoints and then use the Compare
button to compare the book at the selected checkpoint with the current state. The comparison tool will show the
checkpoint on the left and the current state on the right.
Contents
E-books come in all shapes and sizes and more often than not, their metadata (things like title/author/series/publisher)
is incomplete or incorrect. The simplest way to change metadata in calibre is to simply double click on an entry and
type in the correct replacement. For more sophisticated, “power editing” use the edit metadata tools discussed below.
Click the book you want to edit and then click the Edit metadata button or press the E key. A dialog opens that allows
you to edit all aspects of the metadata. It has various features to make editing faster and more efficient. A list of the
commonly used tips:
• You can click the button in between title and authors to swap them automatically.
• You can click the button next to author sort to have calibre automatically fill it in using the sort values stored
with each author. Use the Manage authors dialog to see and change the authors’ sort values. This dialog can be
opened by clicking and holding the button next to author sort.
• You can click the button next to tags to use the Tag editor to manage the tags associated with the book.
125
calibre User Manual, Release 4.21.0
• The “Ids” box can be used to enter an ISBN (and many other types of id), it will have a red background if you
enter an invalid ISBN. It will be green for valid ISBNs.
• The author sort box will be red if the author sort value differs from what calibre thinks it should be.
The nicest feature of the edit metadata dialog is its ability to automatically fill in many metadata fields by getting
metadata from various websites. Currently, calibre uses isbndb.com, Google Books, Amazon and Library Thing. The
metadata download can fill in Title, author, series, tags, rating, description and ISBN for you.
To use the download, fill in the title and author fields and click the Fetch metadata button. calibre will present you
with a list of books that most closely match the title and author. If you fill in the ISBN field first, it will be used in
preference to the title and author. If no matches are found, try making your search a little less specific by including
only some key words in the title and only the author last name.
In calibre, a single book entry can have many different formats associated with it. For example you may have obtained
the Complete Works of Shakespeare in EPUB format and later converted it to MOBI to read on your Kindle. calibre
automatically manages multiple formats for you. In the Available formats section of the Edit metadata dialog, you can
manage these formats. You can add a new format, delete an existing format and also ask calibre to set the metadata
and cover for the book entry from the metadata in one of the formats.
You can ask calibre to download book covers for you, provided the book has a known ISBN. Alternatively you can
specify a file on your computer to use as the cover. calibre can even generate a default cover with basic metadata on it
for you. You can drag and drop images onto the cover to change it and also right click to copy/paste cover images.
In addition, there is a button to automatically trim borders from the cover, in case your cover image has an ugly border.
First select the books you want to edit by holding Ctrl or Shift and clicking on them. If you select more than one book,
clicking the Edit metadata button will cause the Bulk metadata edit dialog to open. Using this dialog, you can quickly
set the author/publisher/rating/tags/series etc of a bunch of books to the same value. This is particularly useful if you
have just imported a number of books that have some metadata in common. This dialog is very powerful, for example,
it has a Search and Replace tab that you can use to perform bulk operations on metadata and even copy metadata from
one column to another.
The normal edit metadata dialog also has Next and Previous buttons that you can use to edit the metadata of several
books one after the other.
The Bulk metadata edit dialog allows you to perform arbitrarily powerful search and replace operations on the selected
books. By default it uses a simple text search and replace, but it also support regular expressions. For more on regular
expressions, see All about using regular expressions in calibre (page 192).
As noted above, there are two search and replace modes: character match and regular expression. Character match
will look in the Search field you choose for the characters you type in the search for box and replace those characters
with what you type in the replace with box. Each occurance of the search characters in the field will be replaced. For
example, assume the field being searched contains a bad cat. If you search for a to be replaced with HELLO, then the
result will be HELLO bHELLOd cHELLOt.
If the field you are searching on is a multiple field like tags, then each tag is treated separately. For example, if your
tags contain Horror, Scary, the search expression r, will not match anything because the expression will first be applied
to Horror and then to Scary.
If you want the search to ignore upper/lowercase differences, uncheck the Case sensitive box.
You can have calibre change the case of the result (information after the replace has happened) by choosing one of the
functions from the Apply function after replace box. The operations available are:
• Lower case – change all the characters in the field to lower case
• Upper case – change all the characters in the field to upper case
• Title case – capitalize each word in the result.
The Your test box is provided for you to enter text to check that search/replace is doing what you want. In the majority
of cases the book test boxes will be sufficient, but it is possible that there is a case you want to check that isn’t shown
in these boxes. Enter that case into Your test.
Regular expression mode has some differences from character mode, beyond (of course) using regular expressions.
The first is that functions are applied to the parts of the string matched by the search string, not the entire field. The
second is that functions apply to the replacement string, not to the entire field.
The third and most important is that the replace string can make reference to parts of the search string by using
backreferences. A backreference is \\n where n is an integer that refers to the n’th parenthesized group in the search
expression. For example, given the same example as above, a bad cat, a search expression a (. . . ) (. . . ), and a replace
expression a \2 \1, the result will be a cat bad. Please see the All about using regular expressions in calibre (page 192)
for more information on backreferences.
One useful pattern: assume you want to change the case of an entire field. The easiest way to do this is to use character
mode, but lets further assume you want to use regular expression mode. The search expression should be (.*) the
replace expression should be \1, and the desired case change function should be selected.
Finally, in regular expression mode you can copy values from one field to another. Simply make the source and
destination field different. The copy can replace the destination field, prepend to the field (add to the front), or append
to the field (add at the end). The ‘use comma’ checkbox tells calibre to (or not to) add a comma between the text and
the destination field in prepend and append modes. If the destination is multiple (e.g., tags), then you cannot uncheck
this box.
Search and replace is done after all the other metadata changes in the other tabs are applied. This can lead to some
confusion, because the test boxes will show the information before the other changes, but the operation will be applied
after the other changes. If you have any doubts about what is going to happen, do not mix search/replace with other
changes.
If you want to download the metadata for multiple books at once, right-click the Edit metadata button and select
Download metadata. You can choose to download only metadata, only covers, or both.
Contents
Contents
129
calibre User Manual, Release 4.21.0
calibre supports the conversion of many input formats to many output formats. It can convert every input format in the
following list, to every output format.
Input Formats: AZW, AZW3, AZW4, CBZ, CBR, CBC, CHM, DJVU, DOCX, EPUB, FB2, FBZ, HTML, HTMLZ,
LIT, LRF, MOBI, ODT, PDF, PRC, PDB, PML, RB, RTF, SNB, TCR, TXT, TXTZ
Output Formats: AZW3, EPUB, DOCX, FB2, HTMLZ, OEB, LIT, LRF, MOBI, PDB, PMLZ, RB, PDF, RTF, SNB,
TCR, TXT, TXTZ, ZIP
Note: PRC is a generic format, calibre supports PRC files with TextRead and MOBIBook headers. PDB is also a
generic format. calibre supports eReader, Plucker (input only), PML and zTxt PDB files. DJVU support is only for
converting DJVU files that contain embedded text. These are typically generated by OCR software. MOBI books can
be of two types Mobi6 and KF8. calibre fully supports both. MOBI files often have .azw or .azw3 file extensions.
DOCX files from Microsoft Word 2007 and newer are supported.
In order of decreasing preference: LIT, MOBI, AZW, EPUB, AZW3, FB2, FBZ, DOCX, HTML, PRC, ODT, RTF,
PDB, TXT, PDF
9.1.3 I converted a PDF file, but the result has various problems?
PDF is a terrible format to convert from. For a list of the various issues you will encounter when converting PDF, see:
Convert PDF documents (page 74).
The first thing to realize is that most e-books have two tables of contents. One is the traditional Table of Contents, like
the ToC you find in paper books. This Table of Contents is part of the main document flow and can be styled however
you like. This ToC is called the content ToC.
Then there is the metadata ToC. A metadata ToC is a ToC that is not part of the book text and is typically accessed by
some special button on a reader. For example, in the calibre viewer, you use the Show Table of Contents button to see
this ToC. This ToC cannot be styled by the book creator. How it is represented is up to the viewer program.
In the MOBI format, the situation is a little confused. This is because the MOBI format, alone amongst mainstream
e-book formats, does not have decent support for a metadata ToC. A MOBI book simulates the presence of a metadata
ToC by putting an extra content ToC at the end of the book. When you click Goto Table of Contents on your Kindle,
it is to this extra content ToC that the Kindle takes you.
Now it might well seem to you that the MOBI book has two identical ToCs. Remember that one is semantically a
content ToC and the other is a metadata ToC, even though both might have exactly the same entries and look the same.
One can be accessed directly from the Kindle’s menus, the other cannot.
When converting to MOBI, calibre detects the metadata ToC in the input document and generates an end-of-file ToC
in the output MOBI file. You can turn this off by an option in the MOBI Output settings. You can also tell calibre
whether to put it and the start or the end of the book via an option in the MOBI Output settings. Remember this ToC
is semantically a metadata ToC, in any format other than MOBI it cannot not be part of the text. The fact that it is part
of the text in MOBI is an accident caused by the limitations of MOBI. If you want a ToC at a particular location in
your document text, create one by hand. So we strongly recommend that you leave the default as it is, i.e. with the
metadata ToC at the end of the book. Also note that if you disable the generation of the end-of-file ToC the resulting
MOBI file may not function correctly on a Kindle, since the Kindle’s use the metadata ToC for many things, including
the Page Flip feature.
If you have a hand edited ToC in the input document, you can use the ToC detection options in calibre to automatically
generate the metadata ToC from it. See the conversion section of the User Manual for more details on how to use these
options.
Finally, I encourage you to ditch the content ToC and only have a metadata ToC in your e-books. Metadata ToCs will
give the people reading your e-books a much superior navigation experience (except on the Kindle, where they are
essentially the same as a content ToC).
Note: The newer AZW3 format has proper support for a metadata ToC. However, the Kindle firmware tends to
malfunction if you disable the generation of the end-of-file inline ToC. So it is recommended that you leave the
generated ToC alone. If you create an AZW3 file with a metadata ToC and no end-of-file generated ToC, some
features on the Kindle will not work, such as the Page Flip feature.
9.1.6 The covers for my MOBI files have stopped showing up in Kindle for
PC/Kindle for Android/iPad etc.
This is caused by a bug in the Amazon software. You can work around it by going to
Preferences→Conversion→Output Options→MOBI output and setting the Enable sharing of book content op-
tion. If you are reconverting a previously converted book, you will also have to enable the option in the conversion
dialog for that individual book (as per book conversion settings are saved and take precedence).
Note that doing this will mean that the generated MOBI will show up under personal documents instead of Books on
the Kindle Fire and Amazon whispersync will not work, but the covers will. It’s your choice which functionality is
more important to you. I encourage you to contact Amazon and ask them to fix this bug.
The bug in Amazon’s software is that when you put a MOBI file on a Kindle, unless the file is marked as a Personal
document, Amazon assumes you bought the book from it and tries to download the cover thumbnail for it from its
servers. When the download fails, it refuses to fallback to the cover defined in the MOBI file. This is likely deliberate
on Amazon’s part to try to force authors to sell only through them. In other words, the Kindle only displays covers for
books marked as Personal Documents or books bought directly from Amazon.
If you send a MOBI file to an e-ink Kindle with calibre using a USB connection, calibre works around this Amazon
bug by uploading a cover thumbnail itself. However, that workaround is only possible when using a USB connection
and sending with calibre. Note that if you send using email, Amazon will automatically mark the MOBI file as a
Personal Document and the cover will work, but the book will show up in Personal Documents.
In order to convert a collection of HTML files in a specific order, you have to create a table of contents file. That is,
another HTML file that contains links to all the other files in the desired order. Such a file looks like:
<html>
<body>
<h1>Table of Contents</h1>
<p style="text-indent:0pt">
<a href="file1.html">First File</a><br/>
<a href="file2.html">Second File</a><br/>
.
.
.
</p>
</body>
</html>
Then, just add this HTML file to the GUI and use the Convert button to create your e-book. You can use the option in
the Table of Contents section in the conversion dialog to control how the Table of Contents is generated.
Note: By default, when adding HTML files, calibre follows links in the files in depth first order. This means that if
file A.html links to B.html and C.html and D.html, but B.html also links to D.html, then the files will be in the order
A.html, B.html, D.html, C.html. If instead you want the order to be A.html, B.html, C.html, D.html then you must tell
calibre to add your files in breadth first order. Do this by going to Preferences→Advanced→Plugins and customizing
the HTML to ZIP plugin.
calibre does not guarantee that an EPUB produced by it is valid. The only guarantee it makes is that if you feed it
valid XHTML 1.1 + CSS 2.1 it will output a valid EPUB. calibre tries hard to ensure that EPUBs it produces actually
work as intended on a wide variety of devices, a goal that is incompatible with producing valid EPUBs, and one that
is far more important to the vast majority of its users. If you need a tool that always produces valid EPUBs, calibre
is not for you. This means, that if you want to send a calibre produced EPUB to an online store that uses an EPUB
validity checker, you have to make sure that the EPUB is valid yourself, calibre will not do it for you – in other words
you must feed calibre valid XHTML + CSS as the input documents.
9.1.9 How do I use some of the advanced features of the conversion tools?
You can get help on any individual feature of the converters by mousing over it in the GUI or running
ebook-convert dummy.html .epub -h at a terminal. A good place to start is to look at the following demo
file that demonstrates some of the advanced features html-demo.zip43
43 https://calibre-ebook.com/downloads/html-demo.zip
Contents
calibre can directly connect to all the major (and most of the minor) e-book reading devices, smartphones, tablets, etc.
In addition, using the Connect to folder function you can use it with any e-book reader that exports itself as a USB
disk. Finally, you can connect wirelessly to any device that has a web browser using the calibre Content server.
If your device appears as a USB disk to the operating system, adding support for it to calibre is very easy. We just
need some information from you:
• Complete list of e-book formats that your device supports.
• Is there a special directory on the device in which all e-book files should be placed? Also does the device detect
files placed in sub-directories?
• We also need information about your device that calibre will collect automatically. First, if your device supports
SD cards, insert them. Then connect your device to the computer. In calibre go to Preferences→Miscellaneous
and click the “Debug device detection” button. This will create some debug output. Copy it to a file and repeat
the process, this time with your device disconnected from your computer.
• Send both the above outputs to us with the other information and we will write a device driver for your device.
Once you send us the output for a particular operating system, support for the device in that operating system will
appear in the next release of calibre. To send us the output, open a bug report and attach the output to it. See calibre
bugs44 .
44 https://calibre-ebook.com/bugs
In addition to the Connect to folder function found under the Connect/share button, calibre provides a User
defined device plugin that can be used to connect to any USB device that shows up as a disk drive in your
operating system. Note: on Windows, the device must have a drive letter for calibre to use it. See the device
plugin Preferences -> Plugins -> Device plugins -> User defined and Preferences ->
Miscellaneous -> Get information to setup the user defined device for more informa-
tion. Note that if you are using the user defined plugin for a device normally detected by a builtin calibre plugin,
you must disable the builtin plugin first, so that your user defined plugin is used instead.
The easiest way to transfer books wirelessly to your Apple device (iPad/iPhone/iPod) is to use the Calibre Compan-
ion47 iOS app. This app allows calibre to connect to your Apple device wirelessly, just as though you plugged in the
device with a USB cable. You can browse files on the device in calibre and use the Send to device button to transfer
files to your device wirelessly.
Another easy way to browse your calibre collection from your Apple device is by using the calibre Content server,
which makes your collection available over the net. First perform the following steps in calibre
• Set the Preferred Output Format in calibre to EPUB (The output format can be set under
Preferences→Interface→Behavior)
• Set the output profile to iPad (this will work for iPhone/iPods as well), under
Preferences→Conversion→Common options→Page setup
45 https://calibre-ebook.com/download
46 https://bugs.launchpad.net/calibre
47 https://calibrecompanion.co?utm_source=Calibre&utm_medium=Website&utm_campaign=Main&utm_term=FAQ&utm_content=IOS
• Convert the books you want to read on your iDevice to EPUB format by selecting them and clicking the Convert
button.
• Turn on the Content server by clicking the Connect/share button and leave calibre running. You can also tell
calibre to automatically start the Content server via Preferences→Sharing→Sharing over the net.
The Content server allows you to read books directly in Safari itself. In addition, there are many apps for your iDevice
that can connect to the calibre Content server. Examples include: Marvin, Mapleread and iBooks itself.
Start the Safari browser and type in the IP address and port of the computer running the calibre server, like this:
http://192.168.1.2:8080/
Replace 192.168.1.2 with the local IP address of the computer running calibre. See The calibre Content server
(page ??) for details on running the server and finding out the right IP address to use.
You will see a list of books in Safari, tap on any book and you will be given the option to either download it, or read it
in the browser itself. If you choose to download it, Safari will ask you if you want to open it with iBooks.
9.2.6 How do I use calibre with my Android phone/tablet or Kindle Fire HD?
There are two ways that you can connect your Android device to calibre. Using a USB cable – or wirelessly, over the
air. The first step to using an Android device is installing an e-book reading application on it. There are many free
and paid e-book reading applications for Android: Some examples (in no particular order): FBReader48 , Moon+49 ,
Mantano50 , Aldiko51 , Kindle52 .
Simply plug your device into the computer with a USB cable. calibre should automatically detect the device and
then you can transfer books to it by clicking the Send to device button. Note that on macOS and Linux only a single
program can connect to an Android device at a time, so make sure the device is not opened in the OS File manager, or
the Android File Transfer utility, etc.
Note: With newer Android devices, you might have to jump through a few hoops to get the connection working,
as Google really does not want you to be independent of its cloud. First, unlock the screen before plugging in the
USB cable. When you plugin in the USB cable you will get a popup notification. Make sure it says some thing like
“Transferring Media files” or “MTP (Media Transfer mode)”. If it does not, tap the notification, and change the mode
to Media Transfer (MTP). You may need to restart calibre at this point in order for your device to be recognized.
Finally, you might get a popup on the device every time calibre or the operating system actually tries to connect to it,
asking for permission, tap OK.
Note: With the Kindle Fire 8 or newer there is an icon that shows up when the USB cable is plugged in, showing that
the device is charging. Tap that and switch the device to data transfer mode, and then start calibre, it should then be
detected.
48 https://play.google.com/store/apps/details?id=org.geometerplus.zlibrary.ui.android&hl=en
49 https://play.google.com/store/apps/details?id=com.flyersoft.moonreader&hl=en
50 https://play.google.com/store/apps/details?id=com.mantano.reader.android.lite&hl=en
51 https://play.google.com/store/apps/details?id=com.aldiko.android&hl=en
52 https://play.google.com/store/apps/details?id=com.amazon.kindle&feature=related_apps
The easiest way to transfer books wirelessly to your Android device is to use the Calibre Companion53 Android app.
This app allows calibre to connect to your Android device wirelessly, just as though you plugged in the device with
a USB cable. You can browse files on the device in calibre and use the Send to device button to transfer files to your
device wirelessly.
calibre also has a builtin web server, the Content server. You can browse your calibre collection on your Android
device by using the calibre Content server, which makes your collection available over the net. First perform the
following steps in calibre
• Set the Preferred Output Format in calibre to EPUB for normal Android devices or MOBI for Kindles (The
output format can be set under Preferences→Interface→Behavior)
• Convert the books you want to read on your device to EPUB/MOBI format by selecting them and clicking the
Convert button.
• Turn on the Content server in calibre’s preferences and leave calibre running.
Now on your Android device, open the browser and browse to
http://192.168.1.2:8080/
Replace 192.168.1.2 with the local IP address of the computer running calibre. See The calibre Content server
(page ??) for details on running the server and finding out the right IP address to use.
You can now browse your book collection and download books from calibre to your device to open with whatever
e-book reading software you have on your android device.
Calibre Companion and many reading apps support browsing the calibre library directly. For example, in Aldiko, click
My Catalogs, then + to add a catalog, then give the catalog a title such as “calibre” and provide the URL listed above.
You can now browse the calibre library and download directly into the reading software.
9.2.7 Can I access my calibre books using the web browser in my Kindle or other
reading device?
calibre has a Content server that exports the books in calibre as a web page. See The calibre Content server (page ??)
for details.
Some devices, like the Kindle (1/2/DX), do not allow you to access port 8080 (the default port on which the content
server runs). In that case, change the port in the calibre Preferences to 80. (On some operating systems, you may not
be able to run the server on a port number less than 1024 because of security settings. In this case the simplest solution
is to adjust your router to forward requests on port 80 to port 8080).
Also some devices do not have browsers advanced enough to run the app-like interface used by the content server. For
such devices, you can simply add /mobile to the server URL to get a simplified, non-JavaScript interface.
Because of the large amount of spam in email, sending email can be tricky, as different mail servers use different
strategies to block email. The most common problem is if you are sending email directly (without a mail relay) in
calibre. Many servers (for example, Amazon) block email that does not come from a well known relay. The most
robust way to setup email sending in calibre is to do the following:
• Create a free GMX account at GMX54 .
53 https://calibrecompanion.co?utm_source=Calibre&utm_medium=Website&utm_campaign=Main&utm_term=FAQ&utm_content=Android
54 https://www.gmx.com
• Goto Preferences→Sharing→Sharing books by email in calibre and click the Use GMX button and fill in the
information asked for.
• Log into your GMX account on the website and enable SMTP sending (Settings->POP3 & IMAP->Send and
receive emails via external program)
• calibre will then be able to use GMX to send the mail.
• If you are sending to your Kindle, remember to update the email preferences on your Amazon Kindle page to
allow email sent from your GMX email address. Also note that Amazon does not allow email delivery of AZW3
and new style (KF8) MOBI files.
Even after doing this, you may have problems. One common source of problems is that some poorly designed antivirus
programs block calibre from opening a connection to send email. Try adding an exclusion for calibre in your antivirus
program.
Note: Microsoft/Google/GMX can disable your account if you use it to send large amounts of email. So,
when using these services to send mail calibre automatically restricts itself to sending one book every five min-
utes. If you don’t mind risking your account being blocked you can reduce this wait interval by going to
Preferences→Advanced→Tweaks in calibre.
Note: Google recently deliberately broke their email sending protocol (SMTP) support in an attempt to force everyone
to use their web interface so they can show you more ads. They are trying to claim that SMTP is insecure, that is
incorrect and simply an excuse. If you have trouble with gmail you will need to allow “less secure” apps as described
here55 .
Note: If you are concerned about giving calibre access to your email account, simply create a new free email account
with GMX or Hotmail and use it only for calibre.
Linux kernels mount devices read-only when their filesystems have errors. You can repair the filesystem with:
Replace /dev/sdc with the path to the device node of your device. You can find the device node of your device, which
will always be under /dev by examining the output of:
mount
9.2.10 Why does calibre not support collections on the Kindle or shelves on the
Nook?
Neither the Kindle nor the Nook provide any way to manipulate collections over a USB connection. If you really care
about using collections, I would urge you to sell your Kindle/Nook and get a Kobo. Only Kobo seems to understand
that life is too short to be entering collections one by one on an e-ink screen :)
55 https://support.google.com/accounts/answer/6010255
Note that in the case of the Kindle, there is a way to manipulate collections via USB, but it requires that the Kindle
be rebooted every time it is disconnected from the computer, for the changes to the collections to be recognized. As
such, it is unlikely that any calibre developers will ever feel motivated enough to support it. There is however, a calibre
plugin that allows you to create collections on your Kindle from the calibre metadata. It is available from here56 .
Note: Amazon have removed the ability to manipulate collections completely in their newer models, like the Kindle
Touch and Kindle Fire, making even the above plugin useless, unless you root your Kindle and install custom firmware.
9.2.11 I am getting an error when I try to use calibre with my Kobo Touch/Glo/etc.?
The Kobo has very buggy firmware. Connecting to it has been known to fail at random. Certain combinations of
motherboard, USB ports/cables/hubs can exacerbate this tendency to fail. If you are getting an error when connecting
to your touch with calibre try the following, each of which has solved the problem for some calibre users.
• Connect the Kobo directly to your computer, not via USB Hub
• Try a different USB cable and a different USB port on your computer
• Log out of the Kobo and log in again, this causes it to rebuild the database, fixing corrupted database errors.
• Try upgrading the firmware on your Kobo Touch to the latest
• Try resetting the Kobo (sometimes this cures the problem for a little while, but then it re-appears, in which case
you have to reset again and again)
• Try only putting one or two books onto the Kobo at a time and do not keep large collections on the Kobo
9.2.12 Covers for books I send to my e-ink Kindle show up momentarily and then
are replaced by a generic cover?
This happens because of an Amazon bug. They try to download a cover for the book from their servers and when
that fails, they replace the existing cover that calibre created with a generic cover. For details see this forum thread57 .
As of version 4.17, calibre has a workaround, where if you connect the Kindle to calibre after the covers have been
destroyed by Amazon, calibre will restore them automatically. So in order to see the covers on your Kindle, you have
to:
1) Send the book to the Kindle with calibre
2) Disconnect the Kindle and wait for Amazon to destroy the cover
3) Reconnect the Kindle to calibre
Note that this workaround only works for books sent with calibre 4.17 or later. Alternately, simply keep your Kindle
in airplane mode, you don’t really want Amazon knowing every book you read anyway. I encourage you to contact
Amazon customer support and complain loudly about this bug. Maybe Amazon will listen.
Note: If the workaround is not working for you make sure you Kindle firmware is at least version 5.12.5, released in
April 2020.
56 https://www.mobileread.com/forums/showthread.php?t=244202
57 https://www.mobileread.com/forums/showthread.php?t=329945
9.2.13 I transferred some books to my Kindle using calibre and they did not show
up?
Books sent to the Kindle only show up on the Kindle after they have been indexed by the Kindle. This can take some
time. If the book still does not show up after some time, then it is likely that the Kindle indexer crashed. Sometimes
a particular book can cause the indexer to crash. Unfortunately, Amazon has not provided any way to deduce which
book is causing a crash on the Kindle. Your only recourse is to either reset the Kindle, or delete all files from its
memory using Windows Explorer (or whatever file manager you use) and then send the books to it again, one by
one, until you discover the problem book. Once you have found the problem book, delete it off the Kindle and do a
MOBI to MOBI or MOBI to AZW3 conversion in calibre and then send it back. This will most likely take care of the
problem.
Contents
When you first run calibre, it will ask you for a folder in which to store your books. Whenever you add a book to
calibre, it will copy the book into that folder. Books in the folder are nicely arranged into sub-folders by Author and
Title. Note that the contents of this folder are automatically managed by calibre, do not add any files/folders manually
to this folder, as they may be automatically deleted. If you want to add a file associated to a particular book, use the
top right area of Edit metadata dialog to do so. Then, calibre will automatically put that file into the correct folder and
move it around when the title/author changes.
Metadata about the books is stored in the file metadata.db at the top level of the library folder. This file is a sqlite
database. When backing up your library make sure you copy the entire folder and all its sub-folders.
The library folder and all its contents make up what is called a calibre library. You can have multiple such libraries.
To manage the libraries, click the calibre icon on the toolbar. You can create new libraries, remove/rename existing
ones and switch between libraries easily.
You can copy or move books between different libraries (once you have more than one library setup) by right clicking
on a book and selecting the Copy to library action.
Author names are complex, especially across cultures, see this note58 for some of the complexities. calibre has a
very flexible strategy for managing author names. The first thing to understand is that books and authors are separate
entities in calibre. A book can have more than one author, and an author can have more than one book. You can
manage the authors of a book by the edit metadata dialog. You can manage individual authors by right clicking on the
author in the Tag browser on the left of the main calibre screen and selecting Manage authors. Using this dialog you
can change the name of an author and also how that name is sorted. This will automatically change the name of the
author in all the books of that author. When a book has multiple authors, separate their names using the & character.
Now coming to author name sorting:
• When a new author is added to calibre (this happens whenever a book by a new author is added), calibre
automatically computes a sort string for both the book and the author.
• Authors in the Tag browser are sorted by the sort value for the authors. Remember that this is different from
the Author sort field for a book.
• By default, this sort algorithm assumes that the author name is in First name Last name format and
generates a Last name, First name sort value.
• You can change this algorithm by going to Preferences→Advanced→Tweaks and setting the au-
thor_sort_copy_method tweak.
• You can force calibre to recalculate the author sort values for every author by right clicking on any author and
selecting Manage authors, then pushing the Recalculate all author sort values button. Do this after you have set
the author_sort_copy_method tweak to what you want.
• You can force calibre to recalculate the author sort values for all books by using the bulk metadata edit dialog
(select all books and click edit metadata, check the Automatically set author sort checkbox, then press OK.)
• When recalculating the author sort values for books, calibre uses the author sort values for each individual author.
Therefore, ensure that the individual author sort values are correct before recalculating the books’ author sort
values.
• You can control whether the Tag browser display authors using their names or their sort values by setting the
categories_use_field_for_author_name tweak in Preferences→Advanced→Tweaks
Note that you can set an individual author’s sort value to whatever you want using Manage authors. This is useful
when dealing with names that calibre will not get right, such as complex multi-part names like Miguel de Cervantes
Saavedra or when dealing with Asian names like Sun Tzu.
With all this flexibility, it is possible to have calibre manage your author names however you like. For example, one
common request is to have calibre display author names LN, FN. To do this, and if the note below does not apply to
you, then:
• Set the author_sort_copy_method tweak to copy as described above.
• Restart calibre. Do not change any book metadata before doing the remaining steps.
• Change all author names to LN, FN using the Manage authors dialog.
• After you have changed all the authors, press the Recalculate all author sort values button.
• Press OK, at which point calibre will change the authors in all your books. This can take a while.
Note:
When changing from FN LN to LN, FN, it is often the case that the values in author_sort are already in LN, FN format. If this is
58 https://www.w3.org/International/questions/qa-personal-names.en.php?changelang=en
9.3.3 Why doesn’t calibre let me store books in my own directory structure?
The whole point of calibre’s library management features is that they provide a search and sort based interface for
locating books that is much more efficient than any possible directory scheme you could come up with for your
collection. Indeed, once you become comfortable using calibre’s interface to find, sort and browse your collection,
you wont ever feel the need to hunt through the files on your disk to find a book again. By managing books in
its own directory structure of Author -> Title -> Book files, calibre is able to achieve a high level of reliability and
standardization. To illustrate why a search/tagging based interface is superior to folders, consider the following.
Suppose your book collection is nicely sorted into folders with the following scheme:
Now this makes it very easy to find for example all science fiction books by Isaac Asimov in the Foundation series.
But suppose you want to find all unread science fiction books. There’s no easy way to do this with this folder scheme,
you would instead need a folder scheme that looks like:
In calibre, you would instead use tags to mark genre and read status and then just use a simple search query like
tag:scifi and not tag:read. calibre even has a nice graphical interface, so you don’t need to learn its
search language instead you can just click on tags to include or exclude them from the search.
To those of you that claim that you need access to the filesystem, so that you can have access to your books over the
network, calibre has an excellent Content server that gives you access to your calibre library over the net.
If you are worried that someday calibre will cease to be developed, leaving all your books marooned in its folder
structure, explore the powerful Save to Disk feature in calibre that lets you export all your files into a folder structure
of arbitrary complexity based on their metadata.
Finally, the reason there are numbers at the end of every title folder, is for robustness. That number is the id number of
the book record in the calibre database. The presence of the number allows you to have multiple records with the same
title and author names. It is also part of what allows calibre to magically regenerate the database with all metadata if
the database file gets corrupted. Given that calibre’s mission is to get you to stop storing metadata in filenames and
stop using the filesystem to find things, the increased robustness afforded by the id numbers is well worth the uglier
folder names.
If you are still not convinced, then I’m afraid calibre is not for you. Look elsewhere for your book cataloguing needs.
Just so we’re clear, this is not going to change. Kindly do not contact us in an attempt to get us to change this.
calibre is designed to have columns for the most frequently and widely used fields. In addition, you can add any
columns you like. Columns can be added via Preferences→Interface→Add your own columns. Watch the tutorial UI
Power tips59 to learn how to create your own columns, or read this blog post60 .
You can also create “virtual columns” that contain combinations of the metadata from other columns. In the add
column dialog use the Quick create links to easily create columns to show the book ISBN or formats. You can use
the powerful calibre template language to do much more with columns. For more details, see The calibre template
language (page 159).
Yes, you can. Follow the instructions in the answer above for adding custom columns.
You can export all calibre data (books, settings and plugins) and then import it on another computer. First let’s see
how to export the data:
• Right click the calibre icon in the main calibre toolbar and select Export/import all calibre data. Note that if
there is currently a device connected, this menu option will not be available – so, disconnect any connected
devices. Then click the button labelled Export all your calibre data. You will see a list of all your calibre
libraries. Click OK and choose an empty folder somewhere on your computer. The exported data will be saved
in this folder. Simply copy this folder to your new computer and follow the instructions below to import the
data.
• Install calibre on your new computer and run through the Welcome wizard, it does not matter what you do there,
as you will be importing your old settings in the next step. You will now have an empty calibre, with just the
Getting Started guide in your library. Once again, right click the calibre button and choose Export/import all
calibre data. Then click the button labelled Import previously exported data. Select the folder with the exported
data that you copied over earlier. You will now have a list of libraries you can import. Go through the list
one by one, and select the new location for each library (a location is just an empty folder somewhere on your
computer). Click OK. After the import completes, calibre will restart, with all your old libraries, settings and
calibre plugins.
Note: This import/export functionality is only available from calibre version 2.47 onwards. If you have an older
version of calibre, or if you encounter problems with the import/export, you can just copy over your calibre library
folder manually, as described in the next paragraph.
Simply copy the calibre library folder from the old to the new computer. You can find out what the library folder is by
clicking the calibre icon in the toolbar. Choose the Switch/create calibre library action and you will see the path to the
current calibre library.
Now on the new computer, start calibre for the first time. It will run the Welcome wizard asking you for the location of
the calibre library. Point it to the previously copied folder. If the computer you are transferring to already has a calibre
installation, then the Welcome wizard wont run. In that case, right-click the calibre icon in the toolbar and point it to
the newly copied directory. You will now have two calibre libraries on your computer and you can switch between
them by clicking the calibre icon on the toolbar. Transferring your library in this manner preserver all your metadata,
tags, custom columns, etc.
59 https://calibre-ebook.com/demo#tutorials
60 http://blog.calibre-ebook.com/2011/11/calibre-custom-columns.html
In order to understand why that happened, you have to understand what a calibre library is. At the most basic level,
a calibre library is just a folder. Whenever you add a book to calibre, that book’s files are copied into this folder
(arranged into sub folders by author and title). Inside the calibre library folder, at the top level, you will see a file
called metadata.db. This file is where calibre stores the metadata like title/author/rating/tags etc. for every book in
your calibre library. The list of books that calibre displays is created by reading the contents of this metadata.db file.
There can be two reasons why calibre is showing a empty list of books:
• Your calibre library folder changed its location. This can happen if it was on an external disk and the drive letter
for that disk changed. Or if you accidentally moved the folder. In this case, calibre cannot find its library and so
starts up with an empty library instead. To remedy this, do a right-click on the calibre icon in the calibre toolbar
and select Switch/create library. Click the little blue icon to select the new location of your calibre library and
click OK. If you don’t know the new location search your computer for the file metadata.db.
• Your metadata.db file was deleted/corrupted. In this case, you can ask calibre to rebuild the metadata.db from its
backups. Right click the calibre icon in the calibre toolbar and select Library maintenance->Restore database.
calibre will automatically rebuild metadata.db.
9.4 Miscellaneous
Contents
• I want calibre to download news from my favorite news website. (page 144)
• Why the name calibre? (page 144)
• Why does calibre show only some of my fonts on macOS? (page 144)
• calibre is not starting on Windows? (page 145)
61 https://www.mobileread.com/forums/showthread.php?t=205581
If you are reasonably proficient with computers, you can teach calibre to download news from any website of your
choosing. To learn how to do this see Adding your favorite news website (page 25).
Otherwise, you can request a particular news site by posting in the calibre Recipes forum62 .
calibre embeds fonts in e-book files it creates. E-book files support embedding only TrueType and OpenType (.ttf and
.otf) fonts. Most fonts on macOS systems are in .dfont format, thus they cannot be embedded. calibre shows only
TrueType and OpenType fonts found on your system. You can obtain many such fonts on the web. Simply download
the .ttf/.otf files and add them to the Library/Fonts directory in your home directory.
62 https://www.mobileread.com/forums/forumdisplay.php?f=228
There are several possible things I know of, that can cause this:
• You recently connected an external monitor or TV to your computer. In this case, whenever calibre opens a new
window like the edit metadata window or the conversion dialog, it appears on the second monitor where you
don’t notice it and so you think calibre has frozen. Disconnect your second monitor and restart calibre.
• The following programs have been reported to cause crashes in calibre: If you are running any of these, close
them before starting calibre, or uninstall them: RoboForm, Logitech SetPoint Settings, Constant Guard Protec-
tion by Xfinity, Spybot, Killer Network Manager, Nahimic UI Interface, Acronis True Image.
• You are using a Wacom branded USB mouse/tablet. There is an incompatibility between Wacom drivers and
the graphics toolkit calibre uses. Try using a non-Wacom mouse.
• On some 64 bit versions of Windows there are security software/settings that prevent 64-bit calibre from working
properly. If you are using the 64-bit version of calibre try switching to the 32-bit version.
63 https://download.calibre-ebook.com/1.48.0/
64 https://www.mobileread.com/forums/forumdisplay.php?f=166
• If the crash happens when you are trying to copy text from the calibre E-book viewer, it is most likely caused
by some clipboard monitoring/managing application you have running. Turn it off and you should be fine.
• If the crashes happen specifically when you are using a file dialog, like clicking on the Add books button or the
Save to Disk button, then you have some software that has installed broken Shell extensions on your computer.
Known culprits include: SpiderOak, odrive sync and Dell Backup and Recovery and NetDrive. If you have one
of these, uninstall them and you will be fine. You can also use the NirSoft Shell Extension Viewer65 to see what
shell extensions are installed on your system and disable them individually, if you dont want to uninstall the full
program. Remember to use “Restart Explorer” or reboot your computer after disabling the shell extensions.
If none of the above apply to you, then there is some other program on your computer that is interfering with calibre.
First reboot your computer in safe mode, to have as few running programs as possible, and see if the crashes still
happen. If they do not, then you know it is some program causing the problem. The most likely such culprit is a
program that modifies other programs’ behavior, such as an antivirus, a device driver, something like RoboForm (an
automatic form filling app) or an assistive technology like Voice Control or a Screen Reader.
The only way to find the culprit is to eliminate the programs one by one and see which one is causing the issue.
Basically, stop a program, run calibre, check for crashes. If they still happen, stop another program and repeat.
9.4.6 Using the viewer or doing any conversions results in a permission denied
error on Windows
Something on your computer is preventing calibre from accessing its own temporary files. Most likely the permissions
on your Temp folder are incorrect. Go to the folder file:C:\Users\USERNAME\AppData\Local in Windows Explorer
and then right click on the file:Temp folder, select Properties and go to the Security tab. Make sure that your user
account has full control for this folder.
Some users have reported that running the following command in an Administrator Command Prompt fixed their
permissions. To get an Administrator Command Prompt search for cmd.exe in the start menu, then right click on the
command prompt entry and select Run as Administrator. At the command prompt type the following command and
press Enter:
Alternately, you can run calibre as Administrator, but doing so will cause some functionality, such as drag and drop to
not work.
Finally, some users have reported that disabling UAC fixes the problem.
One common cause of failures on macOS is the use of accessibility technologies that are incompatible with the graphics
toolkit calibre uses. Try turning off VoiceOver if you have it on. Also go to System Preferences->System->Universal
Access and turn off the setting for enabling access for assistive devices in all the tabs. Another cause can be some
third party apps that modify system behavior, such as Smart Scroll.
You can obtain debug output about why calibre is not starting by running Console.app. Debug output will be printed
to it. If the debug output contains a line that looks like:
then the problem is probably a corrupted font cache. You can clear the cache by following these instructions66 . If that
doesn’t solve it, look for a corrupted font file on your system, in ~/Library/Fonts or the like. An easy way to check
65 https://www.nirsoft.net/utils/shexview.html
66 https://www.macworld.com/article/1139383/fontcacheclear.html
for corrupted fonts in macOS is to start the “Font Book” application, select all fonts and then in the File menu, choose
“Validate fonts”.
Downloading from the Internet can sometimes result in a corrupted download. If the calibre installer you downloaded
is not opening, try downloading it again. If re-downloading it does not work, download it from an alternate location67 .
If the installer still doesn’t work, then something on your computer is preventing it from running.
• Try temporarily disabling your antivirus program (Microsoft Security Essentials, or Kaspersky or Norton or
McAfee or whatever). This is most likely the culprit if the upgrade process is hanging in the middle.
• Try rebooting your computer and running a registry cleaner like Wise registry cleaner68 .
• Try a clean install. That is, uninstall calibre, delete C:\Program Files\Calibre2 (or wherever you
previously chose to install calibre). Then re-install calibre. Note that uninstalling does not touch your books or
settings.
• Try downloading the installer with an alternate browser. For example if you are using Internet Explorer, try
using Firefox or Chrome instead.
• If you get an error about a missing DLL on Windows, then most likely, the permissions on your temporary
folder are incorrect. Go to the folder C:\Users\USERNAME\AppData\Local in Windows explorer and
then right click on the Temp folder and select Properties and go to the Security tab. Make sure that your user
account has full control for this folder.
If you still cannot get the installer to work and you are on Windows, you can use the calibre portable install69 , which
does not need an installer (it is just a zip file).
The first thing to check is that you are downloading calibre from the official website: https://calibre-ebook.com/
download. Make sure you are clicking the download links on the left, not the advertisements on the right. calibre is a
very popular program and unscrupulous people try to setup websites offering it for download to fool the unwary.
If you have the official download and your antivirus program is still claiming calibre is a virus, then, your antivirus
program is wrong. Antivirus programs use heuristics, patterns of code that “look suspicious” to detect viruses. It’s
rather like racial profiling. calibre is a completely open source product. You can actually browse the source code
yourself (or hire someone to do it for you) to verify that it is not a virus. Please report the false identification to whatever
company you buy your antivirus software from. If the antivirus program is preventing you from downloading/installing
calibre, disable it temporarily, install calibre and then re-enable it.
The most important thing to backup is the calibre library folder, that contains all your books and metadata. This is the
folder you chose for your calibre library when you ran calibre for the first time. You can get the path to the library
folder by clicking the calibre icon on the main toolbar. You must backup this complete folder with all its files and
sub-folders.
You can switch calibre to using a backed up library folder by simply clicking the calibre icon on the toolbar and
choosing your backup library folder. A backed up library folder backs up your custom columns and saved searches as
well as all your books and metadata.
67 https://github.com/kovidgoyal/calibre/releases/latest
68 https://www.wisecleaner.com
69 https://calibre-ebook.com/download_portable
If you want to backup the calibre configuration/plugins, you have to backup the config directory. You can find this
config directory via Preferences→Miscellaneous. Note that restoring configuration directories is not officially sup-
ported, but should work in most cases. Just copy the contents of the backup directory into the current configuration
directory to restore.
9.4.11 How do I use purchased EPUB books with calibre (or what do I do with .acsm
files)?
Most purchased EPUB books have DRM (page ??). This prevents calibre from opening them. You can still use calibre
to store and transfer them to your e-book reader. First, you must authorize your reader on a Windows machine with
Adobe Digital Editions. Once this is done, EPUB books transferred with calibre will work fine on your reader. When
you purchase an epub book from a website, you will get an “.acsm” file. This file should be opened with Adobe Digital
Editions, which will then download the actual “.epub” e-book. The e-book file will be stored in the folder “My Digital
Editions”, from where you can add it to calibre.
A permission denied error can occur because of many possible reasons, none of them having anything to do with
calibre.
• You can get permission denied errors if you are using an SD card with write protect enabled.
• On macOS if you get permission errors when connecting a device to calibre, you can fix that by looking under
System Preferences > Security and Privacy > Privacy > Files and Folders.
• If you, or some program you used changed the file permissions of the files in question to read only.
• If there is a filesystem error on the device which caused your operating system to mount the filesystem in read
only mode or mark a particular file as read only pending recovery.
• If the files have their owner set to a user other than you.
• If your file is open in another program.
• If the file resides on a device, you may have reached the limit of a maximum of 256 files in the root of the device.
In this case you need to reformat the device/sd card referred to in the error message with a FAT32 filesystem, or
delete some files from the SD card/device memory.
You will need to fix the underlying cause of the permissions error before resuming to use calibre. Read the error
message carefully, see what file it points to and fix the permissions on that file or its containing folders.
Most readers do not support this. You should complain to the manufacturer about it and hopefully if enough people
complain, things will change. In the meantime, you can insert the metadata, including comments into a “Jacket page”
at the start of the e-book, by using the option to “Insert metadata as page at start of book” during conversion. The
option is found in the Structure detection section of the conversion settings. Note that for this to have effect you have
to convert the book. If your book is already in a format that does not need conversion, you can convert from that
format to the same format.
Another alternative is to create a catalog in e-book form containing a listing of all the books in your calibre library,
with their metadata. Click-and-hold the Convert button to access the catalog creation tool. And before you ask, no
you cannot have the catalog “link directly to” books on your reader.
By default, calibre uses whatever proxy settings are set in your OS. Sometimes these are incorrect, for example, on
Windows if you don’t use Internet Explorer then the proxy settings may not be up to date. You can tell calibre to use
a particular proxy server by setting the http_proxy and https_proxy environment variables. The format of the
variable is: http://username:password@servername you should ask your network administrator to give
you the correct value for this variable. Note that calibre only supports HTTP proxies not SOCKS proxies. You can see
the current proxies used by calibre in Preferences->Miscellaneous.
calibre is licensed under the GNU General Public License v3 (an open source license). This means that you are free
to redistribute calibre as long as you make the source code available. So if you want to put calibre on a CD with your
product, you must also put the calibre source code on the CD. The source code is available for download74 . You are
free to use the results of conversions from calibre however you want. You cannot use either code or libraries from
calibre in your software without making your software open source. For details, see The GNU GPL v375 .
70 https://calibre-ebook.com/get-involved
71 https://calibre-ebook.com/bugs
72 https://calibre-ebook.com/dynamic/downloads
73 https://www.mobileread.com/forums/forumdisplay.php?f=238
74 https://download.calibre-ebook.com
75 https://www.gnu.org/licenses/gpl.html
9.4.19 How do I run parts of calibre like news download and the Content server on
my own Linux server?
First, you must install calibre onto your Linux server. If your server is using a modern Linux distribution, you should
have no problems installing calibre onto it.
Note: calibre needs GLIBC >= 2.18 and libstdc++ >= 6.0.21. If you have an older server, you will either need to
compile these from source, or use calibre 3.48 which requires GLIBC >= 2.17 or 2.85.1 which requires GLIBC >=
2.13 or calibre 1.48 which requires only GLIBC >= 2.10. In addition, although the calibre command line utilities
do not need a running X server, some of them do require the X server libraries to be installed on your system. This
is because of Qt, which is used for various image processing tasks, and links against these libraries. If you get an
ImportError about some Qt modules, you are likely missing some X libraries.
/opt/calibre/calibre-server /path/to/the/library/you/want/to/share
You can download news and convert it into an e-book with the command:
If you want to generate MOBI, use outputfile.mobi instead and use --output-profile kindle.
You can email downloaded news with the command:
/opt/calibre/calibre-smtp
I leave figuring out the exact command line as an exercise for the reader.
Finally, you can add downloaded news to the calibre library with:
Remember to read the Command Line Interface (page 263) section of the calibre User Manual to learn more about
these, and other commands.
76 https://calibre-ebook.com/download_portable
Tutorials
Here you will find tutorials to get you started using calibre’s more advanced features, such as XPath and templates.
Some people wish to organize the books in their library into subgroups, similar to subfolders. The most commonly
provided reason is to create genre hierarchies, but there are many others. One user asked for a way to organize
textbooks by subject and course number. Another wanted to keep track of gifts by subject and recipient. This tutorial
will use the genre example for the rest of this post.
Before going on, please note that we are not talking about folders on the hard disk. Subgroups are not file folders.
Books will not be copied anywhere. calibre’s library file structure is not affected. Instead, we are presenting a way to
organize and display subgroups of books within a calibre library.
151
calibre User Manual, Release 4.21.0
Genre
. History
.. Japanese
.. Military
.. Roman
. Mysteries
.. English
.. Vampire
. Science Fiction
.. Alternate History
.. Military
.. Space Opera
. Thrillers
.. Crime
.. Horror
etc.
By using the hierarchy feature, you can see these genres in the Tag browser in tree form, as shown in the screen image.
In this example the outermost level (Genre) is a custom column that contains the genres. Genres containing sub-genres
appear with a small triangle next to them. Clicking on that triangle will open the item and show the sub-genres, as you
can see with History and Science Fiction.
Clicking on a genre can search for all books with that genre or children of that genre. For example, clicking on
Science Fiction can give all three of the child genres, Alternate History, Military, and Space Opera. Clicking on
Alternate History will give books in that genre, ignoring those in Military and Space Opera. Of course, a book can
have multiple genres. If a book has both Space Opera and Military genres, then you will see that book if you click on
either genre. Searching is discussed in more detail below.
Another thing you can see from the image is that the genre Military appears twice, once under History and once under
Science Fiction. Because the genres are in a hierarchy, these are two separate genres. A book can be in one, the other,
or (doubtfully in this case) both. For example, the books in Winston Churchill’s “The Second World War” could be in
“History.Military”. David Weber’s Honor Harrington books could be in “Science Fiction.Military”, and for that matter
also in “Science Fiction.Space Opera.”
Once a genre exists, that is at least one book has that genre, you can easily apply it to other books by dragging the
books from the library view onto the genre you want the books to have. You can also apply genres in the metadata
editors; more on this below.
10.1.1 Setup
By now, your question might be “How was all of this setup?” There are three steps: 1) create the custom column, 2)
tell calibre that the new column is to be treated as a hierarchy, and 3) add genres.
You create the custom column in the usual way, using Preferences -> Add your own columns. This example uses
“#genre” as the lookup name and “Genre” as the column heading. The column type is “Comma-separated text, like
tags, shown in the Tag browser.”
Then after restarting calibre, you must tell calibre that the column is to be treated as a hierarchy. Go to Preferences
→ Look & feel → Tag browser and enter the lookup name “#genre” into the “Categories with hierarchical items” box.
Press Apply, and you are done with setting up.
At the point there are no genres in the column. We are left with the last step: how to apply a genre to a book. A genre
does not exist in calibre until it appears on at least one book. To learn how to apply a genre for the first time, we must
go into some detail about what a genre looks like in the metadata for a book.
A hierarchy of ‘things’ is built by creating an item consisting of phrases separated by periods. Continuing the genre
example, these items would “History.Military”, “Mysteries.Vampire”, “Science Fiction.Space Opera”, etc. Thus to
create a new genre, you pick a book that should have that genre, edit its metadata, and enter the new genre into
the column you created. Continuing our example, if you want to assign a new genre “Comics” with a sub-genre
“Superheroes” to a book, you would ‘edit metadata’ for that (comic) book, choose the Custom metadata tab, and then
enter “Comics.Superheroes” as shown in the following (ignore the other custom columns):
From here on, to apply this new genre to a book (a comic book, presumably), you can either drag the book onto the
genre, or add it to the book using edit metadata in exactly the same way as done above.
Note: Hierarchical display only works if the Tag browser is set to sort items by name. This is the default and can be
checked by clicking the Configure button at the bottom of the Tag browser.
10.1.2 Searching
The easiest way to search for genres is using the Tag browser, clicking on the genre you wish to see. Clicking on a
genre with children will show you books with that genre and all child genres. However, this might bring up a question.
Just because a genre has children doesn’t mean that it isn’t a genre in its own right. For example, a book can have the
genre “History” but not “History.Military”. How do you search for books with only “History”?
The Tag browser search mechanism knows if an item has children. If it does, clicking on the item cycles through
5 searches instead of the normal three. The first is the normal green plus, which shows you books with that genre
only (e.g., History). The second is a doubled plus (shown above), which shows you books with that genre and all
sub-genres (e.g., History and History.Military). The third is the normal red minus, which shows you books without
that exact genre. The fourth is a doubled minus, which shows you books without that genre or sub-genres. The fifth is
back to the beginning, no mark, meaning no search.
10.1.3 Restrictions
If you search for a genre then create a saved search for it, you can use the ‘restrict to’ box to create a Virtual library of
books with that genre. This is useful if you want to do other searches within the genre or to manage/update metadata
for books in the genre. Continuing our example, you can create a Saved search named ‘History.Japanese’ by first
clicking on the genre Japanese in the Tag browser to get a search into the search field, entering History.Japanese into
the saved search field, then pushing the “Save search” button (the green box with the white plus, on the right-hand
side).
You might want to use the genre information in a template, such as with save to disk or send to device. The
question might then be “How do I get the outermost genre name or names?” A calibre template function,
subitems, is provided to make doing this easier.
For example, assume you want to add the outermost genre level to the save-to-disk template to make genre
folders, as in “History/The Gathering Storm - Churchill, Winston”. To do this, you must extract the first
level of the hierarchy and add it to the front along with a slash to indicate that it should make a folder.
The template below accomplishes this:
{#genre:subitems(0,1)||/}{title} - {authors}
See The template language (page 159) for more information about templates and the subitems() function.
In this tutorial, you will be given a gentle introduction to XPath77 , a query language that can be used to select arbitrary
parts of HTML78 documents in calibre. XPath is a widely used standard, and googling it will yield a ton of information.
This tutorial, however, focuses on using XPath for e-book related tasks like finding chapter headings in an unstructured
HTML document.
Contents
The simplest form of selection is to select tags by name. For example, suppose you want to select all the <h2> tags in
a document. The XPath query for this is simply:
The prefix // means search at any level of the document. Now suppose you want to search for <span> tags that are
inside <a> tags. That can be achieved with:
If you want to search for tags at a particular level in the document, change the prefix:
/h:body/h:div/h:p (Selects <p> tags that are children of <div> tags that are
children of the <body> tag)
This will match only <p>A very short e-book to demonstrate the use of XPath.</p> in the
Sample e-book (page 158) but not any of the other <p> tags. The h: prefix in the above examples is needed to match
XHTML tags. This is because internally, calibre represents all content as XHTML. In XHTML tags have a namespace,
and h: is the namespace prefix for HTML tags.
Now suppose you want to select both <h1> and <h2> tags. To do that, we need a XPath construct called predicate.
A predicate is simply a test that is used to select tags. Tests can be arbitrarily powerful and as this tutorial progresses,
you will see more powerful examples. A predicate is created by enclosing the test expression in square brackets:
//*[name()='h1' or name()='h2']
There are several new features in this XPath expression. The first is the use of the wildcard *. It means match any tag.
Now look at the test expression name()='h1' or name()='h2'. name() is an example of a built-in function. It
simply evaluates to the name of the tag. So by using it, we can select tags whose names are either h1 or h2. Note that
the name() function ignores namespaces so that there is no need for the h: prefix. XPath has several useful built-in
functions. A few more will be introduced in this tutorial.
77 https://en.wikipedia.org/wiki/XPath
78 https://en.wikipedia.org/wiki/HTML
Here, the @ operator refers to the attributes of the tag. You can use some of the XPath built-in functions (page 158) to
perform more sophisticated matching on attribute values.
Using XPath, you can even select tags based on the text they contain. The best way to do this is to use the power of
regular expressions via the built-in function re:test():
//h:h2[re:test(., 'chapter|section', 'i')] (Selects <h2> tags that contain the words
˓→chapter or
section)
Here the . operator refers to the contents of the tag, just as the @ operator referred to its attributes.
<html>
<head>
<title>A very short e-book</title>
<meta name="charset" value="utf-8" />
</head>
<body>
<h1 class="bookTitle">A very short e-book</h1>
<p style="text-align:right">Written by Kovid Goyal</p>
<div class="introduction">
<p>A very short e-book to demonstrate the use of XPath.</p>
</div>
The calibre template language is used in various places. It is used to control the folder structure and file name when
saving files from the calibre library to the disk or e-book reader. It is also used to define “virtual” columns that contain
data from other columns and so on.
The basic template language is very simple, but has very powerful advanced features. The basic idea is that a template
consists of text and names in curly brackets that are then replaced by the corresponding metadata from the book being
processed. So, for example, the default template used for saving books to device in calibre is:
{author_sort}/{title}/{title} - {authors}
The slashes are text, which is put into the template where it appears. For example, if your template is:
Asimov, Isaac Some Important Text The Foundation/The Foundation - Isaac Asimov
You can use all the various metadata fields available in calibre in a template, including any custom columns you have
created yourself. To find out the template name for a column simply hover your mouse over the column header. Names
for custom fields (columns you have created yourself) always have a # as the first character. For series type custom
fields, there is always an additional field named #seriesname_index that becomes the series index for that series.
So if you have a custom series field named #myseries, there will also be a field named #myseries_index.
In addition to the column based fields, you also can use:
If a particular book does not have a particular piece of metadata, the field in the template is automatically removed for
that book. Consider, for example:
{author_sort}/{series}/{title} {series_index}
You can do more than just simple substitution with the templates. You can also conditionally include text and control
how the substituted data is formatted.
First, conditionally including text. There are cases where you might want to have text appear in the output only if
a field is not empty. A common case is series and series_index, where you want either nothing or the two
values with a hyphen between them. calibre handles this case using a special field syntax.
For example, assume you want to use the template:
If the book has no series, the answer will be - - title. Many people would rather the result be simply title,
without the hyphens. To do this, use the extended syntax {field:|prefix_text|suffix_text}. When you
use this syntax, if field has the value SERIES then the result will be prefix_textSERIESsuffix_text. If field
has no value, then the result will be the empty string (nothing); the prefix and suffix are ignored. The prefix and suffix
can contain blanks. Do not use subtemplates (‘{ . . . }‘) or functions (see below) as the prefix or the suffix.
Using this syntax, we can solve the above series problem with the template:
{series}{series_index:| - | - }{title}
The hyphens will be included only if the book has a series index, which it will have only if it has a series.
Notes: you must include the : character if you want to use a prefix or a suffix. You must either use no | characters or
both of them; using one, as in {field:| - }, is not allowed. It is OK not to provide any text for one side or the
other, such as in {series:|| - }. Using {title:||} is the same as using {title}.
Second: formatting. Suppose you wanted to ensure that the series_index is always formatted as three digits with
leading zeros. This would do the trick:
If you use series indices with sub values (e.g., 1.1), you might want to ensure that the decimal points line up. For
example, you might want the indices 1 and 2.5 to appear as 01.00 and 02.50 so that they will sort correctly. To do this,
use:
If you want only the first two letters of the data, use:
{author_sort:.2} - Only the first two letter of the author sort name
The calibre template language comes from Python and for more details on the syntax of these advanced formatting
operations, look at the Python documentation80 .
80 https://docs.python.org/library/string.html#format-string-syntax
There are sometimes cases where you want to display metadata that calibre does not normally display, or to dis-
play data in a way different from how calibre normally does. For example, you might want to display the ISBN, a
field that calibre does not display. You can use custom columns for this by creating a column with the type ‘col-
umn built from other columns’ (hereafter called composite columns), and entering a template. Result: calibre will
display a column showing the result of evaluating that template. To display the ISBN, create the column and enter
{identifiers:select(isbn)} into the template box. To display a column containing the values of two series
custom columns separated by a comma, use {#series1:||,}{#series2}.
Composite columns can use any template option, including formatting.
You cannot change the data contained in a composite column. If you edit a composite column by double-clicking on
any item, you will open the template for editing, not the underlying data. Editing the template on the GUI is a quick
way of testing and changing composite columns.
Suppose you want to display the value of a field in upper case, when that field is normally in title case. You can do this
(and many more things) using the functions available for templates. For example, to display the title in upper case, use
{title:uppercase()}. To display it in title case, use {title:titlecase()}.
Function references appear in the format part, going after the : and before the first | or the closing }. If you have
both a format and a function reference, the function comes after another :. Functions must always end with (). Some
functions take extra values (arguments), and these go inside the ().
Functions are always applied before format specifications. See further down for an example of using both a format
and a function, where this order is demonstrated.
The syntax for using functions is {field:function(arguments)}, or
{field:function(arguments)|prefix|suffix}. Arguments are separated by commas. Commas
inside arguments must be preceded by a backslash ( \ ). The last (or only) argument cannot contain a closing
parenthesis ( ) ). Functions return the value of the field used in the template, suitably modified.
Important: If you have programming experience, please note that the syntax in this mode (single function) is not
what you might expect. Strings are not quoted. Spaces are significant. All arguments must be constants; there is no
sub-evaluation. Do not use subtemplates (‘{ . . . }‘) as function arguments. Instead, use template program mode
(page 164) and general program mode (page 188).
Many functions use regular expressions. In all cases, regular expression matching is case-insensitive.
The functions available are listed below. Note that the definitive documentation for functions is available in the section
Function classification (page 169):
• lowercase() – return value of the field in lower case.
• uppercase() – return the value of the field in upper case.
• titlecase() – return the value of the field in title case.
• capitalize() – return the value with the first letter upper case and the rest lower case.
• contains(pattern, text if match, text if not match) – checks if field contains matches
for the regular expression pattern. Returns text if match if matches are found, otherwise it returns text if no
match.
• count(separator) – interprets the value as a list of items separated by separator, returning the num-
ber of items in the list. Most lists use a comma as the separator, but authors uses an ampersand. Examples:
{tags:count(,)}, {authors:count(&)}
• format_number(template) – interprets the field as a number and format that number using a Python
formatting template such as “{0:5.2f}” or “{0:,d}” or “${0:5,.2f}”. The field_name part of the template must be
a 0 (zero) (the “{0:” in the above examples). You can leave off the leading “{0:” and trailing “}” if the template
contains only a format. See the template language and Python documentation for more examples. Returns the
empty string if formatting fails.
• human_readable() – expects the value to be a number and returns a string representing that number in KB,
MB, GB, etc.
• ifempty(text) – if the field is not empty, return the value of the field. Otherwise return text.
• in_list(separator, pattern, found_val, ..., not_found_val) – interpret the field as a
list of items separated by separator, evaluating the pattern against each value in the list. If the pattern matches a
value, return found_val, otherwise return not_found_val. The pattern and found_value can be repeated as many
times as desired, permitting returning different values depending on the search. The patterns are checked in
order. The first match is returned.
• language_codes(lang_strings) – return the language codes for the strings passed in lang_strings.
The strings must be in the language of the current locale. Lang_strings is a comma-separated list.
• language_strings(lang_codes, localize) – return the strings for the language codes passed in
lang_codes. If localize is zero, return the strings in English. If localize is not zero, return the strings in the
language of the current locale. Lang_codes is a comma-separated list.
• list_item(index, separator) – interpret the field as a list of items separated by separator, returning
the index‘th item. The first item is number zero. The last item can be returned using ‘list_item(-1,separator). If
the item is not in the list, then the empty value is returned. The separator has the same meaning as in the count
function.
• lookup(pattern, field, pattern, field, ..., else_field) – like switch, except the ar-
guments are field (metadata) names, not text. The value of the appropriate field will be fetched and used. Note
that because composite columns are fields, you can use this function in one composite field to use the value of
some other composite field. This is extremely useful when constructing variable save paths (more later).
• rating_to_stars(use_half_stars) – Returns the rating as string of star characters. The source value
must be a number between 0 and 5. Set use_half_stars to 1 if you want half star characters for custom ratings
columns that are not integers, for example 2.5.
• re(pattern, replacement) – return the field after applying the regular expression. All instances of
pattern are replaced with replacement. As in all of calibre, these are Python-compatible regular expressions.
• select(key) – interpret the field as a comma-separated list of items, with the items being of the form
“id:value”. Find the pair with the id equal to key, and return the corresponding value. This function is particularly
useful for extracting a value such as an ISBN from the set of identifiers for a book.
• shorten(left chars, middle text, right chars) – Return a shortened version of the field,
consisting of left chars characters from the beginning of the field, followed by middle text, followed by right
chars characters from the end of the string. Left chars and right chars must be integers. For example, assume
the title of the book is Ancient English Laws in the Times of Ivanhoe, and you want it to fit in a space of at
most 15 characters. If you use {title:shorten(9,-,5)}, the result will be Ancient E-nhoe. If the field’s
length is less than left chars + right chars + the length of middle text, then the field will be used
intact. For example, the title The Dome would not be changed.
• str_in_list(separator, string, found_val, ..., not_found_val) – interpret the field
as a list of items separated by separator, comparing the string against each value in the list. If the string matches
a value (ignoring case), return found_val, otherwise return not_found_val. If the string contains separators, then
it is also treated as a list and each value is checked. The string and found_value can be repeated as many times
as desired, permitting returning different values depending on the search. The strings are checked in order. The
first match is returned.
• subitems(start_index, end_index) – This function is used to break apart lists of tag-like hierar-
chical items such as genres. It interprets the field as a comma-separated list of tag-like items, where each item
is a period-separated list. Returns a new list made by first finding all the period-separated tag-like items, then
for each such item extracting the components from start_index to end_index, then combining the results back
together. The first component in a period-separated list has an index of zero. If an index is negative, then it
counts from the end of the list. As a special case, an end_index of zero is assumed to be the length of the list.
Examples:
Assuming a #genre column containing "A.B.C":
{#genre:subitems(0,1)} returns "A"
{#genre:subitems(0,2)} returns "A.B"
{#genre:subitems(1,0)} returns "B.C"
Assuming a #genre column containing "A.B.C, D.E":
{#genre:subitems(0,1)} returns "A, D"
{#genre:subitems(0,2)} returns "A.B, D.E"
• swap_around_articles(separator) – returns the val with articles moved to the end. The value can
be a list, in which case each member of the list is processed. If the value is a list then you must provide the list
value separator. If no separator is provided then the value is treated as being a single value, not a list.
• swap_around_comma() – given a field with a value of the form B, A, return A B. This is most useful for
converting names in LN, FN format to FN LN. If there is no comma, the function returns val unchanged.
• switch(pattern, value, pattern, value, ..., else_value) – for each pattern,
value pair, checks if the field matches the regular expression pattern and if so, returns that value. If
no pattern matches, then else_value is returned. You can have as many pattern, value pairs as
you want.
• test(text if not empty, text if empty) – return text if not empty if the field is not empty, oth-
erwise return text if empty.
• transliterate() – Returns a string in a latin alphabet formed by approximating the sound of the words in
the source field. For example, if the source field is Фёдор Михaйлович Достоевский the function returns
Fiodor Mikhailovich Dostoievskii.’
Now, what about using functions and formatting in the same field. Suppose you have an integer custom column called
#myint that you want to see with leading zeros, as in 003. To do this, you would use a format of 0>3s. However, by
default, if a number (integer or float) equals zero then the field produces the empty value, so zero values will produce
nothing, not 000. If you really want to see 000 values, then you use both the format string and the ifempty function
to change the empty value back to a zero. The field reference would be:
{#myint:0>3s:ifempty(0)}
Note that you can use the prefix and suffix as well. If you want the number to appear as [003] or [000], then use
the field:
{#myint:0>3s:ifempty(0)|[|]}
The template language program mode differs from single-function mode in that it permits you to write template expres-
sions that refer to other metadata fields, modify values, and do arithmetic. It is a reasonably complete programming
language.
You can use the functions documented above in template program mode. See below for details.
Beginning with an example, assume that you want your template to show the series for a book if it has one, otherwise
show the value of a custom field #genre. You cannot do this in the basic language because you cannot make reference
to another metadata field within a template expression. In program mode, you can. The following expression works:
{#series:'ifempty($, field('#genre'))'}
Comments are lines with a ‘#’ character at the beginning of the line.
An expression always has a value, either the value of the constant, the value contained in the identifier, or the value
returned by a function. The value of a statement is the value of the last expression in the sequence of statements.
As such, the value of the program (statement):
1; 2; 'foobar'; 3
is 3.
Another example of a complex but rather silly program might help make things clearer:
{series_index:'
substr(
strcat($, '->',
cmp(divide($, 2), 1,
assign(c, 1); substr('lt123', c, 0),
'eq', 'gt')),
0, 6)
'| prefix | suffix}
• and(value, value, ...) – returns the string “1” if all values are not empty, otherwise returns the empty
string. This function works well with test or first_non_empty. You can have as many values as you want.
• add(x, y) – returns x + y. Throws an exception if either x or y are not numbers.
• assign(id, val) – assigns val to id, then returns val. id must be an identifier, not an expression
• approximate_formats() – return a comma-separated list of formats that at one point were associated
with the book. There is no guarantee that the list is correct, although it probably is. This function can be called
in template program mode using the template {:'approximate_formats()'}. Note that format names
are always uppercase, as in EPUB.
• author_links(val_separator, pair_separator) – returns a string containing a list of
authors and that author’s link values in the form author1 val_separator author1link
pair_separator author2 val_separator author2link etc. An author is separated from its
link value by the val_separator string with no added spaces. author:linkvalue pairs are separated
by the pair_separator string argument with no added spaces. It is up to you to choose separator strings
that do not occur in author names or links. An author is included even if the author link is empty.
• author_sorts(val_separator) – returns a string containing a list of author’s sort values for the authors
of the book. The sort is the one in the author metadata (different from the author_sort in books). The returned
list has the form author sort 1 val_separator author sort 2 etc. The author sort values in this list are in the
same order as the authors of the book. If you want spaces around val_separator then include them in the
separator string
• booksize() – returns the value of the calibre ‘size’ field. Returns ‘’ if there are no formats.
• check_yes_no(field_name, is_undefined, is_false, is_true) – checks the value of the
yes/no field named by the lookup key field_name for a value specified by the parameters, returning “yes”
if a match is found, otherwise returning an empty string. Set the parameter is_undefined, is_false, or
is_true to 1 (the number) to check that condition, otherwise set it to 0. Example:
check_yes_no("#bool", 1, 0, 1)
returns “yes” if the yes/no field "#bool" is either undefined (neither True nor False) or True. More than one
of is_undefined, is_false, or is_true can be set to 1. This function is usually used by the test()
or is_empty() functions.
• cmp(x, y, lt, eq, gt) – compares x and y after converting both to numbers. Returns lt if x < y.
Returns eq if x == y. Otherwise returns gt.
• current_library_name() – return the last name on the path to the current calibre library. This function
can be called in template program mode using the template {:'current_library_name()'}.
• current_library_path() – return the path to the current calibre library. This function can be called in
template program mode using the template {:'current_library_path()'}.
• days_between(date1, date2) – return the number of days between date1 and date2. The number
is positive if date1 is greater than date2, otherwise negative. If either date1 or date2 are not dates, the
function returns the empty string.
• divide(x, y) – returns x / y. Throws an exception if either x or y are not numbers.
• eval(string) – evaluates the string as a program, passing the local variables (those assign ed to). This
permits using the template processor to construct complex results from local variables. Because the { and
} characters are special, you must use [[ for the { character and ]] for the ‘}’ character; they are converted
automatically. Note also that prefixes and suffixes (the |prefix|suffix syntax) cannot be used in the argument to
this function when using template program mode.
• field(name) – returns the metadata field named by name.
first_matching_cmp(10,5,"small",10,"middle",15,"large","giant")
returns “large”. The same example with a first value of 16 returns “giant”.
• first_non_empty(value, value, ...) – returns the first value that is not empty. If all values are
empty, then the empty value is returned. You can have as many values as you want.
• format_date(val, format_string) – format the value, which must be a date field, using the for-
mat_string, returning a string. The formatting codes are:
AP : use a 12-hour clock instead of a 24-hour clock, with 'AP' replaced by the
˓→localized string for AM or PM.
iso : the date with time and timezone. Must be the only format present.
You might get unexpected results if the date you are formatting contains localized month names, which
can happen if you changed the format tweaks to contain MMMM. In this case, instead of using some-
thing like {pubdate:format_date(yyyy)}, write the template using template program mode as in
{:'format_date(raw_field('pubdate'),'yyyy')'}.
• finish_formatting(val, fmt, prefix, suffix) – apply the format, prefix, and suffix to a value
in the same way as done in a template like {series_index:05.2f| - |- }. This function is provided
to ease conversion of complex single-function- or template-program-mode templates to general program mode
(page 188) (see below) to take advantage of GPM template compilation. For example, the following program
produces the same output as the above template:
program:
strcat(
re(field('series'), '([^\s])[^\s]+(\s|$)', '\1'),
finish_formatting(field('series_index'), '0>2s', ' - ', ' - '),
field('title')
)
Here, we document all the built-in functions available in the calibre template language. Every function is implemented
as a class in python and you can click the source links to see the source code, in case the documentation is insufficient.
The functions are arranged in logical groups by type.
Arithmetic
add(x, y)
class calibre.utils.formatter_functions.BuiltinAdd
add(x, y) – returns x + y. Throws an exception if either x or y are not numbers.
divide(x, y)
class calibre.utils.formatter_functions.BuiltinDivide
divide(x, y) – returns x / y. Throws an exception if either x or y are not numbers.
multiply(x, y)
class calibre.utils.formatter_functions.BuiltinMultiply
multiply(x, y) – returns x * y. Throws an exception if either x or y are not numbers.
subtract(x, y)
class calibre.utils.formatter_functions.BuiltinSubtract
subtract(x, y) – returns x - y. Throws an exception if either x or y are not numbers.
Boolean
and(value, value, . . . )
class calibre.utils.formatter_functions.BuiltinAnd
and(value, value, . . . ) – returns the string “1” if all values are not empty, otherwise returns the empty string.
This function works well with test or first_non_empty. You can have as many values as you want.
not(value)
class calibre.utils.formatter_functions.BuiltinNot
not(value) – returns the string “1” if the value is empty, otherwise returns the empty string. This function works
well with test or first_non_empty.
or(value, value, . . . )
class calibre.utils.formatter_functions.BuiltinOr
or(value, value, . . . ) – returns the string “1” if any value is not empty, otherwise returns the empty string. This
function works well with test or first_non_empty. You can have as many values as you want.
Date functions
days_between(date1, date2)
class calibre.utils.formatter_functions.BuiltinDaysBetween
days_between(date1, date2) – return the number of days between date1 and date2. The number is positive if
date1 is greater than date2, otherwise negative. If either date1 or date2 are not dates, the function returns the
empty string.
today()
class calibre.utils.formatter_functions.BuiltinToday
today() – return a date string for today. This value is designed for use in format_date or days_between, but can
be manipulated like any other string. The date is in ISO format.
Formatting values
class calibre.utils.formatter_functions.BuiltinFinishFormatting
finish_formatting(val, fmt, prefix, suffix) – apply the format, prefix, and suffix to a value in the same way as
done in a template like {series_index:05.2f| - |- }. For example, the following program produces the same output
as the above template: program: finish_formatting(field(“series_index”), “05.2f”, ” - “, ” - “)
format_date(val, format_string)
class calibre.utils.formatter_functions.BuiltinFormatDate
format_date(val, format_string) – format the value, which must be a date, using the format_string, returning a
string. The formatting codes are: d : the day as number without a leading zero (1 to 31) dd : the day as number
with a leading zero (01 to 31) ddd : the abbreviated localized day name (e.g. “Mon” to “Sun”). dddd : the long
localized day name (e.g. “Monday” to “Sunday”). M : the month as number without a leading zero (1 to 12).
MM : the month as number with a leading zero (01 to 12) MMM : the abbreviated localized month name (e.g.
“Jan” to “Dec”). MMMM : the long localized month name (e.g. “January” to “December”). yy : the year as
two digit number (00 to 99). yyyy : the year as four digit number. h : the hours without a leading 0 (0 to 11 or
0 to 23, depending on am/pm) hh : the hours with a leading 0 (00 to 11 or 00 to 23, depending on am/pm) m :
the minutes without a leading 0 (0 to 59) mm : the minutes with a leading 0 (00 to 59) s : the seconds without
a leading 0 (0 to 59) ss : the seconds with a leading 0 (00 to 59) ap : use a 12-hour clock instead of a 24-hour
clock, with “ap” replaced by the localized string for am or pm AP : use a 12-hour clock instead of a 24-hour
clock, with “AP” replaced by the localized string for AM or PM iso : the date with time and timezone. Must be
the only format present
format_number(v, template)
class calibre.utils.formatter_functions.BuiltinFormatNumber
format_number(v, template) – format the number v using a Python formatting template such as “{0:5.2f}”
or “{0:,d}” or “${0:5,.2f}”. The field_name part of the template must be a 0 (zero) (the “{0:” in the above
examples). See the template language and Python documentation for more examples. You can leave off the
leading “{0:” and trailing “}” if the template contains only a format. Returns the empty string if formatting
fails.
human_readable(v)
class calibre.utils.formatter_functions.BuiltinHumanReadable
human_readable(v) – return a string representing the number v in KB, MB, GB, etc.
rating_to_stars(value, use_half_stars)
class calibre.utils.formatter_functions.BuiltinRatingToStars
rating_to_stars(value, use_half_stars) – Returns the rating as string of star characters. The value is a number
between 0 and 5. Set use_half_stars to 1 if you want half star characters for custom ratings columns that support
non-integer ratings, for example 2.5.
approximate_formats()
class calibre.utils.formatter_functions.BuiltinApproximateFormats
approximate_formats() – return a comma-separated list of formats that at one point were associated with the
book. There is no guarantee that this list is correct, although it probably is. This function can be called in
template program mode using the template “{:’approximate_formats()’}”. Note that format names are always
uppercase, as in EPUB. This function works only in the GUI. If you want to use these values in save-to-disk or
send-to-device templates then you must make a custom “Column built from other columns”, use the function in
that column’s template, and use that column’s value in your save/send templates
author_links(val_separator, pair_separator)
class calibre.utils.formatter_functions.BuiltinAuthorLinks
author_links(val_separator, pair_separator) – returns a string containing a list of authors and that author’s link
values in the form author1 val_separator author1link pair_separator author2 val_separator author2link etc. An
author is separated from its link value by the val_separator string with no added spaces. author:linkvalue pairs
are separated by the pair_separator string argument with no added spaces. It is up to you to choose separator
strings that do not occur in author names or links. An author is included even if the author link is empty.
author_sorts(val_separator)
class calibre.utils.formatter_functions.BuiltinAuthorSorts
author_sorts(val_separator) – returns a string containing a list of author’s sort values for the authors of the book.
The sort is the one in the author metadata (different from the author_sort in books). The returned list has the
form author sort 1 val_separator author sort 2 etc. The author sort values in this list are in the same order as the
authors of the book. If you want spaces around val_separator then include them in the separator string
booksize()
class calibre.utils.formatter_functions.BuiltinBooksize
booksize() – return value of the size field. This function works only in the GUI. If you want to use this value in
save-to-disk or send-to-device templates then you must make a custom “Column built from other columns”, use
the function in that column’s template, and use that column’s value in your save/send templates
current_library_name()
class calibre.utils.formatter_functions.BuiltinCurrentLibraryName
current_library_name() – return the last name on the path to the current calibre library. This function can be
called in template program mode using the template “{:’current_library_name()’}”.
current_library_path()
class calibre.utils.formatter_functions.BuiltinCurrentLibraryPath
current_library_path() – return the path to the current calibre library. This function can be called in template
program mode using the template “{:’current_library_path()’}”.
field(name)
class calibre.utils.formatter_functions.BuiltinField
field(name) – returns the metadata field named by name
formats_modtimes(date_format)
class calibre.utils.formatter_functions.BuiltinFormatsModtimes
formats_modtimes(date_format) – return a comma-separated list of colon-separated items representing modifi-
cation times for the formats of a book. The date_format parameter specifies how the date is to be formatted. See
the format_date function for details. You can use the select function to get the mod time for a specific format.
Note that format names are always uppercase, as in EPUB.
formats_paths()
class calibre.utils.formatter_functions.BuiltinFormatsPaths
formats_paths() – return a comma-separated list of colon-separated items representing full path to the formats
of a book. You can use the select function to get the path for a specific format. Note that format names are
always uppercase, as in EPUB.
formats_sizes()
class calibre.utils.formatter_functions.BuiltinFormatsSizes
formats_sizes() – return a comma-separated list of colon-separated items representing sizes in bytes of the
formats of a book. You can use the select function to get the size for a specific format. Note that format names
are always uppercase, as in EPUB.
has_cover()
class calibre.utils.formatter_functions.BuiltinHasCover
has_cover() – return Yes if the book has a cover, otherwise return the empty string
language_codes(lang_strings)
class calibre.utils.formatter_functions.BuiltinLanguageCodes
language_codes(lang_strings) – return the language codes for the strings passed in lang_strings. The strings
must be in the language of the current locale. Lang_strings is a comma-separated list.
language_strings(lang_codes, localize)
class calibre.utils.formatter_functions.BuiltinLanguageStrings
language_strings(lang_codes, localize) – return the strings for the language codes passed in lang_codes. If
localize is zero, return the strings in English. If localize is not zero, return the strings in the language of the
current locale. Lang_codes is a comma-separated list.
ondevice()
class calibre.utils.formatter_functions.BuiltinOndevice
ondevice() – return Yes if ondevice is set, otherwise return the empty string. This function works only in the
GUI. If you want to use this value in save-to-disk or send-to-device templates then you must make a custom
“Column built from other columns”, use the function in that column’s template, and use that column’s value in
your save/send templates
raw_field(name)
class calibre.utils.formatter_functions.BuiltinRawField
raw_field(name) – returns the metadata field named by name without applying any formatting.
raw_list(name, separator)
class calibre.utils.formatter_functions.BuiltinRawList
raw_list(name, separator) – returns the metadata list named by name without applying any formatting or sorting
and with items separated by separator.
series_sort()
class calibre.utils.formatter_functions.BuiltinSeriesSort
series_sort() – return the series sort value
user_categories()
class calibre.utils.formatter_functions.BuiltinUserCategories
user_categories() – return a comma-separated list of the user categories that contain this book. This function
works only in the GUI. If you want to use these values in save-to-disk or send-to-device templates then you
must make a custom “Column built from other columns”, use the function in that column’s template, and use
that column’s value in your save/send templates
virtual_libraries()
class calibre.utils.formatter_functions.BuiltinVirtualLibraries
virtual_libraries() – return a comma-separated list of Virtual libraries that contain this book. This function works
only in the GUI. If you want to use these values in save-to-disk or send-to-device templates then you must make
a custom “Column built from other columns”, use the function in that column’s template, and use that column’s
value in your save/send templates
If-then-else
class calibre.utils.formatter_functions.BuiltinCheckYesNo
check_yes_no(field_name, is_undefined, is_false, is_true) – checks the value of the yes/no field named by the
lookup key field_name for a value specified by the parameters, returning “yes” if a match is found, otherwise
returning an empty string. Set the parameter is_undefined, is_false, or is_true to 1 (the number) to check that
condition, otherwise set it to 0. Example: check_yes_no(“#bool”, 1, 0, 1) returns “yes” if the yes/no field
“#bool” is either undefined (neither True nor False) or True. More than one of is_undefined, is_false, or is_true
can be set to 1. This function is usually used by the test() or is_empty() functions.
class calibre.utils.formatter_functions.BuiltinContains
contains(val, pattern, text if match, text if not match) – checks if val contains matches for the regular expression
pattern. Returns text if match if matches are found, otherwise it returns text if no match
class calibre.utils.formatter_functions.BuiltinIfempty
ifempty(val, text if empty) – return val if val is not empty, otherwise return text if empty
class calibre.utils.formatter_functions.BuiltinTest
test(val, text if not empty, text if empty) – return text if not empty if val is not empty, otherwise return text if
empty
first_non_empty(value, value, . . . )
class calibre.utils.formatter_functions.BuiltinFirstNonEmpty
first_non_empty(value, value, . . . ) – returns the first value that is not empty. If all values are empty, then the
empty value is returned. You can have as many values as you want.
class calibre.utils.formatter_functions.BuiltinLookup
lookup(val, pattern, field, pattern, field, . . . , else_field) – like switch, except the arguments are field (metadata)
names, not text. The value of the appropriate field will be fetched and used. Note that because composite
columns are fields, you can use this function in one composite field to use the value of some other composite
field. This is extremely useful when constructing variable save paths
class calibre.utils.formatter_functions.BuiltinSwitch
switch(val, pattern, value, pattern, value, . . . , else_value) – for each pattern, value pair, checks if val matches
the regular expression pattern and if so, returns that value. If no pattern matches, then else_value is returned.
You can have as many pattern, value pairs as you want
List lookup
class calibre.utils.formatter_functions.BuiltinIdentifierInList
identifier_in_list(val, id, found_val, not_found_val) – treat val as a list of identifiers separated by commas,
comparing the string against each value in the list. An identifier has the format “identifier:value”. The id
parameter should be either “id” or “id:regexp”. The first case matches if there is any identifier with that id. The
second case matches if the regexp matches the identifier’s value. If there is a match, return found_val, otherwise
return not_found_val.
class calibre.utils.formatter_functions.BuiltinInList
in_list(val, separator, pattern, found_val, . . . , not_found_val) – treat val as a list of items separated by separator,
evaluating the pattern against each value in the list. If the pattern matches a value, return found_val, otherwise
return not_found_val. The pattern and found_value can be repeated as many times as desired, permitting return-
ing different values depending on the search. The patterns are checked in order. The first match is returned.
class calibre.utils.formatter_functions.BuiltinListitem
list_item(val, index, separator) – interpret the value as a list of items separated by separator, returning the
index‘th item. The first item is number zero. The last item can be returned using ‘list_item(-1,separator). If
the item is not in the list, then the empty value is returned. The separator has the same meaning as in the count
function.
select(val, key)
class calibre.utils.formatter_functions.BuiltinSelect
select(val, key) – interpret the value as a comma-separated list of items, with the items being “id:value”. Find
the pair with the id equal to key, and return the corresponding value.
class calibre.utils.formatter_functions.BuiltinStrInList
str_in_list(val, separator, string, found_val, . . . , not_found_val) – treat val as a list of items separated by sep-
arator, comparing the string against each value in the list. If the string matches a value (ignoring case) then
return found_val, otherwise return not_found_val. If the string contains separators, then it is also treated as a
list and each value is checked. The string and found_value can be repeated as many times as desired, permitting
returning different values depending on the search. The strings are checked in order. The first match is returned.
List manipulation
count(val, separator)
class calibre.utils.formatter_functions.BuiltinCount
count(val, separator) – interprets the value as a list of items separated by separator, returning the number of items
in the list. Most lists use a comma as the separator, but authors uses an ampersand. Examples: {tags:count(,)},
{authors:count(&)}
class calibre.utils.formatter_functions.BuiltinListDifference
list_difference(list1, list2, separator) – return a list made by removing from list1 any item found in list2, using
a case-insensitive comparison. The items in list1 and list2 are separated by separator, as are the items in the
returned list.
class calibre.utils.formatter_functions.BuiltinListEquals
list_equals(list1, sep1, list2, sep2, yes_val, no_val) – return yes_val if list1 and list2 contain the same items,
otherwise return no_val. The items are determined by splitting each list using the appropriate separator character
(sep1 or sep2). The order of items in the lists is not relevant. The comparison is case insensitive.
class calibre.utils.formatter_functions.BuiltinListIntersection
list_intersection(list1, list2, separator) – return a list made by removing from list1 any item not found in list2,
using a case-insensitive comparison. The items in list1 and list2 are separated by separator, as are the items in
the returned list.
class calibre.utils.formatter_functions.BuiltinListRe
list_re(src_list, separator, include_re, opt_replace) – Construct a list by first separating src_list into items using
the separator character. For each item in the list, check if it matches include_re. If it does, then add it to the list
to be returned. If opt_replace is not the empty string, then apply the replacement before adding the item to the
returned list.
class calibre.utils.formatter_functions.BuiltinListReGroup
list_re_group(src_list, separator, include_re, search_re, group_1_template, . . . ) – Like list_re except replace-
ments are not optional. It uses re_group(list_item, search_re, group_1_template, . . . ) when doing the replace-
ments on the resulting list.
class calibre.utils.formatter_functions.BuiltinListSort
list_sort(list, direction, separator) – return list sorted using a case-insensitive sort. If direction is zero, the list
is sorted ascending, otherwise descending. The list items are separated by separator, as are the items in the
returned list.
class calibre.utils.formatter_functions.BuiltinListUnion
list_union(list1, list2, separator) – return a list made by merging the items in list1 and list2, removing duplicate
items using a case-insensitive comparison. If items differ in case, the one in list1 is used. The items in list1 and
list2 are separated by separator, as are the items in the returned list.
class calibre.utils.formatter_functions.BuiltinSubitems
subitems(val, start_index, end_index) – This function is used to break apart lists of items such as genres. It
interprets the value as a comma-separated list of items, where each item is a period-separated list. Returns a
new list made by first finding all the period-separated items, then for each such item extracting the start_index to
the end_index components, then combining the results back together. The first component in a period-separated
list has an index of zero. If an index is negative, then it counts from the end of the list. As a special case,
an end_index of zero is assumed to be the length of the list. Example using basic template mode and assum-
ing a #genre value of “A.B.C”: {#genre:subitems(0,1)} returns “A”. {#genre:subitems(0,2)} returns “A.B”.
{#genre:subitems(1,0)} returns “B.C”. Assuming a #genre value of “A.B.C, D.E.F”, {#genre:subitems(0,1)}
returns “A, D”. {#genre:subitems(0,2)} returns “A.B, D.E”
class calibre.utils.formatter_functions.BuiltinSublist
sublist(val, start_index, end_index, separator) – interpret the value as a list of items separated by separator,
returning a new list made from the start_index to the end_index item. The first item is number zero. If an
index is negative, then it counts from the end of the list. As a special case, an end_index of zero is assumed
to be the length of the list. Examples using basic template mode and assuming that the tags column (which
is comma-separated) contains “A, B, C”: {tags:sublist(0,1,\,)} returns “A”. {tags:sublist(-1,0,\,)} returns “C”.
{tags:sublist(0,-1,\,)} returns “A, B”.
Other
assign(id, val)
class calibre.utils.formatter_functions.BuiltinAssign
assign(id, val) – assigns val to id, then returns val. id must be an identifier, not an expression
print(a, b, . . . )
class calibre.utils.formatter_functions.BuiltinPrint
print(a, b, . . . ) – prints the arguments to standard output. Unless you start calibre from the command line
(calibre-debug -g), the output will go to a black hole.
Recursion
eval(template)
class calibre.utils.formatter_functions.BuiltinEval
eval(template) – evaluates the template, passing the local variables (those ‘assign’ed to) instead of the book
metadata. This permits using the template processor to construct complex results from local variables. Because
the { and } characters are special, you must use [[ for the { character and ]] for the } character; they are converted
automatically. Note also that prefixes and suffixes (the |prefix|suffix syntax) cannot be used in the argument to
this function when using template program mode.
template(x)
class calibre.utils.formatter_functions.BuiltinTemplate
template(x) – evaluates x as a template. The evaluation is done in its own context, meaning that variables
are not shared between the caller and the template evaluation. Because the { and } characters are special,
you must use [[ for the { character and ]] for the } character; they are converted automatically. For example,
template(‘[[title_sort]]’) will evaluate the template {title_sort} and return its value. Note also that prefixes and
suffixes (the |prefix|suffix syntax) cannot be used in the argument to this function when using template program
mode.
Relational
class calibre.utils.formatter_functions.BuiltinCmp
cmp(x, y, lt, eq, gt) – compares x and y after converting both to numbers. Returns lt if x < y. Returns eq if x ==
y. Otherwise returns gt.
class calibre.utils.formatter_functions.BuiltinFirstMatchingCmp
first_matching_cmp(val, cmp1, result1, cmp2, r2, . . . , else_result) – compares “val < cmpN” in sequence, re-
turning resultN for the first comparison that succeeds. Returns else_result if no comparison succeeds. Example:
first_matching_cmp(10,5,”small”,10,”middle”,15,”large”,”giant”) returns “large”. The same example with a first
value of 16 returns “giant”.
class calibre.utils.formatter_functions.BuiltinStrcmp
strcmp(x, y, lt, eq, gt) – does a case-insensitive comparison of x and y as strings. Returns lt if x < y. Returns eq
if x == y. Otherwise returns gt.
capitalize(val)
class calibre.utils.formatter_functions.BuiltinCapitalize
capitalize(val) – return val capitalized
lowercase(val)
class calibre.utils.formatter_functions.BuiltinLowercase
lowercase(val) – return val in lower case
titlecase(val)
class calibre.utils.formatter_functions.BuiltinTitlecase
titlecase(val) – return val in title case
uppercase(val)
class calibre.utils.formatter_functions.BuiltinUppercase
uppercase(val) – return val in upper case
String manipulation
class calibre.utils.formatter_functions.BuiltinRe
re(val, pattern, replacement) – return val after applying the regular expression. All instances of pattern are
replaced with replacement. As in all of calibre, these are Python-compatible regular expressions
class calibre.utils.formatter_functions.BuiltinReGroup
re_group(val, pattern, template_for_group_1, for_group_2, . . . ) – return a string made by applying the regular
expression pattern to the val and replacing each matched instance with the string computed by replacing each
matched group by the value returned by the corresponding template. The original matched value for the group is
available as $. In template program mode, like for the template and the eval functions, you use [[ for { and ]] for
}. The following example in template program mode looks for series with more than one word and uppercases
the first word: {series:’re_group($, “(S* )(.*)”, “[[$:uppercase()]]”, “[[$]]”)’}
class calibre.utils.formatter_functions.BuiltinShorten
shorten(val, left chars, middle text, right chars) – Return a shortened version of val, consisting of left chars
characters from the beginning of val, followed by middle text, followed by right chars characters from the end
of the string. Left chars and right chars must be integers. For example, assume the title of the book is Ancient
English Laws in the Times of Ivanhoe, and you want it to fit in a space of at most 15 characters. If you use
{title:shorten(9,-,5)}, the result will be Ancient E-nhoe. If the field’s length is less than left chars + right chars
+ the length of middle text, then the field will be used intact. For example, the title The Dome would not be
changed.
strcat(a, b, . . . )
class calibre.utils.formatter_functions.BuiltinStrcat
strcat(a, b, . . . ) – can take any number of arguments. Returns a string formed by concatenating all the arguments
class calibre.utils.formatter_functions.BuiltinStrcatMax
strcat_max(max, string1, prefix2, string2, . . . ) – Returns a string formed by concatenating the arguments. The
returned value is initialized to string1. Prefix, string pairs are added to the end of the value as long as the
resulting string length is less than max. String1 is returned even if string1 is longer than max. You can pass as
many prefix, string pairs as you wish.
strlen(a)
class calibre.utils.formatter_functions.BuiltinStrlen
strlen(a) – Returns the length of the string passed as the argument
class calibre.utils.formatter_functions.BuiltinSubstr
substr(str, start, end) – returns the start’th through the end’th characters of str. The first character in str is the
zero’th character. If end is negative, then it indicates that many characters counting from the right. If end is
zero, then it indicates the last character. For example, substr(‘12345’, 1, 0) returns ‘2345’, and substr(‘12345’,
1, -1) returns ‘234’.
swap_around_articles(val, separator)
class calibre.utils.formatter_functions.BuiltinSwapAroundArticles
swap_around_articles(val, separator) – returns the val with articles moved to the end. The value can be a list,
in which case each member of the list is processed. If the value is a list then you must provide the list value
separator. If no separator is provided then the value is treated as being a single value, not a list.
swap_around_comma(val)
class calibre.utils.formatter_functions.BuiltinSwapAroundComma
swap_around_comma(val) – given a value of the form “B, A”, return “A B”. This is most useful for converting
names in LN, FN format to FN LN. If there is no comma, the function returns val unchanged
transliterate(a)
class calibre.utils.formatter_functions.BuiltinTransliterate
transliterate(a) – Returns a string in a latin alphabet formed by approximating the sound of the words in the
source string. For example, if the source is “Фёдор Михaйлович Достоевский” the function returns “Fiodor
Mikhailovich Dostoievskii”.
The python implementation of the template functions is passed in a Metadata object. Knowing it’s API is useful if you
want to define your own template functions.
class calibre.ebooks.metadata.book.base.Metadata(title, authors=(u’Unknown’, ),
other=None, template_cache=None,
formatter=None)
A class representing all the metadata for a book. The various standard metadata fields are available as attributes
of this object. You can also stick arbitrary attributes onto this object.
Metadata from custom columns should be accessed via the get() method, passing in the lookup name for the
column, for example: “#mytags”.
Use the is_null() (page 184) method to test if a field is null.
This object also has functions to format fields into strings.
The list of standard metadata fields grows with time is in STANDARD_METADATA_FIELDS (page 186).
Please keep the method based API of this class to a minimum. Every method becomes a reserved field name.
is_null(field)
Return True if the value of field is null in this object. ‘null’ means it is unknown or evaluates to False. So
a title of _(‘Unknown’) is null or a language of ‘und’ is null.
Be careful with numeric fields since this will return True for zero as well as None.
Also returns True if the field does not exist.
deepcopy(class_generator=<function <lambda>>)
Do not use this method unless you know what you are doing, if you want to create a simple clone of
this object, use deepcopy_metadata() instead. Class_generator must be a function that returns an
instance of Metadata or a subclass of it.
get_identifiers()
Return a copy of the identifiers dictionary. The dict is small, and the penalty for using a reference where
a copy is needed is large. Also, we don’t want any manipulations of the returned dict to show up in the
book.
set_identifiers(identifiers)
Set all identifiers. Note that if you previously set ISBN, calling this method will delete it.
set_identifier(typ, val)
If val is empty, deletes identifier of type typ
standard_field_keys()
return a list of all possible keys, even if this book doesn’t have them
custom_field_keys()
return a list of the custom fields in this book
all_field_keys()
All field keys known by this instance, even if their value is None
metadata_for_field(key)
return metadata describing a standard or custom field.
all_non_none_fields()
Return a dictionary containing all non-None metadata fields, including the custom ones.
get_standard_metadata(field, make_copy)
return field metadata from the field if it is there. Otherwise return None. field is the key name, not the
label. Return a copy if requested, just in case the user wants to change values in the dict.
get_all_standard_metadata(make_copy)
return a dict containing all the standard field metadata associated with the book.
get_all_user_metadata(make_copy)
return a dict containing all the custom field metadata associated with the book.
get_user_metadata(field, make_copy)
return field metadata from the object if it is there. Otherwise return None. field is the key name, not the
label. Return a copy if requested, just in case the user wants to change values in the dict.
set_all_user_metadata(metadata)
store custom field metadata into the object. Field is the key name not the label
set_user_metadata(field, metadata)
store custom field metadata for one column into the object. Field is the key name not the label
template_to_attribute(other, ops)
Takes a list [(src,dest), (src,dest)], evaluates the template in the context of other, then copies the result to
self[dest]. This is on a best-efforts basis. Some assignments can make no sense.
smart_update(other, replace_metadata=False)
Merge the information in other into self. In case of conflicts, the information in other takes precedence,
unless the information in other is NULL.
format_field(key, series_with_index=True)
Returns the tuple (display_name, formatted_value)
to_html()
A HTML representation of this object.
calibre.ebooks.metadata.book.base.STANDARD_METADATA_FIELDS
The set of standard metadata fields.
'''
All fields must have a NULL value represented as None for simple types,
an empty list/dictionary for complex types and (None, None) for cover_data
'''
SOCIAL_METADATA_FIELDS = frozenset((
'tags', # Ordered list
'rating', # A floating point number between 0 and 10
'comments', # A simple HTML enabled string
'series', # A simple string
'series_index', # A floating point number
# Of the form { scheme1:value1, scheme2:value2}
# For example: {'isbn':'123456789', 'doi':'xxxx', ... }
'identifiers',
))
'''
The list of names that convert to identifiers when in get and set.
'''
TOP_LEVEL_IDENTIFIERS = frozenset((
'isbn',
))
PUBLICATION_METADATA_FIELDS = frozenset((
'title', # title must never be None. Should be _('Unknown')
# Pseudo field that can be set, but if not set is auto generated
# from title and languages
'title_sort',
'authors', # Ordered list. Must never be None, can be [_('Unknown')]
'author_sort_map', # Map of sort strings for each author
# Pseudo field that can be set, but if not set is auto generated
# from authors and languages
'author_sort',
'book_producer',
'timestamp', # Dates and times must be timezone aware
'pubdate',
'last_modified',
'rights',
# So far only known publication type is periodical:calibre
# If None, means book
'publication_type',
'uuid', # A UUID usually of type 4
'languages', # ordered list of languages in this publication
'publisher', # Simple string, no special semantics
# Absolute path to image file encoded in filesystem_encoding
'cover',
(continues on next page)
BOOK_STRUCTURE_FIELDS = frozenset((
# These are used by code, Null values are None.
'toc', 'spine', 'guide', 'manifest',
))
USER_METADATA_FIELDS = frozenset((
# A dict of dicts similar to field_metadata. Each field description dict
# also contains a value field with the key #value#.
'user_metadata',
))
DEVICE_METADATA_FIELDS = frozenset((
'device_collections', # Ordered list of strings
'lpath', # Unicode, / separated
'size', # In bytes
'mime', # Mimetype of the book file being represented
))
CALIBRE_METADATA_FIELDS = frozenset((
'application_id', # An application id, currently set to the db_id.
'db_id', # the calibre primary key of the item.
'formats', # list of formats (extensions) for this book
# a dict of user category names, where the value is a list of item names
# from the book that are in that category
'user_categories',
# a dict of author to an associated hyperlink
'author_link_map',
))
ALL_METADATA_FIELDS = SOCIAL_METADATA_FIELDS.union(
PUBLICATION_METADATA_FIELDS).union(
BOOK_STRUCTURE_FIELDS).union(
USER_METADATA_FIELDS).union(
DEVICE_METADATA_FIELDS).union(
CALIBRE_METADATA_FIELDS)
# Metadata fields that smart update should copy without special handling
SC_COPYABLE_FIELDS = SOCIAL_METADATA_FIELDS.union(
PUBLICATION_METADATA_FIELDS).union(
BOOK_STRUCTURE_FIELDS).union(
DEVICE_METADATA_FIELDS).union(
CALIBRE_METADATA_FIELDS) - \
SC_FIELDS_NOT_COPIED.union(
SC_FIELDS_COPY_NOT_NULL)
SERIALIZABLE_FIELDS = SOCIAL_METADATA_FIELDS.union(
USER_METADATA_FIELDS).union(
PUBLICATION_METADATA_FIELDS).union(
CALIBRE_METADATA_FIELDS).union(
DEVICE_METADATA_FIELDS) - \
frozenset(('device_collections', 'formats',
'cover_data'))
# these are rebuilt when needed
For more complicated template programs, it is sometimes easier to avoid template syntax (all the { and } characters),
instead writing a more classical-looking program. You can do this in calibre by beginning the template with program:.
In this case, no template processing is done. The special variable $ is not set. It is up to your program to produce the
correct results.
One advantage of program: mode is that the brackets are no longer special. For example, it is not necessary to use [[
and ]] when using the template() function. Another advantage is that program mode templates are compiled to Python
and can run much faster than templates in the other two modes. Speed improvement depends on the complexity of
the templates; the more complicated the template the more the improvement. Compilation is turned off or on using
the tweak compile_gpm_templates (Compile General Program Mode templates to Python). The main reason to
turn off compilation is if a compiled template does not work, in which case please file a bug report.
The following example is a program: mode implementation of a recipe on the MobileRead forum: “Put series into the
title, using either initials or a shortened form. Strip leading articles from the series name (any).” For example, for the
book The Two Towers in the Lord of the Rings series, the recipe gives LotR [02] The Two Towers. Using standard
templates, the recipe requires three custom columns and a plugboard, as explained in the following:
The solution requires creating three composite columns. The first column is used to remove the leading articles. The
second is used to compute the ‘shorten’ form. The third is to compute the ‘initials’ form. Once you have these
columns, the plugboard selects between them. You can hide any or all of the three columns on the library view:
First column:
Name: #stripped_series.
Template: {series:re(^(A|The|An)\s+,)||}
Plugboard expression:
Template:{#stripped_series:lookup(.\s,#initials,.,#shortened,series)}{series_index:0>
˓→2.0f| [|] }{title}
Series: Dahak
Series index: 1
Title: Mutineers Moon
Output: Dahak [01] Mutineers Moon
Series: Berserkers
Series Index: 4
Title: Berserker Throne
Output: Bers-kers [04] Berserker Throne
The following program produces the same results as the original recipe, using only one custom column to hold the
results of a program that computes the special title value:
Custom column:
Name: #special_title
Template: (the following with all leading spaces removed)
program:
# compute the equivalent of the composite fields and store them in local
˓→variables
# Now concatenate all the bits together. The switch picks between
# initials and shortened, depending on whether there is a space
# in stripped. We then add the brackets around s_index if it is
# not empty. Finally, add the title. As this is the last function in
# the program, its value will be returned.
strcat(
(continues on next page)
Plugboard expression:
Template:{#special_title}
Destination field: title
It would be possible to do the above with no custom columns by putting the program into the template box of the
plugboard. However, to do so, all comments must be removed because the plugboard text box does not support multi-
line editing. It is debatable whether the gain of not having the custom column is worth the vast increase in difficulty
caused by the program being one giant line.
You can add your own functions to the template processor. Such functions are written in Python, and can be used
in any of the three template programming modes. The functions are added by going to Preferences -> Advanced ->
Template functions. Instructions are shown in that dialog.
Special processing is applied when a template is used in a save to disk or send to device template. The values of the
fields are cleaned, replacing characters that are special to file systems with underscores, including slashes. This means
that field text cannot be used to create folders. However, slashes are not changed in prefix or suffix strings, so slashes
in these strings will cause folders to be created. Because of this, you can create variable-depth folder structure.
For example, assume we want the folder structure series/series_index - title, with the caveat that if series does not
exist, then the title should be in the top folder. The template to do this is:
{series:||/}{series_index:|| - }{title}
The slash and the hyphen appear only if series is not empty.
The lookup function lets us do even fancier processing. For example, assume that if a book has a series, then we want
the folder structure series/series index - title.fmt. If the book does not have a series, then we want the folder structure
genre/author_sort/title.fmt. If the book has no genre, we want to use ‘Unknown’. We want two completely different
paths, depending on the value of series.
To accomplish this, we:
1. Create a composite field (give it lookup name #AA) containing {series}/{series_index} -
{title}. If the series is not empty, then this template will produce series/series_index - title.
2. Create a composite field (give it lookup name #BB) containing {#genre:ifempty(Unknown)}/
{author_sort}/{title}. This template produces genre/author_sort/title, where an empty genre is
replaced with Unknown.
3. Set the save template to {series:lookup(.,#AA,#BB)}. This template chooses composite field
#AA if series is not empty, and composite field #BB if series is empty. We therefore have two completely
different save paths, depending on whether or not series is empty.
Plugboards are used for changing the metadata written into books during send-to-device and save-to-disk operations.
A plugboard permits you to specify a template to provide the data to write into the book’s metadata. You can use
plugboards to modify the following fields: authors, author_sort, language, publisher, tags, title, title_sort. This feature
helps people who want to use different metadata in books on devices to solve sorting or display issues.
When you create a plugboard, you specify the format and device for which the plugboard is to be used. A special
device is provided, save_to_disk, that is used when saving formats (as opposed to sending them to a device). Once
you have chosen the format and device, you choose the metadata fields to change, providing templates to supply the
new values. These templates are connected to their destination fields, hence the name plugboards. You can, of course,
use composite columns in these templates.
When a plugboard might apply (Content server, save to disk, or send to device), calibre searches the defined plugboards
to choose the correct one for the given format and device. For example, to find the appropriate plugboard for an EPUB
book being sent to an ANDROID device, calibre searches the plugboards using the following search order:
• a plugboard with an exact match on format and device, e.g., EPUB and ANDROID
• a plugboard with an exact match on format and the special any device choice, e.g., EPUB and any device
• a plugboard with the special any format choice and an exact match on device, e.g., any format and
ANDROID
• a plugboard with any format and any device
The tags and authors fields have special treatment, because both of these fields can hold more than one item. A book
can have many tags and many authors. When you specify that one of these two fields is to be changed, the template’s
result is examined to see if more than one item is there. For tags, the result is cut apart wherever calibre finds a comma.
For example, if the template produces the value Thriller, Horror, then the result will be two tags, Thriller
and Horror. There is no way to put a comma in the middle of a tag.
The same thing happens for authors, but using a different character for the cut, a & (ampersand) instead of a comma.
For example, if the template produces the value Blogs, Joe&Posts, Susan, then the book will end up with two
authors, Blogs, Joe and Posts, Susan. If the template produces the value Blogs, Joe;Posts, Susan,
then the book will have one author with a rather strange name.
Plugboards affect the metadata written into the book when it is saved to disk or written to the device. Plugboards
do not affect the metadata used by save to disk and send to device to create the file names. Instead, file
names are constructed using the templates entered on the appropriate preferences window.
Regular expressions are features used in many places in calibre to perform sophisticated manipulation of e-book
content and metadata. This tutorial is a gentle introduction to getting you started with using regular expressions in
calibre.
Contents
This is, inevitably, going to be somewhat technical- after all, regular expressions are a technical tool for doing technical
stuff. I’m going to have to use some jargon and concepts that may seem complicated or convoluted. I’m going to try
to explain those concepts as clearly as I can, but really can’t do without using them at all. That being said, don’t be
discouraged by any jargon, as I’ve tried to explain everything new. And while regular expressions themselves may
seem like an arcane, black magic (or, to be more prosaic, a random string of mumbo-jumbo letters and signs), I promise
that they are not all that complicated. Even those who understand regular expressions really well have trouble reading
the more complex ones, but writing them isn’t as difficult- you construct the expression step by step. So, take a step
and follow me into the rabbit hole.
There are a few places calibre uses regular expressions. There’s the Search & replace in conversion options, metadata
detection from filenames in the import settings and Search & replace when editing the metadata of books in bulk. The
calibre book editor can also use regular expressions in its search and replace feature.
A regular expression is a way to describe sets of strings. A single regular expression can match a number of different
strings. This is what makes regular expression so powerful – they are a concise way of describing a potentially large
number of variations.
Note: I’m using string here in the sense it is used in programming languages: a string of one or more characters,
characters including actual characters, numbers, punctuation and so-called whitespace (linebreaks, tabulators etc.).
Please note that generally, uppercase and lowercase characters are not considered the same, thus “a” being a different
character from “A” and so forth. In calibre, regular expressions are case insensitive in the Search bar, but not in the
conversion options. There’s a way to make every regular expression case insensitive, but we’ll discuss that later. It gets
complicated because regular expressions allow for variations in the strings it matches, so one expression can match
multiple strings, which is why people bother using them at all. More on that in a bit.
Well, that’s why we’re here. First, this is the most important concept in regular expressions: A string by itself is a
regular expression that matches itself. That is to say, if I wanted to match the string "Hello, World!" using
a regular expression, the regular expression to use would be Hello, World!. And yes, it really is that simple.
You’ll notice, though, that this only matches the exact string "Hello, World!", not e.g. "Hello, wOrld!" or
"hello, world!" or any other such variation.
Next is the beginning of the really good stuff. Remember where I said that regular expressions can match multiple
strings? This is where it gets a little more complicated. Say, as a somewhat more practical exercise, the e-book you
wanted to convert had a nasty footer counting the pages, like “Page 5 of 423”. Obviously the page number would rise
from 1 to 423, thus you’d have to match 423 different strings, right? Wrong, actually: regular expressions allow you
to define sets of characters that are matched: To define a set, you put all the characters you want to be in the set into
square brackets. So, for example, the set [abc] would match either the character “a”, “b” or “c”. Sets will always
only match one of the characters in the set. They “understand” character ranges, that is, if you wanted to match all the
lower case characters, you’d use the set [a-z] for lower- and uppercase characters you’d use [a-zA-Z] and so on.
Got the idea? So, obviously, using the expression Page [0-9] of 423 you’d be able to match the first 9 pages,
thus reducing the expressions needed to three: The second expression Page [0-9][0-9] of 423 would match
all two-digit page numbers, and I’m sure you can guess what the third expression would look like. Yes, go ahead.
Write it down.
I was hoping you’d say that. But brace yourself, now it gets even better! We just saw that using sets, we could match
one of several characters at once. But you can even repeat a character or set, reducing the number of expressions
needed to handle the above page number example to one. Yes, ONE! Excited? You should be! It works like this:
Some so-called special characters, “+”, “?” and “*”, repeat the single element preceding them. (Element means either
a single character, a character set, an escape sequence or a group (we’ll learn about those last two later)- in short, any
single entity in a regular expression.) These characters are called wildcards or quantifiers. To be more precise, “?”
matches 0 or 1 of the preceding element, “*” matches 0 or more of the preceding element and “+” matches 1 or more
of the preceding element. A few examples: The expression a? would match either “” (which is the empty string, not
strictly useful in this case) or “a”, the expression a* would match “”, “a”, “aa” or any number of a’s in a row, and,
finally, the expression a+ would match “a”, “aa” or any number of a’s in a row (Note: it wouldn’t match the empty
string!). Same deal for sets: The expression [0-9]+ would match every integer number there is! I know what you’re
thinking, and you’re right: If you use that in the above case of matching page numbers, wouldn’t that be the single one
expression to match all the page numbers? Yes, the expression Page [0-9]+ of 423 would match every page
number in that book!
Note: A note on these quantifiers: They generally try to match as much text as possible, so be careful when using
them. This is called “greedy behaviour”- I’m sure you get why. It gets problematic when you, say, try to match a tag.
Consider, for example, the string "<p class="calibre2">Title here</p>" and let’s say you’d want to
match the opening tag (the part between the first pair of angle brackets, a little more on tags later). You’d think that the
expression <p.*> would match that tag, but actually, it matches the whole string! (The character “.” is another special
character. It matches anything except linebreaks, so, basically, the expression .* would match any single line you can
think of.) Instead, try using <p.*?> which makes the quantifier "*" non-greedy. That expression would only match
the first opening tag, as intended. There’s actually another way to accomplish this: The expression <p[^>]*> will
match that same opening tag- you’ll see why after the next section. Just note that there quite frequently is more than
one way to write a regular expression.
10.4.7 Well, these special characters are very neat and all, but what if I wanted to
match a dot or a question mark?
You can of course do that: Just put a backslash in front of any special character and it is interpreted as the literal
character, without any special meaning. This pair of a backslash followed by a single character is called an escape
sequence, and the act of putting a backslash in front of a special character is called escaping that character. An escape
sequence is interpreted as a single element. There are of course escape sequences that do more than just escaping
special characters, for example "\t" means a tabulator. We’ll get to some of the escape sequences later. Oh, and by
the way, concerning those special characters: Consider any character we discuss in this introduction as having some
function to be special and thus needing to be escaped if you want the literal character.
Knew you’d ask. Some useful sets are [0-9] matching a single number, [a-z] matching a single lowercase letter,
[A-Z] matching a single uppercase letter, [a-zA-Z] matching a single letter and [a-zA-Z0-9] matching a single
letter or number. You can also use an escape sequence as shorthand:
\d is equivalent to [0-9]
\w is equivalent to [a-zA-Z0-9_]
\s is equivalent to any whitespace
Note: “Whitespace” is a term for anything that won’t be printed. These characters include space, tabulator, line feed,
form feed and carriage return.
As a last note on sets, you can also define a set as any character but those in the set. You do that by including the
character "^" as the very first character in the set. Thus, [^a] would match any character excluding “a”. That’s
called complementing the set. Those escape sequence shorthands we saw earlier can also be complemented: "\D"
means any non-number character, thus being equivalent to [^0-9]. The other shorthands can be complemented by,
you guessed it, using the respective uppercase letter instead of the lowercase one. So, going back to the example
<p[^>]*> from the previous section, now you can see that the character set it’s using tries to match any character
except for a closing angle bracket.
10.4.9 But if I had a few varying strings I wanted to match, things get complicated?
Fear not, life still is good and easy. Consider this example: The book you’re converting has “Title” written on every
odd page and “Author” written on every even page. Looks great in print, right? But in e-books, it’s annoying. You
can group whole expressions in normal parentheses, and the character "|" will let you match either the expression
to its right or the one to its left. Combine those and you’re done. Too fast for you? Okay, first off, we group the
expressions for odd and even pages, thus getting (Title)(Author) as our two needed expressions. Now we
make things simpler by using the vertical bar ("|" is called the vertical bar character): If you use the expression
(Title|Author) you’ll either get a match for “Title” (on the odd pages) or you’d match “Author” (on the even
pages). Well, wasn’t that easy?
You can, of course, use the vertical bar without using grouping parentheses, as well. Remember when I said that
quantifiers repeat the element preceding them? Well, the vertical bar works a little differently: The expression “Ti-
tle|Author” will also match either the string “Title” or the string “Author”, just as the above example using grouping.
The vertical bar selects between the entire expression preceding and following it. So, if you wanted to match the
strings “Calibre” and “calibre” and wanted to select only between the upper- and lowercase “c”, you’d have to use
the expression (c|C)alibre, where the grouping ensures that only the “c” will be selected. If you were to use
c|Calibre, you’d get a match on the string “c” or on the string “Calibre”, which isn’t what we wanted. In short: If
in doubt, use grouping together with the vertical bar.
. . . wait just a minute, there’s one last, really neat thing you can do with groups. If you have a group that you
previously matched, you can use references to that group later in the expression: Groups are numbered starting with
1, and you reference them by escaping the number of the group you want to reference, thus, the fifth group would be
referenced as \5. So, if you searched for ([^ ]+) \1 in the string “Test Test”, you’d match the whole string!
10.4.11 In the beginning, you said there was a way to make a regular expression
case insensitive?
Yes, I did, thanks for paying attention and reminding me. You can tell calibre how you want certain things handled
by using something called flags. You include flags in your expression by using the special construct (?flags go
here) where, obviously, you’d replace “flags go here” with the specific flags you want. For ignoring case, the flag
is i, thus you include (?i) in your expression. Thus, (?i)test would match “Test”, “tEst”, “TEst” and any case
variation you could think of.
Another useful flag lets the dot match any character at all, including the newline, the flag s. If you want to use multiple
flags in an expression, just put them in the same statement: (?is) would ignore case and make the dot match all. It
doesn’t matter which flag you state first, (?si) would be equivalent to the above.
10.4.12 I think I’m beginning to understand these regular expressions now. . . how
do I use them in calibre?
Conversions
Let’s begin with the conversion settings, which is really neat. In the Search & replace part, you can input a regexp
(short for regular expression) that describes the string that will be replaced during the conversion. The neat part is the
wizard. Click on the wizard staff and you get a preview of what calibre “sees” during the conversion process. Scroll
down to the string you want to remove, select and copy it, paste it into the regexp field on top of the window. If there
are variable parts, like page numbers or so, use sets and quantifiers to cover those, and while you’re at it, remember to
escape special characters, if there are some. Hit the button labeled Test and calibre highlights the parts it would replace
were you to use the regexp. Once you’re satisfied, hit OK and convert. Be careful if your conversion source has tags
like this example:
Maybe, but the cops feel like you do, Anita. What's one more dead vampire?
New laws don't change that. </p>
<p class="calibre4"> <b class="calibre2">Generated by ABC Amber LIT Conv
<a href="http://www.processtext.com/abclit.html" class="calibre3">erter,
http://www.processtext.com/abclit.html</a></b></p>
<p class="calibre4"> It had only been two years since Addison v. Clark.
The court case gave us a revised version of what life was
(shamelessly ripped out of this thread81 ). You’d have to remove some of the tags as well. In this example, I’d
recommend beginning with the tag <b class="calibre2">, now you have to end with the corresponding closing
tag (opening tags are <tag>, closing tags are </tag>), which is simply the next </b> in this case. (Refer to
a good HTML manual or ask in the forum if you are unclear on this point.) The opening tag can be described
using <b.*?>, the closing tag using </b>, thus we could remove everything between those tags using <b.*?
>.*?</b>. But using this expression would be a bad idea, because it removes everything enclosed by <b>- tags
(which, by the way, render the enclosed text in bold print), and it’s a fair bet that we’ll remove portions of the book
in this way. Instead, include the beginning of the enclosed string as well, making the regular expression <b.*?
>\s*Generated\s+by\s+ABC\s+Amber\s+LIT.*?</b> The \s with quantifiers are included here instead
of explicitly using the spaces as seen in the string to catch any variations of the string that might occur. Remember
to check what calibre will remove to make sure you don’t remove any portions you want to keep if you test a new
expression. If you only check one occurrence, you might miss a mismatch somewhere else in the text. Also note that
should you accidentally remove more or fewer tags than you actually wanted to, calibre tries to repair the damaged
code after doing the removal.
Adding books
Another thing you can use regular expressions for is to extract metadata from filenames. You can find this feature
in the “Adding books” part of the settings. There’s a special feature here: You can use field names for metadata
fields, for example (?P<title>) would indicate that calibre uses this part of the string as book title. The allowed
field names are listed in the windows, together with another nice test field. An example: Say you want to import
a whole bunch of files named like Classical Texts: The Divine Comedy by Dante Alighieri.
mobi. (Obviously, this is already in your library, since we all love classical italian poetry) or Science Fiction
epics: The Foundation Trilogy by Isaac Asimov.epub. This is obviously a naming scheme that
calibre won’t extract any meaningful data out of - its standard expression for extracting metadata is (?P<title>.+)
- (?P<author>[^_]+). A regular expression that works here would be [a-zA-Z]+: (?P<title>.+)
by (?P<author>.+). Please note that, inside the group for the metadata field, you need to use expressions to
describe what the field actually matches. And also note that, when using the test field calibre provides, you need to
add the file extension to your testing filename, otherwise you won’t get any matches at all, despite using a working
expression.
The last part is regular expression search and replace in metadata fields. You can access this by selecting multiple
books in the library and using bulk metadata edit. Be very careful when using this last feature, as it can do Very
Bad Things to your library! Doublecheck that your expressions do what you want them to using the test fields, and
only mark the books you really want to change! In the regular expression search mode, you can search in one field,
replace the text with something and even write the result into another field. A practical example: Say your library
contained the books of Frank Herbert’s Dune series, named after the fashion Dune 1 - Dune, Dune 2 - Dune
Messiah and so on. Now you want to get Dune into the series field. You can do that by searching for (.*?) \d+
- .* in the title field and replacing it with \1 in the series field. See what I did there? That’s a reference to the first
81 https://www.mobileread.com/forums/showthread.php?t=75594"
group you’re replacing the series field with. Now that you have the series all set, you only need to do another search
for .*? - in the title field and replace it with "" (an empty string), again in the title field, and your metadata is all
neat and tidy. Isn’t that great? By the way, instead of replacing the entire field, you can also append or prepend to the
field, so, if you wanted the book title to be prepended with series info, you could do that as well. As you by now have
undoubtedly noticed, there’s a checkbox labeled Case sensitive, so you won’t have to use flags to select behaviour
here.
Well, that just about concludes the very short introduction to regular expressions. Hopefully I’ll have shown you
enough to at least get you started and to enable you to continue learning by yourself- a good starting point would be
the Python documentation for regexps82 .
One last word of warning, though: Regexps are powerful, but also really easy to get wrong. calibre provides really
great testing possibilities to see if your expressions behave as you expect them to. Use them. Try not to shoot yourself
in the foot. (God, I love that expression. . . ) But should you, despite the warning, injure your foot (or any other body
parts), try to learn from it.
This checklist summarizes the most commonly used/hard to remember parts of the regexp engine available in the
calibre edit and conversion search/replace features. Note that this engine is more powerful than the basic regexp
engine used throughout the rest of calibre.
Contents
Character classes
Examples:
Representa- Class
tion
[a-z] Lowercase letters. Does not include characters with accent mark and ligatures
[a-z0-9] Lowercase letters from a to z or numbers from 0 to 9
[A-Za-z-] Uppercase or lowercase letters, or a dash. To include the dash in a class, you must put it at the
beginning or at the end so as not to confuse it with the hyphen that specifies a range of characters
[^0-9] Any character except a digit. The caret (^) placed at the beginning of the class excludes the char-
acters of the class (complemented class)
The lowercase consonants. A class can be included in a class. The characters -- exclude what
[[a-z]--[aeiouy]]
follows them
[\w--[\d_]]All letters (including foreign accented characters). Abbreviated classes can be used inside a class
Example:
Representa- Class
tion
\d A digit (same as [0-9])
\D Any non-numeric character (same as [^0-9])
\w An alphanumeric character ([a-zA-Z0-9]) including characters with accent mark and ligatures
\W Any “non-word” character
\s Space, non-breaking space, tab, return line
\S Any “non-whitespace” character
. Any character except newline. Use the “dot all” checkbox or the (?s) regexp modifier to include
the newline character.
The quantifiers
Greed
By default, with quantifiers, the regular expression engine is greedy: it extends the selection as much as possible. This
often causes surprises, at first. ? follows a quantifier to make it lazy. Avoid putting two in the same expression, the
result can be unpredictable.
Beware of nesting quantifiers, for example, the pattern (a*)*, as it exponentially increases processing time.
Alternation
The | character in a regular expression is a logical OR. It means that either the preceding or the following expression
can match.
Exclusion
Method 1
pattern_to_exclude(*SKIP)(*FAIL)|pattern_to_select
Example:
"Blabla"(*SKIP)(*FAIL)|Blabla
selects Blabla, in the strings Blabla or “Blabla or Blabla”, but not in “Blabla”.
Method 2
pattern_to_exclude\K|(pattern_to_select)
"Blabla"\K|(Blabla)
selects Blabla, in the strings Blabla or “Blabla or Blabla”, but not in “Blabla”.
Anchors
An anchor is a way to match a logical location in a string, rather than a character. The most useful anchors for text
processing are:
\b Designates a word boundary, i.e. a transition from space to non-space character. For example, you
can use \bsurd to match the surd but not absurd.
^ Matches the start of a line (in multi-line mode, which is the default)
$ Matches the end of a line (in multi-line mode, which is the default)
\K Resets the start position of the selection to its position in the pattern. Some regexp engines (but not
calibre) do not allow lookbehind of variable length, especially with quantifiers. When you can use
\K with these engines, it also allows you to get rid of this limit by writing the equivalent of a positive
lookbehind of variable length.
Groups
(expression) Capturing group, which stores the selection and can be recalled later in the search or
replace patterns with \n, where n is the sequence number of the capturing group (starting at 1 in
reading order)
(?:expression) Group that does not capture the selection
(?>expression) Atomic Group: As soon as the expression is satisfied, the regexp engine passes,
and if the rest of the pattern fails, it will not backtrack to try other combinations with the expression.
Atomic groups do not capture.
(?|expression) Branch reset group: the branches of the alternations included in the expression
share the same group numbers
(?<name>expression) Group named “name”. The selection can be recalled later in the search
pattern by (?P=name) and in the replace by \g<name>. Two different groups can use the same
name.
Lookarounds
Lookaround Meaning
?= Positive lookahead (to be placed after the selection)
?! Negative lookahead (to be placed after the selection)
?<= Positive lookbehind (to be placed before the selection)
?<! Negative lookbehind (to be placed before the selection)
Lookaheads and lookbehinds do not consume characters, they are zero length and do not capture. They are atomic
groups: as soon as the assertion is satisfied, the regexp engine passes, and if the rest of the pattern fails, it will not
backtrack inside the lookaround to try other combinations.
When looking for multiple matches in a string, at the starting position of each match attempt, a lookbehind can inspect
the characters before the current position. Therefore, on the string 123, the pattern (?<=\d)\d (a digit preceded by
a digit) should, in theory, select 2 and 3. On the other hand, \d\K\d can only select 2, because the starting position
after the first selection is immediately before 3, and there are not enough digits for a second match. Similarly, \d(\d)
only captures 2. In calibre’s regexp engine practice, the positive lookbehind behaves in the same way, and selects only
2, contrary to theory.
Groups can be placed inside lookarounds, but capture is rarely useful. Nevertheless, if it is useful, it will be necessary
to be very careful in the use of a quantifier in a lookbehind: the greed associated with the absence of backtracking can
give a surprising capture. For this reason, use \K rather than a positive lookbehind when you have a quantifier (or
worse, several) in a capturing group of the positive lookbehind.
Example of negative lookahead:
(?![^<>{}]*[>}])
Placed at the end of the pattern prevents to select within a tag or a style embedded in the file.
Whenever possible, it is always better to “anchor” the lookarounds, to reduce the number of steps necessary to obtain
the result.
Recursion
Representation Meaning
(?R) Recursion of the entire pattern
(?1) Recursion of the only pattern of the numbered capturing group, here group 1
Recursion is calling oneself. This is useful for balanced queries, such as quoted strings, which can contain embedded
quoted strings. Thus, if during the processing of a string between double quotation marks, we encounter the beginning
of a new string between double quotation marks, well we know how to do, and we call ourselves. Then we have a
pattern like:
start-pattern(?>atomic sub-pattern|(?R))*end-pattern
To select a string between double quotation marks without stopping on an embedded string:
“((?>[^“”]+|(?R))*[^“”]+)”
This template can also be used to modify pairs of tags that can be embedded, such as <div> tags.
Special characters
Representation Character
\t tabulation
\n line break
\x20 (breakable) space
\xa0 no-break space
Meta-characters
Meta-characters are those that have a special meaning for the regexp engine. Of these, twelve must be preceded by an
escape character, the backslash (\), to lose their special meaning and become a regular character again:
^ . [ ] $ ( ) * + ? | \
Seven other meta-characters do not need to be preceded by a backslash (but can be without any other consequence):
{ } ! < > = :
Special characters lose their status if they are used inside a class (between brackets []). The closing bracket and
the dash have a special status in a class. Outside the class, the dash is a simple literal, the closing bracket remains a
meta-character.
The slash (/) and the number sign (or hash character) (#) are not meta-characters, they don’t need to be escaped.
In some tools, like regex101.com with the Python engine, double quotes have the special status of separator, and must
be escaped, or the options changed. This is not the case in the editor of calibre.
Modes
10.4.14 Credits
• Orpheu
For more about regexps see The Python User Manual83 . The actual regular expression library used by calibre is:
regex84 which supports several useful enhancements over the python standard library one.
calibre has a very modular design. Almost all functionality in calibre comes in the form of plugins. Plugins are used
for conversion, for downloading news (though these are called recipes), for various components of the user interface,
to connect to different devices, to process files when adding them to calibre and so on. You can get a complete list of
all the built-in plugins in calibre by going to Preferences→Advanced→Plugins.
Here, we will teach you how to create your own plugins to add new features to calibre.
Contents
A calibre plugin is very simple, it’s just a ZIP file that contains some Python code and any other resources like image
files needed by the plugin. Without further ado, let’s see a basic example.
Suppose you have an installation of calibre that you are using to self publish various e-documents in EPUB and MOBI
formats. You would like all files generated by calibre to have their publisher set as “Hello world”, here’s how to do it.
83 https://docs.python.org/library/re.html
84 https://bitbucket.org/mrabarnett/mrab-regex/src/hg/
Create a file named __init__.py (this is a special name and must always be used for the main file of your plugin)
and enter the following Python code into it:
class HelloWorld(FileTypePlugin):
That’s all. To add this code to calibre as a plugin, simply run the following in the directory in which you created
__init__.py:
calibre-customize -b .
Note: On macOS, the command line tools are inside the calibre bundle, for example, if you installed calibre in
/Applications the command line tools are in /Applications/calibre.app/Contents/MacOS/.
This plugin will be spread over a few files (to keep the code clean). It will show you how to get resources (images
or data files) from the plugin ZIP file, allow users to configure your plugin, how to create elements in the calibre user
interface and how to access and query the books database in calibre.
You can download this plugin from interface_demo_plugin.zip86
The first thing to note is that this ZIP file has a lot more files in it, explained below, pay particular attention to
plugin-import-name-interface_demo.txt.
85 https://calibre-ebook.com/downloads/helloworld_plugin.zip
86 https://calibre-ebook.com/downloads/interface_demo_plugin.zip
plugin-import-name-interface_demo.txt An empty text file used to enable the multi-file plugin magic.
This file must be present in all plugins that use more than one .py file. It should be empty and its
filename must be of the form: plugin-import-name-**some_name**.txt. The presence
of this file allows you to import code from the .py files present inside the ZIP file, using a statement
like:
from calibre_plugins.some_name.some_module import some_object
The prefix calibre_plugins must always be present. some_name comes from the filename
of the empty text file. some_module refers to some_module.py file inside the ZIP file. Note
that this importing is just as powerful as regular Python imports. You can create packages and
subpackages of .py modules inside the ZIP file, just like you would normally (by defining __init__.py
in each sub-directory), and everything should “just work”.
The name you use for some_name enters a global namespace shared by all plugins, so make it as
unique as possible. But remember that it must be a valid Python identifier (only alphabets, numbers
and the underscore).
__init__.py As before, the file that defines the plugin class
main.py This file contains the actual code that does something useful
ui.py This file defines the interface part of the plugin
images/icon.png The icon for this plugin
about.txt A text file with information about the plugin
translations A folder containing .mo files with the translations of the user interface of your plugin into
different languages. See below for details.
Now let’s look at the code.
__init__.py
class InterfacePluginDemo(InterfaceActionBase):
'''
This class is a simple wrapper that provides information about the actual
plugin class. The actual interface plugin class is called InterfacePlugin
and is defined in the ui.py file, as specified in the actual_plugin field
below.
The reason for having two classes is that it allows the command line
calibre utilities to run without needing to load the GUI libraries.
'''
name = 'Interface Plugin Demo'
description = 'An advanced plugin demo'
supported_platforms = ['windows', 'osx', 'linux']
author = 'Kovid Goyal'
version = (1, 0, 0)
minimum_calibre_version = (0, 7, 53)
#: This field defines the GUI plugin class that contains all the code
#: that actually does something. Its format is module_path:class_name
#: The specified class must be defined in the specified module.
(continues on next page)
def is_customizable(self):
'''
This method must return True to enable customization via
Preferences->Plugins
'''
return True
def config_widget(self):
'''
Implement this method and :meth:`save_settings` in your plugin to
use a custom configuration dialog.
This method, if implemented, must return a QWidget. The widget can have
an optional method validate() that takes no arguments and is called
immediately after the user clicks OK. Changes are applied if and only
if the method returns True.
If for some reason you cannot perform the configuration at this time,
return a tuple of two strings (message, details), these will be
displayed as a warning dialog to the user and the process will be
aborted.
The only noteworthy feature is the field actual_plugin. Since calibre has both command line and GUI interfaces,
GUI plugins like this one should not load any GUI libraries in __init__.py. The actual_plugin field does this for you,
by telling calibre that the actual plugin is to be found in another file inside your ZIP archive, which will only be loaded
in a GUI context.
Remember that for this to work, you must have a plugin-import-name-some_name.txt file in your plugin ZIP file, as
discussed above.
Also there are a couple of methods for enabling user configuration of the plugin. These are discussed below.
ui.py
Now let’s look at ui.py which defines the actual GUI plugin. The source code is heavily commented and should be self
explanatory:
from calibre.gui2.actions import InterfaceAction
from calibre_plugins.interface_demo.main import DemoDialog
class InterfacePlugin(InterfaceAction):
def genesis(self):
# This method is called once per plugin, do initial setup here
def show_dialog(self):
# The base plugin object defined in __init__.py
base_plugin_object = self.interface_action_base_plugin
# Show the config dialog
# The config dialog can also be shown from within
# Preferences->Plugins, which is why the do_user_config
# method is defined on the base plugin class
do_user_config = base_plugin_object.do_user_config
def apply_settings(self):
from calibre_plugins.interface_demo.config import prefs
# In an actual non trivial plugin, you would probably need to
# do something based on the settings in prefs
(continues on next page)
main.py
class DemoDialog(QDialog):
self.l = QVBoxLayout()
self.setLayout(self.l)
self.label = QLabel(prefs['hello_world_msg'])
self.l.addWidget(self.label)
self.marked_button = QPushButton(
'Show books with only one format in the calibre GUI', self)
self.marked_button.clicked.connect(self.marked)
self.l.addWidget(self.marked_button)
self.view_button = QPushButton(
'View the most recently added book', self)
self.view_button.clicked.connect(self.view)
self.l.addWidget(self.view_button)
self.update_metadata_button = QPushButton(
'Update metadata in a book\'s files', self)
self.update_metadata_button.clicked.connect(self.update_metadata)
self.l.addWidget(self.update_metadata_button)
self.conf_button = QPushButton(
'Configure this plugin', self)
(continues on next page)
self.resize(self.sizeHint())
def about(self):
# Get the about text from a file inside the plugin zip file
# The get_resources function is a builtin function defined for all your
# plugin code. It loads files from the plugin zip file. It returns
# the bytes from the specified file.
#
# Note that if you are loading more than one file, for performance, you
# should pass a list of names to get_resources. In this case,
# get_resources will return a dictionary mapping names to bytes. Names that
# are not found in the zip file will not be in the returned dictionary.
text = get_resources('about.txt')
QMessageBox.about(self, 'About the Interface Plugin Demo',
text.decode('utf-8'))
def marked(self):
''' Show books with only one format '''
db = self.db.new_api
matched_ids = {book_id for book_id in db.all_book_ids() if len(db.
˓→formats(book_id)) == 1}
def view(self):
''' View the most recently added book '''
most_recent = most_recent_id = None
db = self.db.new_api
for book_id, timestamp in db.all_field_for('timestamp', db.all_book_ids()).
˓→items():
def update_metadata(self):
'''
Set the metadata in the files in the selected book's record to
match the current metadata in the database.
'''
from calibre.ebooks.metadata.meta import set_metadata
from calibre.gui2 import error_dialog, info_dialog
def config(self):
self.do_user_config(parent=self)
# Apply the changes
self.label.setText(prefs['hello_world_msg'])
calibre’s plugin loading system defines a couple of built-in functions that allow you to conveniently get files from the
plugin ZIP file.
get_resources(name_or_list_of_names) This function should be called with a list of paths to files inside
the ZIP file. For example to access the file icon.png in the directory images in the ZIP file, you would
use: images/icon.png. Always use a forward slash as the path separator, even on Windows.
When you pass in a single name, the function will return the raw bytes of that file or None if the
name was not found in the ZIP file. If you pass in more than one name then it returns a dict mapping
the names to bytes. If a name is not found, it will not be present in the returned dict.
get_icons(name_or_list_of_names) A convenience wrapper for get_resources() that creates QIcon ob-
jects from the raw bytes returned by get_resources. If a name is not found in the ZIP file the
corresponding QIcon will be null.
To allow users to configure your plugin, you must define three methods in your base plugin class, is_customizable,
config_widget and save_settings as shown below:
def is_customizable(self):
'''
This method must return True to enable customization via
Preferences->Plugins
'''
return True
def config_widget(self):
'''
Implement this method and :meth:`save_settings` in your plugin to
use a custom configuration dialog.
This method, if implemented, must return a QWidget. The widget can have
an optional method validate() that takes no arguments and is called
immediately after the user clicks OK. Changes are applied if and only
if the method returns True.
If for some reason you cannot perform the configuration at this time,
return a tuple of two strings (message, details), these will be
displayed as a warning dialog to the user and the process will be
aborted.
calibre has many different ways to store configuration data (a legacy of its long history). The recommended way is to
use the JSONConfig class, which stores your configuration information in a .json file.
The code to manage configuration data in the demo plugin is in config.py:
# Set defaults
prefs.defaults['hello_world_msg'] = 'Hello, World!'
class ConfigWidget(QWidget):
def __init__(self):
QWidget.__init__(self)
self.l = QHBoxLayout()
self.setLayout(self.l)
self.msg = QLineEdit(self)
self.msg.setText(prefs['hello_world_msg'])
self.l.addWidget(self.msg)
self.label.setBuddy(self.msg)
def save_settings(self):
prefs['hello_world_msg'] = self.msg.text()
The prefs object is now available throughout the plugin code by a simple:
from calibre_plugins.interface_demo.config import prefs
Now let’s change gears for a bit and look at creating a plugin to add tools to the calibre book editor. The plugin is
available here: editor_demo_plugin.zip87 .
The first step, as for all plugins is to create the import name empty txt file, as described above (page 203). We shall
name the file plugin-import-name-editor_plugin_demo.txt.
Now we create the mandatory __init__.py file that contains metadata about the plugin – its name, author, version,
etc.
from calibre.customize import EditBookToolPlugin
class DemoPlugin(EditBookToolPlugin):
A single editor plugin can provide multiple tools each tool corresponds to a single button in the toolbar and entry in
the Plugins menu in the editor. These can have sub-menus in case the tool has multiple related actions.
The tools must all be defined in the file main.py in your plugin. Every tool is a class that inherits from the
calibre.gui2.tweak_book.plugin.Tool (page 334) class. Let’s look at main.py from the demo plugin,
the source code is heavily commented and should be self-explanatory. Read the API documents of the calibre.
gui2.tweak_book.plugin.Tool (page 334) class for more details.
main.py
Here we will see the definition of a single tool that will multiply all font sizes in the book by a number provided by
the user. This tool demonstrates various important concepts that you will need in developing your own plugins, so you
should read the (heavily commented) source code carefully.
import re
from PyQt5.Qt import QAction, QInputDialog
from css_parser.css import CSSRule
class DemoTool(Tool):
#: If True the user can choose to place this tool in the plugins toolbar
allowed_in_toolbar = True
#: If True the user can choose to place this tool in the plugins menu
allowed_in_menu = True
ac.triggered.connect(self.ask_user)
return ac
def ask_user(self):
# Ask the user for a factor by which to multiply all font sizes
factor, ok = QInputDialog.getDouble(
self.gui, 'Enter a magnification factor', 'Allow font sizes in the book
˓→will be multiplied by the specified factor',
self.boss.commit_all_editors_to_container()
try:
self.magnify_fonts(factor)
except Exception:
# Something bad happened report the error to the user
import traceback
error_dialog(self.gui, _('Failed to magnify fonts'), _(
'Failed to magnify fonts, click "Show details" for more info'),
det_msg=traceback.format_exc(), show=True)
# Revert to the saved restore point
self.boss.revert_requested(self.boss.global_undo.previous_container)
else:
# Show the user what changes we have made, allowing her to
# revert them if necessary
self.boss.show_current_diff()
# Update the editor UI to take into account all the changes we
# have made
self.boss.apply_container_update_to_gui()
# Iterate over all style declarations in the book, this means css
# stylesheets, <style> tags and style="" attributes
for name, media_type in container.mime_map.items():
if media_type in OEB_STYLES:
# A stylesheet. Parsed stylesheets are css_parser CSSStylesheet
# objects.
self.magnify_stylesheet(container.parsed(name), factor)
container.dirty(name) # Tell the container that we have changed the
˓→stylesheet
self.magnify_declaration(block, factor)
elem.set('style', force_unicode(block.getCssText(separator=' '),
˓→'utf-8'))
Let’s break down main.py. We see that it defines a single tool, named Magnify fonts. This tool will ask the user for
a number and multiply all font sizes in the book by that number.
The first important thing is the tool name which you must set to some relatively unique string as it will be used as the
key for this tool.
The next important entry point is the calibre.gui2.tweak_book.plugin.Tool.create_action()
(page 335). This method creates the QAction objects that appear in the plugins toolbar and plugin menu. It also,
optionally, assigns a keyboard shortcut that the user can customize. The triggered signal from the QAction is con-
nected to the ask_user() method that asks the user for the font size multiplier, and then runs the magnification code.
The magnification code is well commented and fairly simple. The main things to note are that you get a reference to the
editor window as self.gui and the editor Boss as self.boss. The Boss is the object that controls the editor user
interface. It has many useful methods, that are documented in the calibre.gui2.tweak_book.boss.Boss
(page 335) class.
Finally, there is self.current_container which is a reference to the book being edited as a calibre.
ebooks.oeb.polish.container.Container (page 327) object. This represents the book as a collection
of its constituent HTML/CSS/image files and has convenience methods for doing many useful things. The container
object and various useful utility functions that can be reused in your plugin code are documented in API documentation
for the e-book editing tools (page 327).
If you are writing a user interface plugin that needs to make use of Qt WebEngine, it cannot be run in the main calibre
process as it is not possible to use WebEngine there. Instead you can copy the data your plugin needs to a temporary
directory and run the plugin with that data in a separate process. A simple example plugin follows that shows how to
do this.
You can download the plugin from webengine_demo_plugin.zip88 .
The important part of the plugin is in two functions:
def show_dialog(self):
# Ask the user for a URL
url, ok = QInputDialog.getText(self.gui, 'Enter a URL', 'Enter a URL to
˓→browse below', text='https://calibre-ebook.com')
def main(url):
# This function is run in a separate process and can do anything it likes,
# including use QWebEngine. Here it simply opens the passed in URL
# in a QWebEngineView
app = Application([])
w = QWebEngineView()
w.setUrl(QUrl(url))
w.show()
w.raise_()
app.exec_()
The show_demo() function asks the user for a URL and then runs the main() function passing it that URL. The
main() function displays the URL in a QWebEngineView.
You can have all the user interface strings in your plugin translated and displayed in whatever language is set for the
main calibre user interface.
The first step is to go through your plugin’s source code and mark all user visible strings as translatable, by surrounding
them in _(). For example:
action_spec = (_('My plugin'), None, _('My plugin is cool'), None)
Then use some program to generate .po files from your plugin source code. There should be one .po file for every
language you want to translate into. For example: de.po for German, fr.po for French and so on. You can use the
Poedit89 program for this.
88 https://calibre-ebook.com/downloads/webengine_demo_plugin.zip
89 https://poedit.net/
Send these .po files to your translators. Once you get them back, compile them into .mo files. You can again use Poedit
for that, or just do:
Put the .mo files into the translations folder in your plugin.
The last step is to simply call the function load_translations() at the top of your plugin’s .py files. For performance
reasons you should only call this function in those .py files that actually have translatable strings. So in a typical User
Interface plugin you would call it at the top of ui.py but not __init__.py.
You can test the translations of your plugins by changing the user interface language in calibre under
Preferences→Interface→Look & feel or by running calibre like this:
CALIBRE_OVERRIDE_LANG=de calibre
Replace de with the language code of the language you want to test.
As you may have noticed above, a plugin in calibre is a class. There are different classes for the different types of
plugins in calibre. Details on each class, including the base class of all plugins can be found in API documentation for
plugins (page 227).
Your plugin is almost certainly going to use code from calibre. To learn how to find various bits of functionality in the
calibre code base, read the section on the calibre Code layout (page 314).
The first, most important step is to run calibre in debug mode. You can do this from the command line with:
calibre-debug -g
Or from within calibre by right-clicking the Preferences button or using the Ctrl+Shift+R keyboard shortcut.
When running from the command line, debug output will be printed to the console, when running from within calibre
the output will go to a txt file.
You can insert print statements anywhere in your plugin code, they will be output in debug mode. Remember, this is
Python, you really shouldn’t need anything more than print statements to debug ;) I developed all of calibre using just
this debugging technique.
You can quickly test changes to your plugin by using the following command line:
This will shutdown a running calibre, wait for the shutdown to complete, then update your plugin in calibre and
relaunch calibre.
If you would like to share the plugins you have created with other users of calibre, post your plugin in a new thread in
the calibre plugins forum91 .
The calibre E-book viewer has the ability to display math embedded in e-books (EPUB and HTML files). You can
typeset the math directly with TeX or MathML or AsciiMath. The calibre E-book viewer uses the excellent MathJax92
library to do this. This is a brief tutorial on creating e-books with math in them that work well with the calibre E-book
viewer.
You can write mathematics inline inside a simple HTML file and the calibre E-book viewer will render it into properly
typeset mathematics. In the example below, we use TeX notation for mathematics. You will see that you can use
normal TeX commands, with the small caveat that ampersands and less than and greater than signs have to be written
as & < and > respectively.
The first step is to tell calibre that this will contains maths. You do this by adding the following snippet of code to the
<head> section of the HTML file:
<script type="text/x-mathjax-config"></script>
That’s it, now you can type mathematics just as you would in a .tex file. For example, here are Lorentz’s equations:
<h2>The Lorenz Equations</h2>
<p>
\begin{align}
\dot{x} & = \sigma(y-x) \\
\dot{y} & = \rho x - y - xz \\
\dot{z} & = -\beta z + xy
\end{align}
</p>
This snippet looks like the following screen shot in the calibre E-book viewer.
The complete HTML file, with more equations and inline mathematics is reproduced below. You can convert this
HTML file to EPUB in calibre to end up with an e-book you can distribute easily to other people.
91 https://www.mobileread.com/forums/forumdisplay.php?f=237
92 https://www.mathjax.org
<!DOCTYPE html>
<html>
<!-- Copyright (c) 2012 Design Science, Inc. -->
<head>
<title>Math Test Page</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<!-- This script tag is needed to make calibre's ebook-viewer recpgnize that this
˓→file needs math typesetting -->
<script type="text/x-mathjax-config">
// This line adds numbers to all equations automatically, unless explicitly
˓→suppressed.
<style>
h1 {text-align:center}
h2 {
font-weight: bold;
background-color: #DDDDDD;
padding: .2em .5em;
margin-top: 1.5em;
border-top: 3px solid #666666;
border-bottom: 2px solid #999999;
}
</style>
</head>
<body>
<h1>Sample Equations</h1>
<p>
\begin{align}
\dot{x} & = \sigma(y-x) \label{lorenz}\\
\dot{y} & = \rho x - y - xz \\
\dot{z} & = -\beta z + xy
\end{align}
</p>
<p>\[
\left( \sum_{k=1}^n a_k b_k \right)^{\!\!2} \leq
\left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)
\]</p>
<p>\[
\mathbf{V}_1 \times \mathbf{V}_2 =
\begin{vmatrix}
\mathbf{i} & \mathbf{j} & \mathbf{k} \\
\frac{\partial X}{\partial u} & \frac{\partial Y}{\partial u} & 0 \\
\frac{\partial X}{\partial v} & \frac{\partial Y}{\partial v} & 0 \\
\end{vmatrix}
(continues on next page)
<h2>The probability of getting \(k\) heads when flipping \(n\) coins is:</h2>
<p>\[
\frac{1}{(\sqrt{\phi \sqrt{5}}-\phi) e^{\frac25 \pi}} =
1+\frac{e^{-2\pi}} {1+\frac{e^{-4\pi}} {1+\frac{e^{-6\pi}}
{1+\frac{e^{-8\pi}} {1+\ldots} } } }
\]</p>
<p>\[
1 + \frac{q^2}{(1-q)}+\frac{q^6}{(1-q)(1-q^2)}+\cdots =
\prod_{j=0}^{\infty}\frac{1}{(1-q^{5j+2})(1-q^{5j+3})},
\quad\quad \text{for $|q|<1$}.
\]</p>
<h2>Maxwell's Equations</h2>
<p>
\begin{align}
\nabla \times \vec{\mathbf{B}} -\, \frac1c\, \frac{\partial\vec{\mathbf{E}}}
˓→{\partial t} & = \frac{4\pi}{c}\vec{\mathbf{j}} \\
<h2>In-line Mathematics</h2>
<h2>References to equations</h2>
</body>
</html>
Since the calibre E-book viewer uses the MathJax library to render mathematics, the best place to find out more about
math in e-books and get help is the MathJax website93 .
calibre’s Create catalog feature enables you to create a catalog of your library in a variety of formats. This help file
describes cataloging options when generating a catalog in AZW3, EPUB and MOBI formats.
If you want all of your library cataloged, remove any search or filtering criteria in the main window. With a single
book selected, all books in your library will be candidates for inclusion in the generated catalog. Individual books may
be excluded by various criteria; see the Excluded genres (page 222) section below for more information.
If you want only some of your library cataloged, you have two options:
• Create a multiple selection of the books you want cataloged. With more than one book selected in calibre’s main
window, only the selected books will be cataloged.
• Use the Search field or the Tag browser to filter the displayed books. Only the displayed books will be cataloged.
To begin catalog generation, select the menu item Convert books > Create a catalog of the books in your calibre
library. You may also add a Create catalog button to a toolbar in Preferences > Interface > Toolbars & menus for
easier access to the Generate catalog dialog.
93 https://www.mathjax.org
In Catalog options, select AZW3, EPUB or MOBI as the Catalog format. In the Catalog title field, provide a name
that will be used for the generated catalog. If a catalog of the same name and format already exists, it will be replaced
with the newly-generated catalog.
Enabling Send catalog to device automatically will download the generated catalog to a connected device upon com-
pletion.
10.7.3 Prefixes
Prefix rules allow you to add a prefix to book listings when certain criteria are met. For example, you might want to
mark books you’ve read with a checkmark, or books on your wishlist with an X.
The checkbox in the first column enables the rule. Name is a rule name that you provide. Field is either Tags or a
custom column from your library. Value is the content of Field to match. When a prefix rule is satisfied, the book will
be marked with the selected Prefix.
Three prefix rules have been specified in the example above:
1. Read book specifies that a book with any date in a custom column named Last read will be prefixed with a
checkmark symbol.
2. Wishlist item specifies that any book with a Wishlist tag will be prefixed with an X symbol.
3. Library books specifies that any book with a value of True (or Yes) in a custom column Available in Library
will be prefixed with a double arrow symbol.
The first matching rule supplies the prefix. Disabled or incomplete rules are ignored.
Exclusion rules allow you to specify books that will not be cataloged.
The checkbox in the first column enables the rule. Name is a rule name that you provide. Field is either Tags or a
custom column in your library. Value is the content of Field to match. When an exclusion rule is satisfied, the book
will be excluded from the generated catalog.
Two exclusion rules have been specified in the example above:
1. The Catalogs rule specifies that any book with a Catalog tag will be excluded from the generated catalog.
2. The Archived Books rule specifies that any book with a value of Archived in the custom column Status will be
excluded from the generated catalog.
All rules are evaluated for every book. Disabled or incomplete rules are ignored.
When the catalog is generated, tags in your database are used as genres. For example, you may use the tags Fiction
and Nonfiction. These tags become genres in the generated catalog, with books listed under their respective genre
lists based on their assigned tags. A book will be listed in every genre section for which it has a corresponding tag.
You may be using certain tags for other purposes, perhaps a + to indicate a read book, or a bracketed tag like [Amazon
Freebie] to indicate a book’s source. The Excluded genres regex allows you to specify tags that you don’t want
used as genres in the generated catalog. The default exclusion regex pattern \[.+\]\+ excludes any tags of the form
[tag], as well as excluding +, the default tag for read books, from being used as genres in the generated catalog.
You can also use an exact tag name in a regex. For example, [Amazon Freebie] or [Project Gutenberg].
If you want to list multiple exact tags for exclusion, put a pipe (vertical bar) character between them: [Amazon
Freebie]|[Project Gutenberg].
Results of regex shows you which tags will be excluded when the catalog is built, based on the tags in your database
and the regex pattern you enter. The results are updated as you modify the regex pattern.
Catalog cover specifies whether to generate a new cover or use an existing cover. It is possible to create a custom
cover for your catalogs - see Custom catalog covers (page 224) for more information. If you have created a custom
cover that you want to reuse, select Use existing cover. Otherwise, select Generate new cover.
Extra Description note specifies a custom column’s contents to be inserted into the Description page, next to the cover
thumbnail. For example, you might want to display the date you last read a book using a Last Read custom column.
For advanced use of the Description note feature, see this post in the calibre forum94 .
Thumb width specifies a width preference for cover thumbnails included with Descriptions pages. Thumbnails are
cached to improve performance. To experiment with different widths, try generating a catalog with just a few books
until you’ve determined your preferred width, then generate your full catalog. The first time a catalog is generated
with a new thumbnail width, performance will be slower, but subsequent builds of the catalog will take advantage of
the thumbnail cache.
Merge with Comments specifies a custom column whose content will be non-destructively merged with the Comments
metadata during catalog generation. For example, you might have a custom column Author bio that you’d like to
append to the Comments metadata. You can choose to insert the custom column contents before or after the Comments
section, and optionally separate the appended content with a horizontal rule separator. Eligible custom column types
include text, comments, and composite.
94 https://www.mobileread.com/forums/showpost.php?p=1335767&postcount=395
With the Generate Cover plugin95 installed, you can create cus-
tom covers for your catalog. To install the plugin, go to Preferences > Advanced > Plugins > Get new plugins.
For more information on calibre’s Catalog feature, see the MobileRead forum sticky Creating Catalogs - Start here96 ,
where you can find information on how to customize the catalog templates, and how to submit a bug report.
To ask questions or discuss calibre’s Catalog feature with other users, visit the MobileRead forum Calibre Catalogs97 .
In calibre, a Virtual library is a way to tell calibre to open only a subset of a normal library. For example, you might
want to only work with books by a certain author, or books having only a certain tag. Using Virtual libraries is the
preferred way of partitioning your large book collection into smaller sub collections. It is superior to splitting up your
library into multiple smaller libraries as, when you want to search through your entire collection, you can simply go
back to the full library. There is no way to search through multiple separate libraries simultaneously in calibre.
A Virtual library is different from a simple search. A search will only restrict the list of books shown in the book list.
A Virtual library does that, and in addition it also restricts the entries shown in the Tag browser to the left. The Tag
browser will only show tags, authors, series, publishers, etc. that come from the books in the Virtual library. A Virtual
library thus behaves as though the actual library contains only the restricted set of books.
95 https://www.mobileread.com/forums/showthread.php?t=124219
96 https://www.mobileread.com/forums/showthread.php?t=118556
97 https://www.mobileread.com/forums/forumdisplay.php?f=236
To use a Virtual library click the Virtual library button located to the left of the Search
bar and select the Create Virtual library option. As a first example, let’s create a Virtual library that shows us only the
books by a particular author. Click the Authors link as shown in the image below and choose the author you want to
use and click OK.
The Create Virtual library dialog has been filled in for you. Click OK and you will see that a new Virtual library has
been created, and automatically switched to, that displays only the books by the selected author. As far as calibre is
concerned, it is as if your library contains only the books by the selected author.
You can switch back to the full library at any time by once again clicking the Virtual library and selecting the entry
named <None>.
Virtual libraries are based on searches. You can use any search as the basis of a Virtual library. The Virtual library
will contain only the books matched by that search. First, type in the search you want to use in the Search bar or
build a search using the Tag browser. When you are happy with the returned results, click the Virtual library button,
choose Create library and enter a name for the new Virtual library. The Virtual library will then be created based on
the search you just typed in. Searches are very powerful, for examples of the kinds of things you can do with them,
see The search interface (page 11).
You can edit a previously created Virtual library or remove it, by clicking the Virtual library and choosing the appro-
priate action.
You can tell calibre that you always want to apply a particular Virtual library when the current library is opened, by
going to Preferences→Interface→Behavior.
You can quickly use the current search as a temporary Virtual library by clicking the Virtual library button and choosing
the *current search entry.
You can display all available Virtual libraries as tabs above the book list. This is particularly handy if you like
switching between Virtual libraries very often. Click the Virtual library button and select Show Virtual libraries as
tabs. You can re-arrange the tabs by drag and drop and close ones you do not want to see. Closed tabs can be restored
by right-clicking on the tab bar.
You can search for books that are in a Virtual library using the vl: prefix. For example, vl:Read will find all the
books in the Read Virtual library. The search vl:Read and vl:"Science Fiction" will find all the books
that are in both the Read and Science Fiction Virtual libraries.
The value following vl: must be the name of a Virtual library. If the Virtual library name contains spaces then
surround it with quotes.
One use for a Virtual library search is in the content server. In Preferences→Sharing over the net→Require username
and password you can limit the calibre libraries visible to a user. For each visible library you can specify a search
expression to further limit which books are seen. Use vl:"Virtual library name" to limit the books to those
in a Virtual library.
You can further restrict the books shown in a Virtual library by using Additional restrictions. An additional restriction
is saved search you previously created that can be applied to the current Virtual library to further restrict the books
shown in a Virtual library. For example, say you have a Virtual library for books tagged as Historical Fiction and
a saved search that shows you unread books, you can click the Virtual Library button and choose the Additional
restriction option to show only unread Historical Fiction books. To learn about saved searches, see Saving searches
(page 14).
Customizing calibre
calibre has a highly modular design. Various parts of it can be customized. You can learn how to create recipes to add
new sources of online content to calibre in the Section Adding your favorite news website (page 25). Here, you will
learn, first, how to use environment variables and tweaks to customize calibre’s behavior, and then how to specify your
own static resources like icons and templates to override the defaults and finally how to use plugins to add functionality
to calibre.
Defines various abstract base classes that can be subclassed to create powerful plugins. The useful classes are:
227
calibre User Manual, Release 4.21.0
11.1.1 Plugin
class calibre.customize.Plugin(plugin_path)
A calibre plugin. Useful members include:
• self.plugin_path: Stores path to the ZIP file that contains this plugin or None if it is a builtin
plugin
• self.site_customization: Stores a customization string entered by the user.
Methods that should be overridden in sub classes:
• initialize() (page 228)
• customization_help() (page 229)
Useful methods:
• temporary_file() (page 229)
• __enter__()
• load_resources() (page 229)
supported_platforms = []
List of platforms this plugin works on. For example: ['windows', 'osx', 'linux']
name = u'Trivial Plugin'
The name of this plugin. You must set it something other than Trivial Plugin for it to work.
version = (1, 0, 0)
The version of this plugin as a 3-tuple (major, minor, revision)
description = u'Does absolutely nothing'
A short string describing what this plugin does
author = u'Unknown'
The author of this plugin
priority = 1
When more than one plugin exists for a filetype, the plugins are run in order of decreasing priority. Plugins
with higher priority will be run first. The highest possible priority is sys.maxsize. Default priority is
1.
minimum_calibre_version = (0, 4, 118)
The earliest version of calibre this plugin requires
can_be_disabled = True
If False, the user will not be able to disable this plugin. Use with care.
type = u'Base'
The type of this plugin. Used for categorizing plugins in the GUI
initialize()
Called once when calibre plugins are initialized. Plugins are re-initialized every time a new plugin is
added. Also note that if the plugin is run in a worker process, such as for adding books, then the plugin
will be initialized for every new worker process.
Perform any plugin specific initialization here, such as extracting resources from the plugin ZIP file. The
path to the ZIP file is available as self.plugin_path.
Note that self.site_customization is not available at this point.
config_widget()
Implement this method and save_settings() (page 229) in your plugin to use a custom configuration
dialog, rather then relying on the simple string based default customization.
This method, if implemented, must return a QWidget. The widget can have an optional method validate()
that takes no arguments and is called immediately after the user clicks OK. Changes are applied if and only
if the method returns True.
If for some reason you cannot perform the configuration at this time, return a tuple of two strings (message,
details), these will be displayed as a warning dialog to the user and the process will be aborted.
save_settings(config_widget)
Save the settings specified by the user with config_widget.
Parameters config_widget – The widget returned by config_widget() (page 229).
do_user_config(parent=None)
This method shows a configuration dialog for this plugin. It returns True if the user clicks OK, False
otherwise. The changes are automatically applied.
load_resources(names)
If this plugin comes in a ZIP file (user added plugin), this method will allow you to load resources from
the ZIP file.
For example to load an image:
pixmap = QPixmap()
pixmap.loadFromData(self.load_resources(['images/icon.png'])['images/icon.png
˓→'])
icon = QIcon(pixmap)
Parameters names – List of paths to resources in the ZIP file using / as separator
Returns A dictionary of the form {name: file_contents}. Any names that were not
found in the ZIP file will not be present in the dictionary.
customization_help(gui=False)
Return a string giving help on how to customize this plugin. By default raise a
NotImplementedError, which indicates that the plugin does not require customization.
If you re-implement this method in your subclass, the user will be asked to enter a string as customization
for this plugin. The customization string will be available as self.site_customization.
Site customization could be anything, for example, the path to a needed binary on the user’s computer.
Parameters gui – If True return HTML help, otherwise return plain text help.
temporary_file(suffix)
Return a file-like object that is a temporary file on the file system. This file will remain available even after
being closed and will only be removed on interpreter shutdown. Use the name member of the returned
object to access the full path to the created temporary file.
Parameters suffix – The suffix that the temporary file will have.
cli_main(args)
This method is the main entry point for your plugins command line interface. It is called when the user
does: calibre-debug -r “Plugin Name”. Any arguments passed are present in the args variable.
11.1.2 FileTypePlugin
class calibre.customize.FileTypePlugin(plugin_path)
Bases: calibre.customize.Plugin (page 228)
A plugin that is associated with a particular set of file types.
file_types = set([])
Set of file types for which this plugin should be run. Use ‘*’ for all file types. For example: {'lit',
'mobi', 'prc'}
on_import = False
If True, this plugin is run when books are added to the database
on_postimport = False
If True, this plugin is run after books are added to the database. In this case the postimport and postadd
methods of the plugin are called.
on_preprocess = False
If True, this plugin is run just before a conversion
on_postprocess = False
If True, this plugin is run after conversion on the final file produced by the conversion output plugin.
run(path_to_ebook)
Run the plugin. Must be implemented in subclasses. It should perform whatever modifications are required
on the e-book and return the absolute path to the modified e-book. If no modifications are needed, it should
return the path to the original e-book. If an error is encountered it should raise an Exception. The default
implementation simply return the path to the original e-book. Note that the path to the original file (before
any file type plugins are run, is available as self.original_path_to_file).
The modified e-book file should be created with the temporary_file() method.
Parameters path_to_ebook – Absolute path to the e-book.
Returns Absolute path to the modified e-book.
postimport(book_id, book_format, db)
Called post import, i.e., after the book file has been added to the database. Note that this is different from
postadd() (page 230) which is called when the book record is created for the first time. This method is
called whenever a new file is added to a book record. It is useful for modifying the book record based on
the contents of the newly added file.
Parameters
• book_id – Database id of the added book.
• book_format – The file type of the book that was added.
• db – Library database.
postadd(book_id, fmt_map, db)
Called post add, i.e. after a book has been added to the db. Note that this is different from postimport()
(page 230), which is called after a single book file has been added to a book. postadd() is called only when
an entire book record with possibly more than one book file has been created for the first time. This is
useful if you wish to modify the book record in the database when the book is first added to calibre.
Parameters
class calibre.customize.CatalogPlugin(plugin_path)
Bases: calibre.customize.Plugin (page 228)
A plugin that implements a catalog generator.
file_types = set([])
Output file type for which this plugin should be run. For example: ‘epub’ or ‘xml’
cli_options = []
CLI parser options specific to this plugin, declared as namedtuple Option:
from collections import namedtuple Option = namedtuple(‘Option’, ‘option, default, dest, help’)
cli_options = [Option(‘–catalog-title’, default = ‘My Catalog’, dest = ‘catalog_title’, help = (_(‘Ti-
tle of generated catalog. nDefault:’) + ” ‘” + ‘%default’ + “’”))] cli_options parsed in cali-
bre.db.cli.cmd_catalog:option_parser()
initialize()
If plugin is not a built-in, copy the plugin’s .ui and .py files from the ZIP file to $TMPDIR. Tab will be
dynamically generated and added to the Catalog Options dialog in calibre.gui2.dialogs.catalog.py:Catalog
run(path_to_output, opts, db, ids, notification=None)
Run the plugin. Must be implemented in subclasses. It should generate the catalog in the format specified
in file_types, returning the absolute path to the generated catalog file. If an error is encountered it should
raise an Exception.
The generated catalog file should be created with the temporary_file() method.
Parameters
• path_to_output – Absolute path to the generated catalog file.
• opts – A dictionary of keyword arguments
• db – A LibraryDatabase2 object
prefer_results_with_isbn = True
If set to True, and this source returns multiple results for a query, some of which have ISBNs and some of
which do not, the results without ISBNs will be ignored
is_configured()
Return False if your plugin needs to be configured before it can be used. For example, it might need a
username/password/API key.
get_author_tokens(authors, only_first_author=True)
Take a list of authors and return a list of tokens useful for an AND search query. This function tries to
return tokens in first name middle names last name order, by assuming that if a comma is in the author
name, the name is in lastname, other names form.
get_title_tokens(title, strip_joiners=True, strip_subtitle=False)
Take a title and return a list of tokens useful for an AND search query. Excludes connectives(optionally)
and punctuation.
split_jobs(jobs, num)
Split a list of jobs into at most num groups, as evenly as possible
test_fields(mi)
Return the first field from self.touched_fields that is null on the mi object
clean_downloaded_metadata(mi)
Call this method in your plugin’s identify method to normalize metadata before putting the Metadata object
into result_queue. You can of course, use a custom algorithm suited to your metadata source.
get_book_url(identifiers)
Return a 3-tuple or None. The 3-tuple is of the form: (identifier_type, identifier_value, URL). The URL
is the URL for the book identified by identifiers at this source. identifier_type, identifier_value specify the
identifier corresponding to the URL. This URL must be browseable to by a human using a browser. It is
meant to provide a clickable link for the user to easily visit the books page at this source. If no URL is
found, return None. This method must be quick, and consistent, so only implement it if it is possible to
construct the URL from a known scheme given identifiers.
get_book_url_name(idtype, idval, url)
Return a human readable name from the return value of get_book_url().
get_book_urls(identifiers)
Override this method if you would like to return multiple urls for this book. Return a list of 3-tuples. By
default this method simply calls get_book_url() (page 233).
get_cached_cover_url(identifiers)
Return cached cover URL for the book identified by the identifiers dict or None if no such URL exists.
Note that this method must only return validated URLs, i.e. not URLS that could result in a generic cover
image or a not found error.
id_from_url(url)
Parse a URL and return a tuple of the form: (identifier_type, identifier_value). If the URL does not match
the pattern for the metadata source, return None.
identify_results_keygen(title=None, authors=None, identifiers={})
Return a function that is used to generate a key that can sort Metadata objects by their relevance given a
search query (title, authors, identifiers).
These keys are used to sort the results of a call to identify() (page 233).
For details on the default algorithm see InternalMetadataCompareKeyGen (page 234). Re-
implement this function in your plugin if the default algorithm is not suitable.
The sort key ensures that an ascending order sort is a sort by order of decreasing relevance.
The algorithm is:
• Prefer results that have at least one identifier the same as for the query
• Prefer results with a cached cover URL
• Prefer results with all available fields filled in
• Prefer results with the same language as the current user interface language
• Prefer results that are an exact title match to the query
• Prefer results with longer comments (greater than 10% longer)
• Use the relevance of the result as reported by the metadata source’s search engine
class calibre.customize.conversion.InputFormatPlugin(*args)
Bases: calibre.customize.Plugin (page 228)
InputFormatPlugins are responsible for converting a document into HTML+OPF+CSS+etc. The results of the
conversion must be encoded in UTF-8. The main action happens in convert() (page 235).
file_types = set([])
Set of file types for which this plugin should be run For example: set(['azw', 'mobi', 'prc'])
is_image_collection = False
If True, this input plugin generates a collection of images, one per HTML file. This can be set dynamically,
in the convert method if the input files can be both image collections and non-image collections. If you set
this to True, you must implement the get_images() method that returns a list of images.
core_usage = 1
Number of CPU cores used by this plugin. A value of -1 means that it uses all available cores
for_viewer = False
If set to True, the input plugin will perform special processing to make its output suitable for viewing
output_encoding = u'utf-8'
The encoding that this input plugin creates files in. A value of None means that the encoding is undefined
and must be detected individually
common_options = set([<calibre.customize.conversion.OptionRecommendation object>])
Options shared by all Input format plugins. Do not override in sub-classes. Use options (page 235)
instead. Every option must be an instance of OptionRecommendation.
options = set([])
Options to customize the behavior of this plugin. Every option must be an instance of
OptionRecommendation.
recommendations = set([])
A set of 3-tuples of the form (option_name, recommended_value, recommendation_level)
get_images()
Return a list of absolute paths to the images, if this input plugin represents an image collection. The list of
images is in the same order as the spine and the TOC.
convert(stream, options, file_ext, log, accelerators)
This method must be implemented in sub-classes. It must return the path to the created OPF file or an
OEBBook instance. All output should be contained in the current directory. If this plugin creates files
outside the current directory they must be deleted/marked for deletion before this method returns.
Parameters
• stream – A file like object that contains the input file.
• options – Options to customize the conversion process. Guaranteed to have attributes
corresponding to all the options declared by this plugin. In addition, it will have a verbose
attribute that takes integral values from zero upwards. Higher numbers mean be more
verbose. Another useful attribute is input_profile that is an instance of calibre.
customize.profiles.InputProfile.
• file_ext – The extension (without the .) of the input file. It is guaranteed to be one of
the file_types supported by this plugin.
• log – A calibre.utils.logging.Log object. All output should use this object.
• accelarators – A dictionary of various information that the input plugin can get easily
that would speed up the subsequent stages of the conversion.
postprocess_book(oeb, opts, log)
Called to allow the input plugin to perform postprocessing after the book has been parsed.
specialize(oeb, opts, log, output_fmt)
Called to allow the input plugin to specialize the parsed book for a particular output format. Called after
postprocess_book and before any transforms are performed on the parsed book.
gui_configuration_widget(parent, get_option_by_name, get_option_help, db, book_id=None)
Called to create the widget used for configuring this plugin in the calibre GUI. The widget must be an
instance of the PluginWidget class. See the builtin input plugins for examples.
class calibre.customize.conversion.OutputFormatPlugin(*args)
Bases: calibre.customize.Plugin (page 228)
OutputFormatPlugins are responsible for converting an OEB document (OPF+HTML) into an output e-book.
The OEB document can be assumed to be encoded in UTF-8. The main action happens in convert()
(page 236).
file_type = None
The file type (extension without leading period) that this plugin outputs
common_options = set([<calibre.customize.conversion.OptionRecommendation object>])
Options shared by all Input format plugins. Do not override in sub-classes. Use options (page 236)
instead. Every option must be an instance of OptionRecommendation.
options = set([])
Options to customize the behavior of this plugin. Every option must be an instance of
OptionRecommendation.
recommendations = set([])
A set of 3-tuples of the form (option_name, recommended_value, recommendation_level)
convert(oeb_book, output, input_plugin, opts, log)
Render the contents of oeb_book (which is an instance of calibre.ebooks.oeb.OEBBook) to the
file specified by output.
Parameters
• output – Either a file like object or a string. If it is a string it is the path to a directory
that may or may not exist. The output plugin should write its output into that directory. If
it is a file like object, the output plugin should write its output into the file.
• input_plugin – The input plugin that was used at the beginning of the conversion
pipeline.
The base class for all device drivers is DevicePlugin (page 237). However, if your device exposes itself as a
USBMS drive to the operating system, you should use the USBMS class instead as it implements all the logic needed
to support these kinds of devices.
class calibre.devices.interface.DevicePlugin(plugin_path)
Bases: calibre.customize.Plugin (page 228)
Defines the interface that should be implemented by backends that communicate with an e-book reader.
FORMATS = [u'lrf', u'rtf', u'pdf', u'txt']
Ordered list of supported formats
VENDOR_ID = 0
VENDOR_ID can be either an integer, a list of integers or a dictionary If it is a dictionary, it must be a
dictionary of dictionaries, of the form:
{
integer_vendor_id : { product_id : [list of BCDs], ... },
...
}
PRODUCT_ID = 0
An integer or a list of integers
BCD = None
BCD can be either None to not distinguish between devices based on BCD, or it can be a list of the BCD
numbers of all devices supported by this driver.
THUMBNAIL_HEIGHT = 68
Height for thumbnails on the device
THUMBNAIL_COMPRESSION_QUALITY = 75
Compression quality for thumbnails. Set this closer to 100 to have better quality thumbnails with fewer
compression artifacts. Of course, the thumbnails get larger as well.
WANTS_UPDATED_THUMBNAILS = False
Set this to True if the device supports updating cover thumbnails during sync_booklists. Setting it to true
will ask device.py to refresh the cover thumbnails during book matching
CAN_SET_METADATA = [u'title', u'authors', u'collections']
Whether the metadata on books can be set via the GUI.
CAN_DO_DEVICE_DB_PLUGBOARD = False
Whether the device can handle device_db metadata plugboards
path_sep = '/'
Path separator for paths to books on device
icon = u'/home/kovid/work/calibre/resources/images/reader.png'
Icon for this device
UserAnnotation
alias of Annotation
OPEN_FEEDBACK_MESSAGE = None
GUI displays this as a message if not None. Useful if opening can take a long time
VIRTUAL_BOOK_EXTENSIONS = frozenset([])
Set of extensions that are “virtual books” on the device and therefore cannot be viewed/saved/added to
library. For example: frozenset(['kobo'])
VIRTUAL_BOOK_EXTENSION_MESSAGE = None
Message to display to user for virtual book extensions.
NUKE_COMMENTS = None
Whether to nuke comments in the copy of the book sent to the device. If not None this should be short
string that the comments will be replaced by.
MANAGES_DEVICE_PRESENCE = False
If True indicates that this driver completely manages device detection, ejecting and so forth. If you set this
to True, you must implement the detect_managed_devices and debug_managed_device_detection meth-
ods. A driver with this set to true is responsible for detection of devices, managing a blacklist of devices,
a list of ejected devices and so forth. calibre will periodically call the detect_managed_devices() method
and if it returns a detected device, calibre will call open(). open() will be called every time a device is
returned even if previous calls to open() failed, therefore the driver must maintain its own blacklist of
failed devices. Similarly, when ejecting, calibre will call eject() and then assuming the next call to de-
tect_managed_devices() returns None, it will call post_yank_cleanup().
SLOW_DRIVEINFO = False
If set the True, calibre will call the get_driveinfo() (page 240) method after the books lists have
been loaded to get the driveinfo.
ASK_TO_ALLOW_CONNECT = False
If set to True, calibre will ask the user if they want to manage the device with calibre, the first
time it is detected. If you set this to True you must implement get_device_uid() (page 242)
and ignore_connected_device() (page 242) and get_user_blacklisted_devices()
(page 243) and set_user_blacklisted_devices() (page 243)
user_feedback_after_callback = None
Set this to a dictionary of the form {‘title’:title, ‘msg’:msg, ‘det_msg’:detailed_msg} to have calibre popup
a message to the user after some callbacks are run (currently only upload_books). Be careful to not spam
the user with too many messages. This variable is checked after every callback, so only set it when you
really need to.
is_usb_connected(devices_on_system, debug=False, only_presence=False)
Return True, device_info if a device handled by this plugin is currently connected.
This method can raise an OpenFeedback exception to display a message to the user.
Parameters
• connected_device – The device that we are trying to open. It is a tuple of (vendor
id, product id, bcd, manufacturer name, product name, device serial number). However,
some devices have no serial number and on Windows only the first three fields are present,
the rest are None.
• library_uuid – The UUID of the current calibre library. Can be None if there is no
library (for example when used from the command line).
eject()
Un-mount / eject the device from the OS. This does not check if there are pending GUI jobs that need to
communicate with the device.
NOTE: That this method may not be called on the same thread as the rest of the device methods.
post_yank_cleanup()
Called if the user yanks the device without ejecting it first.
set_progress_reporter(report_progress)
Set a function to report progress information.
Parameters report_progress – Function that is called with a % progress (number between
0 and 100) for various tasks If it is called with -1 that means that the task does not have any
progress information
get_device_information(end_session=True)
Ask device for device information. See L{DeviceInfoQuery}.
Returns (device name, device version, software version on device, MIME type) The tuple can
optionally have a fifth element, which is a drive information dictionary. See usbms.driver for
an example.
get_driveinfo()
Return the driveinfo dictionary. Usually called from get_device_information(), but if loading the driveinfo
is slow for this driver, then it should set SLOW_DRIVEINFO. In this case, this method will be called by
calibre after the book lists have been loaded. Note that it is not called on the device thread, so the driver
should cache the drive info in the books() method and this function should return the cached data.
card_prefix(end_session=True)
Return a 2 element list of the prefix to paths on the cards. If no card is present None is set for the card’s
prefix. E.G. (‘/place’, ‘/place2’) (None, ‘place2’) (‘place’, None) (None, None)
total_space(end_session=True)
Get total space available on the mountpoints:
1. Main memory
2. Memory Card A
3. Memory Card B
Returns A 3 element list with total space in bytes of (1, 2, 3). If a particular device doesn’t have
any of these locations it should return 0.
free_space(end_session=True)
Get free space available on the mountpoints:
1. Main memory
2. Card A
3. Card B
Returns A 3 element list with free space in bytes of (1, 2, 3). If a particular device doesn’t have
any of these locations it should return -1.
books(oncard=None, end_session=True)
Return a list of e-books on the device.
Parameters oncard – If ‘carda’ or ‘cardb’ return a list of e-books on the specific storage card,
otherwise return list of e-books in main memory of device. If a card is specified and no books
are on the card return empty list.
Returns A BookList.
upload_books(files, names, on_card=None, end_session=True, metadata=None)
Upload a list of books to the device. If a file already exists on the device, it should be replaced. This
method should raise a FreeSpaceError if there is not enough free space on the device. The text of the
FreeSpaceError must contain the word “card” if on_card is not None otherwise it must contain the word
“memory”.
Parameters
• files – A list of paths
• names – A list of file names that the books should have once uploaded to the device.
len(names) == len(files)
• metadata – If not None, it is a list of Metadata objects. The idea is to use the metadata
to determine where on the device to put the book. len(metadata) == len(files). Apart from
the regular cover (path to cover), there may also be a thumbnail attribute, which should be
used in preference. The thumbnail attribute is of the form (width, height, cover_data as
jpeg).
Returns A list of 3-element tuples. The list is meant to be passed to
add_books_to_metadata() (page 241).
classmethod add_books_to_metadata(locations, metadata, booklists)
Add locations to the booklists. This function must not communicate with the device.
Parameters
• locations – Result of a call to L{upload_books}
• metadata – List of Metadata objects, same as for upload_books() (page 241).
• booklists – A tuple containing the result of calls to (books(oncard=None)(),
books(oncard='carda')(), :meth‘books(oncard=’cardb’)‘).
delete_books(paths, end_session=True)
Delete books at paths on device.
classmethod remove_books_from_metadata(paths, booklists)
Remove books from the metadata list. This function must not communicate with the device.
Parameters
• paths – paths to books on the device.
• booklists – A tuple containing the result of calls to (books(oncard=None)(),
books(oncard='carda')(), :meth‘books(oncard=’cardb’)‘).
sync_booklists(booklists, end_session=True)
Update metadata on device.
Parameters booklists – A tuple containing the result of calls
to (books(oncard=None)(), books(oncard='carda')(),
:meth‘books(oncard=’cardb’)‘).
get_file(path, outfile, end_session=True)
Read the file at path on the device and write it to outfile.
Parameters outfile – file object like sys.stdout or the result of an open() (page 239)
call.
classmethod config_widget()
Should return a QWidget. The QWidget contains the settings for the device interface
classmethod save_settings(settings_widget)
Should save settings to disk. Takes the widget created in config_widget() (page 242) and saves all
settings to disk.
classmethod settings()
Should return an opts object. The opts object should have at least one attribute format_map which is an
ordered list of formats for the device.
set_plugboards(plugboards, pb_func)
provide the driver the current set of plugboards and a function to select a specific plugboard. This method
is called immediately before add_books and sync_booklists.
pb_func is a callable with the following signature:: def pb_func(device_name, format, plugboards)
You give it the current device name (either the class name or DEVICE_PLUGBOARD_NAME), the for-
mat you are interested in (a ‘real’ format or ‘device_db’), and the plugboards (you were given those by
set_plugboards, the same place you got this method).
Returns None or a single plugboard instance.
set_driveinfo_name(location_code, name)
Set the device name in the driveinfo file to ‘name’. This setting will persist until the file is re-created or
the name is changed again.
Non-disk devices should implement this method based on the location codes returned by the
get_device_information() method.
prepare_addable_books(paths)
Given a list of paths, returns another list of paths. These paths point to addable versions of the books.
If there is an error preparing a book, then instead of a path, the position in the returned list for that book
should be a three tuple: (original_path, the exception instance, traceback)
startup()
Called when calibre is starting the device. Do any initialization required. Note that multiple instances of
the class can be instantiated, and thus __init__ can be called multiple times, but only one instance will
have this method called. This method is called on the device thread, not the GUI thread.
shutdown()
Called when calibre is shutting down, either for good or in preparation to restart. Do any cleanup required.
This method is called on the device thread, not the GUI thread.
get_device_uid()
Must return a unique id for the currently connected device (this is called immediately after a successful
call to open()). You must implement this method if you set ASK_TO_ALLOW_CONNECT = True
ignore_connected_device(uid)
Should ignore the device identified by uid (the result of a call to get_device_uid()) in the future. You must
implement this method if you set ASK_TO_ALLOW_CONNECT = True. Note that this function is called
immediately after open(), so if open() caches some state, the driver should reset that state.
get_user_blacklisted_devices()
Return map of device uid to friendly name for all devices that the user has asked to be ignored.
set_user_blacklisted_devices(devices)
Set the list of device uids that should be ignored by this driver.
specialize_global_preferences(device_prefs)
Implement this method if your device wants to override a particular preference. You must ensure that
all call sites that want a preference that can be overridden use device_prefs[‘something’] instead of
prefs[‘something’]. Your method should call device_prefs.set_overrides(pref=val, pref=val, . . . ). Cur-
rently used for: metadata management (prefs[‘manage_device_metadata’])
set_library_info(library_name, library_uuid, field_metadata)
Implement this method if you want information about the current calibre library. This method is called at
startup and when the calibre library changes while connected.
is_dynamically_controllable()
Called by the device manager when starting plugins. If this method returns a string, then a) it supports the
device manager’s dynamic control interface, and b) that name is to be used when talking to the plugin.
This method can be called on the GUI thread. A driver that implements this method must be thread safe.
start_plugin()
This method is called to start the plugin. The plugin should begin to accept device connections however it
does that. If the plugin is already accepting connections, then do nothing.
This method can be called on the GUI thread. A driver that implements this method must be thread safe.
stop_plugin()
This method is called to stop the plugin. The plugin should no longer accept connections, and should
cleanup behind itself. It is likely that this method should call shutdown. If the plugin is already not
accepting connections, then do nothing.
This method can be called on the GUI thread. A driver that implements this method must be thread safe.
get_option(opt_string, default=None)
Return the value of the option indicated by opt_string. This method can be called when the plugin is not
started. Return None if the option does not exist.
This method can be called on the GUI thread. A driver that implements this method must be thread safe.
set_option(opt_string, opt_value)
Set the value of the option indicated by opt_string. This method can be called when the plugin is not
started.
This method can be called on the GUI thread. A driver that implements this method must be thread safe.
is_running()
Return True if the plugin is started, otherwise false
This method can be called on the GUI thread. A driver that implements this method must be thread safe.
synchronize_with_db(db, book_id, book_metadata, first_call)
Called during book matching when a book on the device is matched with a book in calibre’s db. The
method is responsible for syncronizing data from the device to calibre’s db (if needed).
The method must return a two-value tuple. The first value is a set of calibre book ids changed if calibre’s
database was changed or None if the database was not changed. If the first value is an empty set then the
metadata for the book on the device is updated with calibre’s metadata and given back to the device, but
no GUI refresh of that book is done. This is useful when the calibre data is correct but must be sent to the
device.
The second value is itself a 2-value tuple. The first value in the tuple specifies whether a book format
should be sent to the device. The intent is to permit verifying that the book on the device is the same as the
book in calibre. This value must be None if no book is to be sent, otherwise return the base file name on
the device (a string like foobar.epub). Be sure to include the extension in the name. The device subsystem
will construct a send_books job for all books with not- None returned values. Note: other than to later
retrieve the extension, the name is ignored in cases where the device uses a template to generate the file
name, which most do. The second value in the returned tuple indicated whether the format is future-dated.
Return True if it is, otherwise return False. calibre will display a dialog to the user listing all future dated
books.
Extremely important: this method is called on the GUI thread. It must be threadsafe with respect to the
device manager’s thread.
book_id: the calibre id for the book in the database. book_metadata: the Metadata object for the book
coming from the device. first_call: True if this is the first call during a sync, False otherwise
class calibre.devices.interface.BookList(oncard, prefix, settings)
Bases: list
A list of books. Each Book object must have the fields
1. title
2. authors
3. size (file size of the book)
4. datetime (a UTC time tuple)
5. path (path on the device to the book)
6. thumbnail (can be None) thumbnail is either a str/bytes object with the image data or it should have an
attribute image_path that stores an absolute (platform native) path to the image
7. tags (a list of strings, can be empty).
supports_collections()
Return True if the device supports collections for this book list.
add_book(book, replace_metadata)
Add the book to the booklist. Intent is to maintain any device-internal metadata. Return True if booklists
must be sync’ed
remove_book(book)
Remove a book from the booklist. Correct any device metadata at the same time
get_collections(collection_attributes)
Return a dictionary of collections created from collection_attributes. Each entry in the dictionary is of the
form collection name:[list of books]
The list of books is sorted by book title, except for collections created from series, in which case se-
ries_index is used.
Parameters collection_attributes – A list of attributes of the Book object
The base class for such devices is calibre.devices.usbms.driver.USBMS (page 246). This class in turn
inherits some of its functionality from its bases, documented below. A typical basic USBMS based driver looks like
this:
class PDNOVEL(USBMS):
name = 'Pandigital Novel device interface'
gui_name = 'PD Novel'
description = _('Communicate with the Pandigital Novel')
author = 'Kovid Goyal'
supported_platforms = ['windows', 'linux', 'osx']
FORMATS = ['epub', 'pdf']
VENDOR_ID = [0x18d1]
PRODUCT_ID = [0xb004]
BCD = [0x224]
THUMBNAIL_HEIGHT = 144
EBOOK_DIR_MAIN = 'eBooks'
SUPPORTS_SUB_DIRS = False
class calibre.devices.usbms.device.Device(plugin_path)
Bases: calibre.devices.usbms.deviceconfig.DeviceConfig, calibre.devices.
interface.DevicePlugin (page 237)
This class provides logic common to all drivers for devices that export themselves as USB Mass Storage devices.
Provides implementations for mounting/ejecting of USBMS devices on all platforms.
WINDOWS_MAIN_MEM = None
String identifying the main memory of the device in the Windows PnP id strings This can be None, string,
list of strings or compiled regex
WINDOWS_CARD_A_MEM = None
String identifying the first card of the device in the Windows PnP id strings This can be None, string, list
of strings or compiled regex
WINDOWS_CARD_B_MEM = None
String identifying the second card of the device in the Windows PnP id strings This can be None, string,
list of strings or compiled regex
OSX_MAIN_MEM_VOL_PAT = None
Used by the new driver detection to disambiguate main memory from storage cards. Should be a regular
expression that matches the main memory mount point assigned by macOS
MAX_PATH_LEN = 250
The maximum length of paths created on the device
NEWS_IN_FOLDER = True
Put news in its own folder
windows_sort_drives(drives)
Called to disambiguate main memory and storage card for devices that do not distinguish between them
on the basis of WINDOWS_CARD_NAME. For e.g.: The EB600
sanitize_callback(path)
Callback to allow individual device drivers to override the path sanitization used by
create_upload_path().
filename_callback(default, mi)
Callback to allow drivers to change the default file name set by create_upload_path().
sanitize_path_components(components)
Perform any device specific sanitization on the path components for files to be uploaded to the device
get_annotations(path_map)
Resolve path_map to annotation_map of files found on the device
add_annotation_to_library(db, db_id, annotation)
Add an annotation to the calibre library
class calibre.devices.usbms.cli.CLI
class calibre.devices.usbms.driver.USBMS(plugin_path)
Bases: calibre.devices.usbms.cli.CLI (page 246), calibre.devices.usbms.device.
Device (page 245)
The base class for all USBMS devices. Implements the logic for sending/getting/updating metadata/caching
metadata/etc.
upload_cover(path, filename, metadata, filepath)
Upload book cover to the device. Default implementation does nothing.
Parameters
• path – The full path to the directory where the associated book is located.
• filename – The name of the book file without the extension.
• metadata – metadata belonging to the book. Use metadata.thumbnail for cover
• filepath – The full path to the e-book file
classmethod normalize_path(path)
Return path with platform native path separators
If you are adding your own plugin in a ZIP file, you should subclass both InterfaceActionBase and InterfaceAction.
The load_actual_plugin() method of your InterfaceActionBase subclass must return an instantiated object of
your InterfaceBase subclass.
class calibre.gui2.actions.InterfaceAction(parent, site_customization)
Bases: PyQt5.QtCore.QObject
A plugin representing an “action” that can be taken in the graphical user interface. All the items in the toolbar
and context menus are implemented by these plugins.
Note that this class is the base class for these plugins, however, to integrate the plugin with calibre’s plugin
system, you have to make a wrapper class that references the actual plugin. See the calibre.customize.
builtins module for examples.
If two InterfaceAction (page 246) objects have the same name, the one with higher priority takes prece-
dence.
self.gui.iactions['Save To Disk']
To access the actual plugin, use the interface_action_base_plugin attribute, this attribute only be-
comes available after the plugin has been initialized. Useful if you want to use methods from the plugin class
like do_user_config().
The QAction specified by action_spec (page 247) is automatically create and made available as self.
qaction.
name = u'Implement me'
The plugin name. If two plugins with the same name are present, the one with higher priority takes
precedence.
priority = 1
The plugin priority. If two plugins with the same name are present, the one with higher priority takes
precedence.
popup_type = 1
The menu popup type for when this plugin is added to a toolbar
auto_repeat = False
Whether this action should be auto repeated when its shortcut key is held down.
action_spec = (u'text', u'icon', None, None)
Of the form: (text, icon_path, tooltip, keyboard shortcut) icon, tooltip and keyboard shortcut can be None
shortcut must be a string, None or tuple of shortcuts. If None, a keyboard shortcut corresponding to the
action is not registered. If you pass an empty tuple, then the shortcut is registered with no default key
binding.
action_add_menu = False
If True, a menu is automatically created and added to self.qaction
action_menu_clone_qaction = False
If True, a clone of self.qaction is added to the menu of self.qaction If you want the text of this action to be
different from that of self.qaction, set this variable to the new text
dont_add_to = frozenset([])
Set of locations to which this action must not be added. See all_locations for a list of possible
locations
dont_remove_from = frozenset([])
Set of locations from which this action must not be removed. See all_locations for a list of possible
locations
action_type = u'global'
Type of action ‘current’ means acts on the current view ‘global’ means an action that does not act on the
current view, but rather on calibre as a whole
accepts_drops = False
If True, then this InterfaceAction will have the opportunity to interact with drag and drop events. See the
methods, accept_enter_event() (page 247), :meth‘:accept_drag_move_event‘, drop_event()
(page 248) for details.
accept_enter_event(event, mime_data)
This method should return True iff this interface action is capable of handling the drag event. Do not call
accept/ignore on the event, that will be taken care of by the calibre UI.
accept_drag_move_event(event, mime_data)
This method should return True iff this interface action is capable of handling the drag event. Do not call
accept/ignore on the event, that will be taken care of by the calibre UI.
drop_event(event, mime_data)
This method should perform some useful action and return True iff this interface action is capable of
handling the drop event. Do not call accept/ignore on the event, that will be taken care of by the cali-
bre UI. You should not perform blocking/long operations in this function. Instead emit a signal or use
QTimer.singleShot and return quickly. See the builtin actions for examples.
create_menu_action(menu, unique_name, text, icon=None, shortcut=None, description=None,
triggered=None, shortcut_name=None)
Convenience method to easily add actions to a QMenu. Returns the created QAction. This action has one
extra attribute calibre_shortcut_unique_name which if not None refers to the unique name under which
this action is registered with the keyboard manager.
Parameters
• menu – The QMenu the newly created action will be added to
• unique_name – A unique name for this action, this must be globally unique, so make it
as descriptive as possible. If in doubt, add an UUID to it.
• text – The text of the action.
• icon – Either a QIcon or a file name. The file name is passed to the I() builtin, so you do
not need to pass the full path to the images directory.
• shortcut – A string, a list of strings, None or False. If False, no keyboard shortcut
is registered for this action. If None, a keyboard shortcut with no default keybinding is
registered. String and list of strings register a shortcut with default keybinding as specified.
• description – A description for this action. Used to set tooltips.
• triggered – A callable which is connected to the triggered signal of the created action.
• shortcut_name – The text displayed to the user when customizing the keyboard short-
cuts for this action. By default it is set to the value of text.
load_resources(names)
If this plugin comes in a ZIP file (user added plugin), this method will allow you to load resources from
the ZIP file.
For example to load an image:
pixmap = QPixmap()
pixmap.loadFromData(tuple(self.load_resources(['images/icon.png']).
˓→values())[0])
icon = QIcon(pixmap)
Parameters names – List of paths to resources in the ZIP file using / as separator
Returns A dictionary of the form {name : file_contents}. Any names that were not
found in the ZIP file will not be present in the dictionary.
genesis()
Setup this plugin. Only called once during initialization. self.gui is available. The action specified by
action_spec (page 247) is available as self.qaction.
location_selected(loc)
Called whenever the book list being displayed in calibre changes. Currently values for loc are: library,
main, card and cardb.
This method should enable/disable this action and its sub actions as appropriate for the location.
library_changed(db)
Called whenever the current library is changed.
Parameters db – The LibraryDatabase corresponding to the current library.
gui_layout_complete()
Called once per action when the layout of the main GUI is completed. If your action needs to make changes
to the layout, they should be done here, rather than in initialization_complete() (page 249).
initialization_complete()
Called once per action when the initialization of the main GUI is completed.
shutting_down()
Called once per plugin when the main GUI is in the process of shutting down. Release any used resources,
but try not to block the shutdown for long periods of time.
class calibre.customize.InterfaceActionBase(*args, **kwargs)
Bases: calibre.customize.Plugin (page 228)
load_actual_plugin(gui)
This method must return the actual interface action plugin object.
class calibre.customize.PreferencesPlugin(plugin_path)
Bases: calibre.customize.Plugin (page 228)
A plugin representing a widget displayed in the Preferences dialog.
This plugin has only one important method create_widget() (page 249). The various fields of the plugin
control how it is categorized in the UI.
config_widget = None
Import path to module that contains a class named ConfigWidget which implements the ConfigWidget-
Interface. Used by create_widget() (page 249).
category_order = 100
Where in the list of categories the category (page 249) of this plugin should be.
name_order = 100
Where in the list of names in a category, the gui_name (page 249) of this plugin should be
category = None
The category this plugin should be in
gui_category = None
The category name displayed to the user for this plugin
gui_name = None
The name displayed to the user for this plugin
icon = None
The icon for this plugin, should be an absolute path
description = None
The description used for tooltips and the like
create_widget(parent=None)
Create and return the actual Qt widget used for setting this group of preferences. The widget must imple-
ment the calibre.gui2.preferences.ConfigWidgetInterface (page 250).
The default implementation uses config_widget (page 249) to instantiate the widget.
class calibre.gui2.preferences.ConfigWidgetInterface
This class defines the interface that all widgets displayed in the Preferences dialog must implement. See
ConfigWidgetBase (page 250) for a base class that implements this interface and defines various con-
venience methods as well.
changed_signal = None
This signal must be emitted whenever the user changes a value in this widget
supports_restoring_to_defaults = True
Set to True iff the restore_to_defaults() method is implemented.
restore_defaults_desc = u'Restore settings to default values. You have to click Apply t
The tooltip for the “Restore defaults” button
restart_critical = False
If True the Preferences dialog will not allow the user to set any more preferences. Only has effect if
commit() (page 250) returns True.
genesis(gui)
Called once before the widget is displayed, should perform any necessary setup.
Parameters gui – The main calibre graphical user interface
initialize()
Should set all config values to their initial values (the values stored in the config files).
restore_defaults()
Should set all config values to their defaults.
commit()
Save any changed settings. Return True if the changes require a restart, False otherwise. Raise an
AbortCommit exception to indicate that an error occurred. You are responsible for giving the user
feedback about what the error is and how to correct it.
refresh_gui(gui)
Called once after this widget is committed. Responsible for causing the gui to reread any changed settings.
Note that by default the GUI re-initializes various elements anyway, so most widgets won’t need to use
this method.
class calibre.gui2.preferences.ConfigWidgetBase(parent=None)
Base class that contains code to easily add standard config widgets like checkboxes, combo boxes, text fields
and so on. See the register() (page 250) method.
This class automatically handles change notification, resetting to default, translation between gui objects and
config objects, etc. for registered settings.
If your config widget inherits from this class but includes setting that are not registered, you should override the
ConfigWidgetInterface (page 250) methods and call the base class methods inside the overrides.
register(name, config_obj, gui_name=None, choices=None, restart_required=False,
empty_string_is_None=True, setting=<class ’calibre.gui2.preferences.Setting’>)
Register a setting.
Parameters
• name – The setting name
• config – The config object that reads/writes the setting
• gui_name – The name of the GUI object that presents an interface to change the setting.
By default it is assumed to be 'opt_' + name.
• choices – If this setting is a multiple choice (combobox) based setting, the list of
choices. The list is a list of two element tuples of the form: [(gui name, value),
...]
• setting – The class responsible for managing this setting. The default class handles
almost all cases, so this param is rarely used.
CALIBRE_DEVELOP_FROM=$HOME/calibre-src/src
CALIBRE_NO_NATIVE_FILEDIALOGS=1
CALIBRE_CONFIG_DIRECTORY=~/.config/calibre
11.3 Tweaks
Tweaks are small changes that you can specify to control various aspects of calibre’s behavior. You can change them
by going to Preferences->Advanced->Tweaks. The default values for the tweaks are reproduced below
#!/usr/bin/env python2
# vim:fileencoding=UTF-8:ts=4:sw=4:sta:et:sts=4:ai
# License: GPLv3 Copyright: 2010, Kovid Goyal <kovid at kovidgoyal.net>
from __future__ import unicode_literals
# Contains various tweaks that affect calibre behavior. Only edit this file if
# you know what you are doing. If you delete this file, it will be recreated from
# defaults.
# Examples:
# series_index_auto_increment = 'next'
# series_index_auto_increment = 'next_free'
# series_index_auto_increment = 16.5
#
# Set the use_series_auto_increment_tweak_when_importing tweak to True to
# use the above values when importing/adding books. If this tweak is set to
# False (the default) then the series number will be set to 1 if it is not
# explicitly set during the import. If set to True, then the
# series index will be set according to the series_index_auto_increment setting.
# Note that the use_series_auto_increment_tweak_when_importing tweak is used
# only when a value is not provided during import. If the importing regular
# expression produces a value for series_index, or if you are reading metadata
# from books and the import plugin produces a value, than that value will
# be used irrespective of the setting of the tweak.
series_index_auto_increment = 'next'
use_series_auto_increment_tweak_when_importing = False
# AP use a 12-hour clock instead of a 24-hour clock, with "AP" replaced by the
˓→localized string for AM or PM
# iso the date with time and timezone. Must be the only format present
# For example, given the date of 9 Jan 2010, the following formats show
# MMM yyyy ==> Jan 2010 yyyy ==> 2010 dd MMM yyyy ==> 09 Jan 2010
# MM/yyyy ==> 01/2010 d/M/yy ==> 9/1/10 yy ==> 10
#
# publication default if not set: MMM yyyy
# timestamp default if not set: dd MMM yyyy
# last_modified_display_format if not set: dd MMM yyyy
gui_pubdate_display_format = 'MMM yyyy'
gui_timestamp_display_format = 'dd MMM yyyy'
gui_last_modified_display_format = 'dd MMM yyyy'
#: Control how tags are applied when copying books to another library
# Set this to True to ensure that tags in 'Tags to add when adding
# a book' are added when copying books to another library
add_new_book_tags_when_importing_books = False
#: The maximum width and height for covers saved in the calibre library
# All covers in the calibre library will be resized, preserving aspect ratio,
# to fit within this size. This is to prevent slowdowns caused by extremely
# large covers
maximum_cover_size = (1650, 2200)
#: Save original file when converting/polishing from same format to same format
# When calibre does a conversion from the same format to the same format, for
# example, from EPUB to EPUB, the original file is saved, so that in case the
# conversion is poor, you can tweak the settings and run it again. By setting
# this to False you can prevent calibre from saving the original file.
# Similarly, by setting save_original_format_when_polishing to False you can
# prevent calibre from saving the original file when polishing.
save_original_format = True
save_original_format_when_polishing = True
#: Image file types to treat as e-books when dropping onto the "Book details" panel
# Normally, if you drop any image file in a format known to calibre onto the
# "Book details" panel, it will be used to set the cover. If you want to store
# some image types as e-books instead, you can set this tweak.
# Examples:
# cover_drop_exclude = {'tiff', 'webp'}
cover_drop_exclude = ()
Note: calibre has direct support for icon themes, there are several icon themes available for calibre, that you can use
by going to Preferences→Interface→Look & Feel→Change Icon theme. The icon themes use the same mechanism
as described below for overriding static resources.
calibre allows you to override the static resources, like icons, JavaScript and templates for the metadata jacket, catalogs,
etc. with customized versions that you like. All static resources are stored in the resources sub-folder of the calibre
install location. On Windows, this is usually C:\Program Files\Calibre2\app\resources. On macOS,
/Applications/calibre.app/Contents/Resources/resources/. On Linux, if you are using the
binary installer from the calibre website it will be /opt/calibre/resources. These paths can change depending
on where you choose to install calibre.
You should not change the files in this resources folder, as your changes will get overwritten the next time you update
calibre. Instead, go to Preferences→Advanced→Miscellaneous and click Open calibre configuration directory. In this
configuration directory, create a sub-folder called resources and place the files you want to override in it. Place the files
in the appropriate sub folders, for example place images in resources/images, etc. calibre will automatically use
your custom file in preference to the built-in one the next time it is started.
For example, if you wanted to change the icon for the Remove books action, you would first look in the built-in
resources folder and see that the relevant file is resources/images/remove_books.png. Assuming you have
an alternate icon in PNG format called my_remove_books.png you would save it in the configuration directory as
resources/images/remove_books.png. All the icons used by the calibre user interface are in resources/
images and its sub-folders.
If you have created a beautiful set of icons and wish to share them with other calibre users via cali-
bre’s builtin icon theme support, you can easily package up your icons into a theme. To do so, go to
Preferences→Miscellaneous→Create icon theme, select the folder where you have put your icons (usually the
resources/images folder in the calibre config directory, as described above). Then fill up the theme metadata
and click OK. This will result in a ZIP file containing the theme icons. You can upload that to the calibre forum at
Mobileread99 and then I will make your theme available via calibre’s builtin icon theme system.
calibre has a very modular design. Almost all functionality in calibre comes in the form of plugins. Plugins are used
for conversion, for downloading news (though these are called recipes), for various components of the user interface,
to connect to different devices, to process files when adding them to calibre and so on. You can get a complete list of
all the built-in plugins in calibre by going to Preferences→Advanced→Plugins.
You can write your own plugins to customize and extend the behavior of calibre. The plugin architecture in calibre is
very simple, see the tutorial Writing your own plugins to extend calibre’s functionality (page 202).
99 https://www.mobileread.com/forums/forumdisplay.php?f=166
Note: On macOS, the command line tools are inside the calibre bundle, for example, if you installed calibre in
/Applications the command line tools are in /Applications/calibre.app/Contents/MacOS/.
12.1.1 calibre
Launch the main calibre Graphical User Interface and optionally add the e-book at path_to_ebook to the database.
Whenever you pass arguments to calibre that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
[options]
--detach
Detach from the controlling terminal, if any (Linux only)
--help, -h
show this help message and exit
--ignore-plugins
Ignore custom plugins, useful if you installed a plugin that is preventing calibre from starting
--no-update-check
Do not check for updates
263
calibre User Manual, Release 4.21.0
--shutdown-running-calibre, -s
Cause a running calibre instance, if any, to be shutdown. Note that if there are running jobs, they will be silently
aborted, so use with care.
--start-in-tray
Start minimized to system tray.
--verbose, -v
Ignored, do not use. Present only for legacy reasons
--version
show program's version number and exit
--with-library
Use the library located at the specified path.
12.1.2 calibre-customize
calibre-customize options
[options]
--add-plugin, -a
Add a plugin by specifying the path to the ZIP file containing it.
--build-plugin, -b
For plugin developers: Path to the directory where you are developing the plugin. This command will automat-
ically zip up the plugin and update it in calibre.
--customize-plugin
Customize plugin. Specify name of plugin and customization string separated by a comma.
--disable-plugin
Disable the named plugin
--enable-plugin
Enable the named plugin
--help, -h
show this help message and exit
--list-plugins, -l
List all installed plugins
--remove-plugin, -r
Remove a custom plugin by name. Has no effect on builtin plugins
--version
show program's version number and exit
12.1.3 calibre-debug
calibre-debug [options]
Various command line interfaces useful for debugging calibre. With no options, this command starts an embedded
Python interpreter. You can also run the main calibre GUI, the calibre viewer and the calibre editor in debug mode.
It also contains interfaces to various bits of calibre that do not have dedicated command line tools, such as font
subsetting, the E-book diff tool and so on.
You can also use calibre-debug to run standalone scripts. To do that use it like this:
calibre-debug myscript.py -- --option1 --option2 file1 file2 . . .
Everything after the -- is passed to the script.
Whenever you pass arguments to calibre-debug that have spaces in them, enclose the arguments in quotation
marks. For example: “/some path/with spaces”
[options]
--add-simple-plugin
Add a simple plugin (i.e. a plugin that consists of only a .py file), by specifying the path to the py file containing
the plugin code.
--command, -c
Run Python code.
--debug-device-driver, -d
Debug device detection
--default-programs
(Un)register calibre from Windows Default Programs. --default-programs (page 265) =
(register|unregister)
--diff
Run the calibre diff tool. For example: calibre-debug --diff (page 265) file1 file2
--edit-book, -t
Launch the calibre "Edit book" tool in debug mode.
--exec-file, -e
Run the Python code in file.
--explode-book, -x
Explode the book into the specified directory. 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. Works with EPUB, AZW3,
HTMLZ and DOCX files.
--export-all-calibre-data
Export all calibre data (books/settings/plugins). Normally, you will be asked for the export dir and the libraries
to export. You can also specify them as command line arguments to skip the questions. Use absolute paths for
the export directory and libraries. The special keyword "all" can be used to export all libraries.
--gui, -g
Run the GUI with debugging enabled. Debug output is printed to stdout and stderr.
--gui-debug
Run the GUI with a debug console, logging to the specified path. For internal use only, use the -g option to run
the GUI in debug mode
--help, -h
show this help message and exit
--implode-book, -i
Implode a previously exploded book. Usage: -i output_dir file.epub Imports the book from the files in output_dir
which must have been created by a previous call to --explode-book (page 265). Be sure to specify the same
file type as was used when exploding.
--import-calibre-data
Import previously exported calibre data
--inspect-mobi, -m
Inspect the MOBI file(s) at the specified path(s)
--paths
Output the paths necessary to setup the calibre environment
--reinitialize-db
Re-initialize the sqlite calibre database at the specified path. Useful to recover from db corruption.
--run-plugin, -r
Run a plugin that provides a command line interface. For example: calibre-debug -r "Add Books" -- file1
--option1 Everything after the -- will be passed to the plugin as arguments.
--shutdown-running-calibre, -s
Cause a running calibre instance, if any, to be shutdown. Note that if there are running jobs, they will be silently
aborted, so use with care.
--subset-font, -f
Subset the specified font. Use -- after this option to pass option to the font subsetting program.
--test-build
Test binary modules in build
--version
show program's version number and exit
--viewer, -w
Run the E-book viewer in debug mode
12.1.4 calibre-server
Start the calibre Content server. The calibre Content server exposes your calibre libraries over the internet. You can
specify the path to the library folders as arguments to calibre-server. If you do not specify any paths, all the
libraries that the main calibre program knows about will be used.
Whenever you pass arguments to calibre-server that have spaces in them, enclose the arguments in quotation
marks. For example: “/some path/with spaces”
[options]
--access-log
Path to the access log file. This log contains information about clients connecting to the server and making
requests. By default no access logging is done.
--ajax-timeout
Time (in seconds) to wait for a response from the server when making queries.
--auth-mode
Choose the type of authentication used. Set the HTTP authentication mode used by the server. Set to "basic" if
you are putting this server behind an SSL proxy. Otherwise, leave it as "auto", which will use "basic" if SSL
is configured otherwise it will use "digest".
--auto-reload
Automatically reload server when source code changes. Useful for development. You should also specify a
small value for the shutdown timeout.
--ban-after
Number of login failures for ban. The number of login failures after which an IP address is banned
--ban-for
Ban IP addresses that have repeated login failures. Temporarily bans access for IP addresses that have repeated
login failures for the specified number of minutes. Useful to prevent attempts at guessing passwords. If set to
zero, no banning is done.
--book-list-mode
Choose the default book list mode. Set the default book list mode that will be used for new users. Individual
users can override the default in their own settings. The default is to use a cover grid.
--compress-min-size
Minimum size for which responses use data compression (in bytes).
--custom-list-template
Path to a JSON file containing a template for the custom book list mode. The easiest way to create such a
template file is to go to Preferences-> Sharing over the net-> Book list template in calibre, create the template
and export it.
--daemonize
Run process in background as a daemon (Linux only).
--displayed-fields
Restrict displayed user-defined fields. Comma separated list of user-defined metadata fields that will be dis-
played by the Content server in the /opds and /mobile views. If you specify this option, any fields not in this list
will not be displayed. For example: my_rating,my_tags
--enable-allow-socket-preallocation, --disable-allow-socket-preallocation
Socket pre-allocation, for example, with systemd socket activation. By default, this option is enabled.
--enable-auth, --disable-auth
Password based authentication to access the server. Normally, the server is unrestricted, allowing anyone to
access it. You can restrict access to predefined users with this option. By default, this option is disabled.
--enable-fallback-to-detected-interface, --disable-fallback-to-detected-interface
Fallback to auto-detected interface. If for some reason the server is unable to bind to the interface specified in
the listen_on option, then it will try to detect an interface that connects to the outside world and bind to that. By
default, this option is enabled.
--enable-local-write, --disable-local-write
Allow un-authenticated local connections to make changes. Normally, if you do not turn on authentication, the
server operates in read-only mode, so as to not allow anonymous users to make changes to your calibre libraries.
This option allows anybody connecting from the same computer as the server is running on to make changes.
This is useful if you want to run the server without authentication but still use calibredb to make changes to
your calibre libraries. Note that turning on this option means any program running on the computer can make
changes to your calibre libraries. By default, this option is disabled.
--enable-log-not-found, --disable-log-not-found
Log HTTP 404 (Not Found) requests. Normally, the server logs all HTTP requests for resources that are not
found. This can generate a lot of log spam, if your server is targeted by bots. Use this option to turn it off. By
default, this option is enabled.
--enable-use-bonjour, --disable-use-bonjour
Advertise OPDS feeds via BonJour. Advertise the OPDS feeds via the BonJour service, so that OPDS based
reading apps can detect and connect to the server automatically. By default, this option is enabled.
--enable-use-sendfile, --disable-use-sendfile
Zero copy file transfers for increased performance. This will use zero-copy in-kernel transfers when sending
files over the network, increasing performance. However, it can cause corrupted file transfers on some broken
filesystems. If you experience corrupted file transfers, turn it off. By default, this option is enabled.
--help, -h
show this help message and exit
--ignored-fields
Ignored user-defined metadata fields. Comma separated list of user-defined metadata fields that will not be
displayed by the Content server in the /opds and /mobile views. For example: my_rating,my_tags
--listen-on
The interface on which to listen for connections. The default is to listen on all available IPv4 interfaces. You
can change this to, for example, "127.0.0.1" to only listen for connections from the local machine, or to "::" to
listen to all incoming IPv6 and IPv4 connections.
--log
Path to log file for server log. This log contains server information and errors, not access logs. By default it is
written to stdout.
--manage-users
Manage the database of users allowed to connect to this server. See also the --userdb (page 269) option.
--max-header-line-size
Max. size of single HTTP header (in KB).
--max-job-time
Maximum time for worker processes. Maximum amount of time worker processes are allowed to run (in min-
utes). Set to zero for no limit.
--max-jobs
Maximum number of worker processes. Worker processes are launched as needed and used for large jobs such
as preparing a book for viewing, adding books, converting, etc. Normally, the max. number of such processes
is based on the number of CPU cores. You can control it by this setting.
--max-log-size
Max. log file size (in MB). The maximum size of log files, generated by the server. When the log becomes
larger than this size, it is automatically rotated. Set to zero to disable log rotation.
--max-opds-items
Maximum number of books in OPDS feeds. The maximum number of books that the server will return in a
single OPDS acquisition feed.
--max-opds-ungrouped-items
Maximum number of ungrouped items in OPDS feeds. Group items in categories such as author/tags by first
letter when there are more than this number of items. Set to zero to disable.
--max-request-body-size
Max. allowed size for files uploaded to the server (in MB).
--num-per-page
Number of books to show in a single page. The number of books to show in a single page in the browser.
--pidfile
Write process PID to the specified file
--port
The port on which to listen for connections.
--search-the-net-urls
Path to a JSON file containing URLs for the "Search the internet" feature. The easiest way to create such a file
is to go to Preferences-> Sharing over the net->Search the internet in calibre, create the URLs and export them.
--shutdown-timeout
Total time in seconds to wait for clean shutdown.
--ssl-certfile
Path to the SSL certificate file.
--ssl-keyfile
Path to the SSL private key file.
--timeout
Time (in seconds) after which an idle connection is closed.
--trusted-ips
Allow un-authenticated connections from specific IP addresses to make changes. Normally, if you do not turn
on authentication, the server operates in read-only mode, so as to not allow anonymous users to make changes to
your calibre libraries. This option allows anybody connecting from the specified IP addresses to make changes.
Must be a comma separated list of address or network specifications. This is useful if you want to run the server
without authentication but still use calibredb to make changes to your calibre libraries. Note that turning on this
option means anyone connecting from the specified IP addresses can make changes to your calibre libraries.
--url-prefix
A prefix to prepend to all URLs. Useful if you wish to run this server behind a reverse proxy. For example use,
/calibre as the URL prefix.
--userdb
Path to the user database to use for authentication. The database is a SQLite file. To create it use
--manage-users (page 268). You can read more about managing users at: https://manual.calibre-ebook.
com/server.html#managing-user-accounts-from-the-command-line-only
--version
show program's version number and exit
--worker-count
Number of worker threads used to process requests.
12.1.5 calibre-smtp
Send mail using the SMTP protocol. calibre-smtp has two modes of operation. In the compose mode you specify
from to and text and these are used to build and send an email message. In the filter mode, calibre-smtp reads a
complete email message from STDIN and sends it.
text is the body of the email message. If text is not specified, a complete email message is read from STDIN. from
is the email address of the sender and to is the email address of the recipient. When a complete email is read from
STDIN, from and to are only used in the SMTP negotiation, the message headers are not modified.
Whenever you pass arguments to calibre-smtp that have spaces in them, enclose the arguments in quotation
marks. For example: “/some path/with spaces”
[options]
--fork, -f
Fork and deliver message in background. If you use this option, you should also use --outbox (page 270) to
handle delivery failures.
--help, -h
show this help message and exit
--localhost, -l
Host name of localhost. Used when connecting to SMTP server.
--outbox, -o
Path to maildir folder to store failed email messages in.
--timeout, -t
Timeout for connection
--verbose, -v
Be more verbose
--version
show program's version number and exit
COMPOSE MAIL
SMTP RELAY
Options to use an SMTP relay server to send mail. calibre will try to send the email directly unless –relay is specified.
--cafile
Path to a file of concatenated CA certificates in PEM format, used to verify the server certificate when using
TLS. By default, the system CA certificates are used.
--dont-verify-server-certificate
Do not verify the server certificate when connecting using TLS. This used to be the default behavior in calibre
versions before 3.27. If you are using a relay with a self-signed or otherwise invalid certificate, you can use this
option to restore the pre 3.27 behavior
--encryption-method, -e
Encryption method to use when connecting to relay. Choices are TLS, SSL and NONE. Default is TLS. WARN-
ING: Choosing NONE is highly insecure
--password, -p
Password for relay
--port
Port to connect to on relay server. Default is to use 465 if encryption method is SSL and 25 otherwise.
--relay, -r
An SMTP relay server to use to send mail.
--username, -u
Username for relay
12.1.6 calibredb
calibredb is the command line interface to the calibre database. It has several sub-commands, documented below.
calibredb can be used to manipulate either a calibre database specified by path or a calibre Content server
running either on the local machine or over the internet. You can start a calibre Content server using either the
calibre-server program or in the main calibre program click Connect/share → Start Content server. Since
calibredb can make changes to your calibre libraries, you must setup authentication on the server first. There are
two ways to do that:
• If you plan to connect only to a server running on the same computer, you can simply use the
--enable-local-write option of the content server, to allow any program, including calibredb, running
on the local computer to make changes to your calibre data. When running the server from the main calibre
program, this option is in Preferences→Sharing over the net→Advanced.
• If you want to enable access over the internet, then you should setup user accounts on the server and use
the --username (page 272) and --password (page 272) options to calibredb to give it access. You
can setup user authentication for calibre-server by using the --enable-auth option and using
--manage-users to create the user accounts. If you are running the server from the main calibre program,
use Preferences→Sharing over the net→Require username/password.
To connect to a running Content server, pass the URL of the server to the --with-library (page 272) option, see
the documentation of that option for details and examples.
Global Options
--help, -h
show this help message and exit
--library-path, --with-library
Path to the calibre library. Default is to use the path stored in the settings. You can also connect to a calibre
Content server to perform actions on remote libraries. To do so use a URL of the form: http://hostname:
port/#library_id for example, http://localhost:8080/#mylibrary. library_id is the library id of the library you
want to connect to on the Content server. You can use the special library_id value of - to get a list of library ids
available on the server. For details on how to setup access via a Content server, see https://manual.calibre-ebook.
com/generated/en/calibredb.html.
--password
Password for connecting to a calibre Content server. To read the password from standard input, use the special
value: <stdin>. To read the password from a file, use: <f:/path/to/file> (i.e. <f: followed by the full path to the
file and a trailing >). The angle brackets in the above are required, remember to escape them or use quotes for
your shell.
--username
Username for connecting to a calibre Content server
--version
show program's version number and exit
list
"all" can be used to select all fields. In addition to the builtin fields above, custom fields are also available as
*field_name, for example, for a custom field #rating, use the name: *rating
--for-machine
Generate output in JSON format, which is more suitable for machine parsing. Causes the line width and sepa-
rator options to be ignored.
--limit
The maximum number of results to display. Default: all
--line-width, -w
The maximum width of a single line in the output. Defaults to detecting screen size.
--prefix
The prefix for all file paths. Default is the absolute path to the library folder.
--search, -s
Filter the results by the search query. For the format of the search query, please see the search related documen-
tation in the User Manual. Default is to do no filtering.
--separator
The string used to separate fields. Default is a space.
--sort-by
The field by which to sort the results. Available fields: author_sort, authors, comments, cover, formats, identi-
fiers, isbn, languages, last_modified, pubdate, publisher, rating, series, series_index, size, tags, timestamp, title,
uuid Default: id
add
Add the specified files as books to the database. You can also specify directories, see the directory related options
below.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--authors, -a
Set the authors of the added book(s)
--cover, -c
Path to the cover to use for the added book
--duplicates, -d
Add books to database even if they already exist. Comparison is done based on book titles.
--empty, -e
Add an empty book (a book with no formats)
--identifier, -I
Set the identifiers for this book, for e.g. -I asin:XXX -I isbn:YYY
--isbn, -i
Set the ISBN of the added book(s)
--languages, -l
A comma separated list of languages (best to use ISO639 language codes, though some language names may
also be recognized)
--series, -s
Set the series of the added book(s)
--series-index, -S
Set the series number of the added book(s)
--tags, -T
Set the tags of the added book(s)
--title, -t
Set the title of the added book(s)
Options to control the adding of books from directories. By default only files that have extensions of known e-book
file types are added.
--add
A filename (glob) pattern, files matching this pattern will be added when scanning directories for files, even if
they are not of a known e-book file type. Can be specified multiple times for multiple patterns.
--ignore
A filename (glob) pattern, files matching this pattern will be ignored when scanning directories for files. Can be
specified multiple times for multiple patterns. For e.g.: *.pdf will ignore all pdf files
--one-book-per-directory, -1
Assume that each directory has only a single logical book and that all files in it are different e-book formats of
that book
--recurse, -r
Process directories recursively
remove
Remove the books identified by ids from the database. ids should be a comma separated list of id numbers (you can
get id numbers by using the search command). For example, 23,34,57-85 (when specifying a range, the last number
in the range is not included).
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--permanent
Do not use the recycle bin
add_format
Add the e-book in ebook_file to the available formats for the logical book identified by id. You can get id by using the
search command. If the format already exists, it is replaced, unless the do not replace option is specified.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--dont-replace
Do not replace the format if it already exists
remove_format
Remove the format fmt from the logical book identified by id. You can get id by using the search command. fmt
should be a file extension like LRF or TXT or EPUB. If the logical book does not have fmt available, do nothing.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
show_metadata
Show the metadata stored in the calibre database for the book identified by id. id is an id number from the search
command.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--as-opf
Print metadata in OPF form (XML)
set_metadata
Set the metadata stored in the calibre database for the book identified by id from the OPF file metadata.opf. id is an
id number from the search command. You can get a quick feel for the OPF format by using the –as-opf switch to the
show_metadata command. You can also set the metadata of individual fields with the –field option. If you use the
–field option, there is no need to specify an OPF file.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--field, -f
The field to set. Format is field_name:value, for example: --field (page 275) tags:tag1,tag2. Use
--list-fields (page 275) to get a list of all field names. You can specify this option multiple times to
set multiple fields. Note: For languages you must use the ISO639 language codes (e.g. en for English, fr for
French and so on). For identifiers, the syntax is --field (page 275) identifiers:isbn:XXXX,doi:YYYYY. For
boolean (yes/no) fields use true and false or yes and no.
--list-fields, -l
List the metadata field names that can be used with the --field (page 275) option
export
Export the books specified by ids (a comma separated list) to the filesystem. The export operation saves all formats
of the book, its cover and metadata (in an opf file). You can get id numbers from the search command.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--all
Export all books in database, ignoring the list of ids.
--dont-asciiize
Normally, calibre will convert all non English characters into English equivalents for the file names. WARNING:
If you turn this off, you may experience errors when saving, depending on how well the filesystem you are saving
to supports unicode. Specifying this switch will turn this behavior off.
--dont-save-cover
Normally, calibre will save the cover in a separate file along with the actual e-book files. Specifying this switch
will turn this behavior off.
--dont-update-metadata
Normally, calibre will update the metadata in the saved files from what is in the calibre library. Makes saving to
disk slower. Specifying this switch will turn this behavior off.
--dont-write-opf
Normally, calibre will write the metadata into a separate OPF file along with the actual e-book files. Specifying
this switch will turn this behavior off.
--formats
Comma separated list of formats to save for each book. By default all available formats are saved.
--progress
Report progress
--replace-whitespace
Replace whitespace with underscores.
--single-dir
Export all books into a single directory
--template
The template to control the filename and directory structure of the saved files. Default is
"{author_sort}/{title}/{title} - {authors}" which will save books into a per-author subdirectory with filenames
containing title and author. Available controls are: {author_sort, authors, id, isbn, languages, last_modified,
pubdate, publisher, rating, series, series_index, tags, timestamp, title}
--timefmt
The format in which to display dates. %d - day, %b - month, %m - month number, %Y - year. Default is: %b,
%Y
--to-dir
Export books to the specified directory. Default is .
--to-lowercase
Convert paths to lowercase.
catalog
Export a catalog in format specified by path/to/destination extension. Options control how entries are displayed in
the generated catalog output. Note that different catalog formats support different sets of options.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--ids, -i
Comma-separated list of database IDs to catalog. If declared, --search (page 277) is ignored. Default: all
--search, -s
Filter the results by the search query. For the format of the search query, please see the search-related documen-
tation in the User Manual. Default: no filtering
--verbose, -v
Show detailed output information. Useful for debugging
Epub Options
--catalog-title
Title of generated catalog used as title in metadata. Default: 'My Books' Applies to: AZW3, EPUB, MOBI
output formats
--cross-reference-authors
Create cross-references in Authors section for books with multiple authors. Default: 'False' Applies to:
AZW3, EPUB, MOBI output formats
--debug-pipeline
Save the output from different stages of the conversion pipeline to the specified directory. Useful if you are
unsure at which stage of the conversion process a bug is occurring. Default: 'None' Applies to: AZW3,
EPUB, MOBI output formats
--exclude-genre
Regex describing tags to exclude as genres. Default: '[.+]|^+$' excludes bracketed tags, e.g. '[Project Guten-
berg]', and '+', the default tag for read books. Applies to: AZW3, EPUB, MOBI output formats
--exclusion-rules
Specifies the rules used to exclude books from the generated catalog. The model for an exclusion rule
is either ('<rule name>','Tags','<comma-separated list of tags>') or ('<rule name>','<custom col-
umn>','<pattern>'). For example: (('Archived books','#status','Archived'),) will exclude a book with
a value of 'Archived' in the custom column 'status'. When multiple rules are defined, all rules will be ap-
plied. Default: "(('Catalogs','Tags','Catalog'),)" Applies to: AZW3, EPUB, MOBI output formats
--generate-authors
Include 'Authors' section in catalog. Default: 'False' Applies to: AZW3, EPUB, MOBI output formats
--generate-descriptions
Include 'Descriptions' section in catalog. Default: 'False' Applies to: AZW3, EPUB, MOBI output formats
--generate-genres
Include 'Genres' section in catalog. Default: 'False' Applies to: AZW3, EPUB, MOBI output formats
--generate-recently-added
Include 'Recently Added' section in catalog. Default: 'False' Applies to: AZW3, EPUB, MOBI output
formats
--generate-series
Include 'Series' section in catalog. Default: 'False' Applies to: AZW3, EPUB, MOBI output formats
--generate-titles
Include 'Titles' section in catalog. Default: 'False' Applies to: AZW3, EPUB, MOBI output formats
--genre-source-field
Source field for 'Genres' section. Default: 'Tags' Applies to: AZW3, EPUB, MOBI output formats
--header-note-source-field
Custom field containing note text to insert in Description header. Default: '' Applies to: AZW3, EPUB, MOBI
output formats
--merge-comments-rule
#<custom field>:[before|after]:[True|False] specifying: <custom field> Custom field containing notes to merge
with Comments [before|after] Placement of notes with respect to Comments [True|False] - A horizontal rule is
inserted between notes and Comments Default: '::' Applies to: AZW3, EPUB, MOBI output formats
--output-profile
Specifies the output profile. In some cases, an output profile is required to optimize the catalog for the device. For
example, 'kindle' or 'kindle_dx' creates a structured Table of Contents with Sections and Articles. Default:
'None' Applies to: AZW3, EPUB, MOBI output formats
--prefix-rules
Specifies the rules used to include prefixes indicating read books, wishlist items and other user-specified prefixes.
The model for a prefix rule is ('<rule name>','<source field>','<pattern>','<prefix>'). When multiple
rules are defined, the first matching rule will be used. Default: "(('Read books','tags','+','X'),('Wishlist
item','tags','Wishlist','×'))" Applies to: AZW3, EPUB, MOBI output formats
--preset
Use a named preset created with the GUI catalog builder. A preset specifies all settings for building a catalog.
Default: 'None' Applies to: AZW3, EPUB, MOBI output formats
--thumb-width
Size hint (in inches) for book covers in catalog. Range: 1.0 - 2.0 Default: '1.0' Applies to: AZW3, EPUB,
MOBI output formats
--use-existing-cover
Replace existing cover when generating the catalog. Default: 'False' Applies to: AZW3, EPUB, MOBI output
formats
saved_searches
Manage the saved searches stored in this database. If you try to add a query with a name that already exists, it will be
replaced.
Syntax for adding:
calibredb saved_searches add search_name search_expression
Syntax for removing:
calibredb saved_searches remove search_name
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
add_custom_column
Create a custom column. label is the machine friendly name of the column. Should not contain spaces or colons. name
is the human friendly name of the column. datatype is one of: bool, comments, composite, datetime, enumeration,
float, int, rating, series, text
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--display
A dictionary of options to customize how the data in this column will be interpreted. This is a JSON string.
For enumeration columns, use --display (page 279)"{\ "enum_values\ ":[\ "val1\ ", \ "val2\ "]}" There
are many options that can go into the display variable.The options by column type are: composite: compos-
ite_template, composite_sort, make_category,contains_html, use_decorations datetime: date_format enumera-
tion: enum_values, enum_colors, use_decorations int, float: number_format text: is_names, use_decorations
The best way to find legal combinations is to create a custom column of the appropriate type in the GUI then
look at the backup OPF for a book (ensure that a new OPF has been created since the column was added). You
will see the JSON for the "display" for the new column in the OPF.
--is-multiple
This column stores tag like data (i.e. multiple comma separated values). Only applies if datatype is text.
custom_columns
remove_custom_column
Remove the custom column identified by label. You can see available columns with the custom_columns command.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--force, -f
Do not ask for confirmation
set_custom
Set the value of a custom column for the book identified by id. You can get a list of ids using the search command.
You can get a list of custom column names using the custom_columns command.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--append, -a
If the column stores multiple values, append the specified values to the existing ones, instead of replacing them.
restore_database
Restore this database from the metadata stored in OPF files in each directory of the calibre library. This is useful if
your metadata.db file has been corrupted.
WARNING: This command completely regenerates your database. You will lose all saved searches, user categories,
plugboards, stored per-book conversion settings, and custom recipes. Restored metadata will only be as accurate as
what is found in the OPF files.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--really-do-it, -r
Really do the recovery. The command will not run unless this option is specified.
check_library
Perform some checks on the filesystem representing a library. Reports are invalid_titles, extra_titles, invalid_authors,
extra_authors, missing_formats, extra_formats, extra_files, missing_covers, extra_covers, failed_folders
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--csv, -c
Output in CSV
--ignore_extensions, -e
Comma-separated list of extensions to ignore. Default: all
--ignore_names, -n
Comma-separated list of names to ignore. Default: all
--report, -r
Comma-separated list of reports. Default: all
list_categories
Produce a report of the category information in the database. The information is the equivalent of what is shown in the
tags pane.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--categories, -r
Comma-separated list of category lookup names. Default: all
--csv, -c
Output in CSV
--dialect
The type of CSV file to produce. Choices: excel, excel-tab
--item_count, -i
Output only the number of items in a category instead of the counts per item within the category
--width, -w
The maximum width of a single line in the output. Defaults to detecting screen size.
backup_metadata
Backup the metadata stored in the database into individual OPF files in each books directory. This normally happens
automatically, but you can run this command to force re-generation of the OPF files, with the –all option.
Note that there is normally no need to do this, as the OPF files are backed up automatically, every time metadata is
changed.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--all
Normally, this command only operates on books that have out of date OPF files. This option makes it operate
on all books.
clone
Create a clone of the current library. This creates a new, empty library that has all the same custom columns, Virtual
libraries and other settings as the current library.
The cloned library will contain no books. If you want to create a full duplicate, including all books, then simply use
your filesystem tools to copy the library folder.
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
embed_metadata
Update the metadata in the actual book files stored in the calibre library from the metadata in the calibre database.
Normally, metadata is updated only when exporting files from calibre, this command is useful if you want the files to
be updated in place. Note that different file formats support different amounts of metadata. You can use the special
value ‘all’ for book_id to update metadata in all books. You can also specify many book ids separated by spaces and
id ranges separated by hyphens. For example: calibredb embed_metadata 1 2 10-15 23
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--only-formats, -f
Only update metadata in files of the specified format. Specify it multiple times for multiple formats. By default,
all formats are updated.
search
Search the library for the specified search term, returning a comma separated list of book ids matching the search
expression. The output format is useful to feed into other commands that accept a list of ids as input.
The search expression can be anything from calibre’s powerful search query language, for example: au-
thor:asimov title:robot
Whenever you pass arguments to calibredb that have spaces in them, enclose the arguments in quotation marks. For
example: “/some path/with spaces”
--limit, -l
The maximum number of results to return. Default is all results.
12.1.7 ebook-convert
Below are the options that are common to all conversion, followed by the options specific to every input and output
format.
--help, -h
show this help message and exit
--input-profile
Specify the input profile. The input profile gives the conversion system information on how to interpret various
information in the input document. For example resolution dependent lengths (i.e. lengths in pixels). Choices
are:cybookg3, cybook_opus, default, hanlinv3, hanlinv5, illiad, irexdr1000, irexdr800, kindle, msreader, mo-
bipocket, nook, sony, sony300, sony900
--list-recipes
List builtin recipe names. You can create an e-book from a builtin recipe like this: ebook-convert "Recipe
Name.recipe" output.epub
--output-profile
Specify the output profile. The output profile tells the conversion system how to optimize the created doc-
ument for the specified device (such as by resizing images for the device screen size). In some cases, an
output profile can be used to optimize the output for a particular device, but this is rarely necessary. Choices
are:cybookg3, cybook_opus, default, generic_eink, generic_eink_hd, generic_eink_large, hanlinv3, hanlinv5,
illiad, ipad, ipad3, irexdr1000, irexdr800, jetbook5, kindle, kindle_dx, kindle_fire, kindle_oasis, kindle_pw,
kindle_pw3, kindle_voyage, kobo, msreader, mobipocket, nook, nook_color, nook_hd_plus, pocketbook_900,
pocketbook_pro_912, galaxy, sony, sony300, sony900, sony-landscape, sonyt3, tablet
--version
show program's version number and exit
--disable-font-rescaling
Disable all rescaling of font sizes.
--embed-all-fonts
Embed every font that is referenced in the input document but not already embedded. This will search your
system for the fonts, and if found, they will be embedded. Embedding will only work if the format you are
converting to supports embedded fonts, such as EPUB, AZW3, DOCX or PDF. Please ensure that you have the
proper license for embedding the fonts used in this document.
--embed-font-family
Embed the specified font family into the book. This specifies the "base" font used for the book. If the input
document specifies its own fonts, they may override this base font. You can use the filter style information
option to remove fonts from the input document. Note that font embedding only works with some output
formats, principally EPUB, AZW3 and DOCX.
--expand-css
By default, calibre will use the shorthand form for various CSS properties such as margin, padding, border,
etc. This option will cause it to use the full expanded form instead. Note that CSS is always expanded when
generating EPUB files with the output profile set to one of the Nook profiles as the Nook cannot handle shorthand
CSS.
--extra-css
Either the path to a CSS stylesheet or raw CSS. This CSS will be appended to the style rules from the source
file, so it can be used to override those rules.
--filter-css
A comma separated list of CSS properties that will be removed from all CSS style rules. This is useful if
the presence of some style information prevents it from being overridden on your device. For example: font-
family,color,margin-left,margin-right
--font-size-mapping
Mapping from CSS font names to font sizes in pts. An example setting is 12,12,14,16,18,20,22,24. These are
the mappings for the sizes xx-small to xx-large, with the final size being for huge fonts. The font rescaling
algorithm uses these sizes to intelligently rescale fonts. The default is to use a mapping based on the output
profile you chose.
--insert-blank-line
Insert a blank line between paragraphs. Will not work if the source file does not use paragraphs (<p> or <div>
tags).
--insert-blank-line-size
Set the height of the inserted blank lines (in em). The height of the lines between paragraphs will be twice the
value set here.
--keep-ligatures
Preserve ligatures present in the input document. A ligature is a special rendering of a pair of characters like ff,
fi, fl et cetera. Most readers do not have support for ligatures in their default fonts, so they are unlikely to render
correctly. By default, calibre will turn a ligature into the corresponding pair of normal characters. This option
will preserve them instead.
--line-height
The line height in pts. Controls spacing between consecutive lines of text. Only applies to elements that do not
define their own line height. In most cases, the minimum line height option is more useful. By default no line
height manipulation is performed.
--linearize-tables
Some badly designed documents use tables to control the layout of text on the page. When converted these
documents often have text that runs off the page and other artifacts. This option will extract the content from
the tables and present it in a linear fashion.
--margin-bottom
Set the bottom margin in pts. Default is 5.0. Setting this to less than zero will cause no margin to be set (the
margin setting in the original document will be preserved). Note: Page oriented formats such as PDF and DOCX
have their own margin settings that take precedence.
--margin-left
Set the left margin in pts. Default is 5.0. Setting this to less than zero will cause no margin to be set (the margin
setting in the original document will be preserved). Note: Page oriented formats such as PDF and DOCX have
their own margin settings that take precedence.
--margin-right
Set the right margin in pts. Default is 5.0. Setting this to less than zero will cause no margin to be set (the margin
setting in the original document will be preserved). Note: Page oriented formats such as PDF and DOCX have
their own margin settings that take precedence.
--margin-top
Set the top margin in pts. Default is 5.0. Setting this to less than zero will cause no margin to be set (the margin
setting in the original document will be preserved). Note: Page oriented formats such as PDF and DOCX have
their own margin settings that take precedence.
--minimum-line-height
The minimum line height, as a percentage of the element's calculated font size. calibre will ensure that every
element has a line height of at least this setting, irrespective of what the input document specifies. Set to zero to
disable. Default is 120%. Use this setting in preference to the direct line height specification, unless you know
what you are doing. For example, you can achieve "double spaced" text by setting this to 240.
--remove-paragraph-spacing
Remove spacing between paragraphs. Also sets an indent on paragraphs of 1.5em. Spacing removal will not
work if the source file does not use paragraphs (<p> or <div> tags).
--remove-paragraph-spacing-indent-size
When calibre removes blank lines between paragraphs, it automatically sets a paragraph indent, to ensure that
paragraphs can be easily distinguished. This option controls the width of that indent (in em). If you set this value
negative, then the indent specified in the input document is used, that is, calibre does not change the indentation.
--smarten-punctuation
Convert plain quotes, dashes and ellipsis to their typographically correct equivalents. For details, see https:
//daringfireball.net/projects/smartypants
--subset-embedded-fonts
Subset all embedded fonts. Every embedded font is reduced to contain only the glyphs used in this document.
This decreases the size of the font files. Useful if you are embedding a particularly large font with lots of unused
glyphs.
--transform-css-rules
Path to a file containing rules to transform the CSS styles in this book. The easiest way to create such a file is to
use the wizard for creating rules in the calibre GUI. Access it in the "Look & feel->Transform styles" section
of the conversion dialog. Once you create the rules, you can use the "Export" button to save them to a file.
--unsmarten-punctuation
Convert fancy quotes, dashes and ellipsis to their plain equivalents.
Heuristic Processing
Modify the document text and structure using common patterns. Disabled by default. Use –enable-heuristics to enable.
Individual actions can be disabled with the –disable-* options.
--disable-dehyphenate
Analyze hyphenated words throughout the document. The document itself is used as a dictionary to determine
whether hyphens should be retained or removed.
--disable-delete-blank-paragraphs
Remove empty paragraphs from the document when they exist between every other paragraph
--disable-fix-indents
Turn indentation created from multiple non-breaking space entities into CSS indents.
--disable-format-scene-breaks
Left aligned scene break markers are center aligned. Replace soft scene breaks that use multiple blank lines
with horizontal rules.
--disable-italicize-common-cases
Look for common words and patterns that denote italics and italicize them.
--disable-markup-chapter-headings
Detect unformatted chapter headings and sub headings. Change them to h2 and h3 tags. This setting will not
create a TOC, but can be used in conjunction with structure detection to create one.
--disable-renumber-headings
Looks for occurrences of sequential <h1> or <h2> tags. The tags are renumbered to prevent splitting in the
middle of chapter headings.
--disable-unwrap-lines
Unwrap lines using punctuation and other formatting clues.
--enable-heuristics
Enable heuristic processing. This option must be set for any heuristic processing to take place.
--html-unwrap-factor
Scale used to determine the length at which a line should be unwrapped. Valid values are a decimal between
0 and 1. The default is 0.4, just below the median line length. If only a few lines in the document require
unwrapping this value should be reduced
--replace-scene-breaks
Replace scene breaks with the specified text. By default, the text from the input document is used.
Modify the document text and structure using user defined patterns.
--search-replace
Path to a file containing search and replace regular expressions. The file must contain alternating lines of regular
expression followed by replacement pattern (which can be an empty line). The regular expression must be in
the Python regex syntax and the file must be UTF-8 encoded.
--sr1-replace
Replacement to replace the text found with sr1-search.
--sr1-search
Search pattern (regular expression) to be replaced with sr1-replace.
--sr2-replace
Replacement to replace the text found with sr2-search.
--sr2-search
Search pattern (regular expression) to be replaced with sr2-replace.
--sr3-replace
Replacement to replace the text found with sr3-search.
--sr3-search
Search pattern (regular expression) to be replaced with sr3-replace.
Structure Detection
Table of Contents
Control the automatic generation of a Table of Contents. By default, if the source file has a Table of Contents, it will
be used in preference to the automatically generated one.
--duplicate-links-in-toc
When creating a TOC from links in the input document, allow duplicate entries, i.e. allow more than one entry
with the same text, provided that they point to a different location.
--level1-toc
XPath expression that specifies all tags that should be added to the Table of Contents at level one. If this is
specified, it takes precedence over other forms of auto-detection. See the XPath Tutorial in the calibre User
Manual for examples.
--level2-toc
XPath expression that specifies all tags that should be added to the Table of Contents at level two. Each entry is
added under the previous level one entry. See the XPath Tutorial in the calibre User Manual for examples.
--level3-toc
XPath expression that specifies all tags that should be added to the Table of Contents at level three. Each entry
is added under the previous level two entry. See the XPath Tutorial in the calibre User Manual for examples.
--max-toc-links
Maximum number of links to insert into the TOC. Set to 0 to disable. Default is: 50. Links are only added to
the TOC if less than the threshold number of chapters were detected.
--no-chapters-in-toc
Don't add auto-detected chapters to the Table of Contents.
--toc-filter
Remove entries from the Table of Contents whose titles match the specified regular expression. Matching entries
and all their children are removed.
--toc-threshold
If fewer than this number of chapters is detected, then links are added to the Table of Contents. Default: 6
--use-auto-toc
Normally, if the source file already has a Table of Contents, it is used in preference to the auto-generated one.
With this option, the auto-generated one is always used.
Metadata
--read-metadata-from-opf, --from-opf, -m
Read metadata from the specified OPF file. Metadata read from this file will override any metadata in the source
file.
--series
Set the series this e-book belongs to.
--series-index
Set the index of the book in this series.
--tags
Set the tags for the book. Should be a comma separated list.
--timestamp
Set the book timestamp (no longer used anywhere)
--title
Set the title.
--title-sort
The version of the title to be used for sorting.
Debug
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--colors
Reduce the number of colors used in the image. This works only if you choose the PNG output format. It is
useful to reduce file sizes. Set to zero to turn off. Maximum value is 256. It is off by default.
--comic-image-size
Specify the image size as widthxheight pixels. Normally, an image size is automatically calculated from the
output profile, this option overrides it.
--despeckle
Enable Despeckle. Reduces speckle noise. May greatly increase processing time.
--disable-trim
Disable trimming of comic pages. For some comics, trimming might remove content as well as borders.
--dont-add-comic-pages-to-toc
When converting a CBC do not add links to each page to the TOC. Note this only applies if the TOC has more
than one section
--dont-grayscale
Do not convert the image to grayscale (black and white)
--dont-normalize
Disable normalize (improve contrast) color range for pictures. Default: False
--dont-sharpen
Disable sharpening.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--keep-aspect-ratio
Maintain picture aspect ratio. Default is to fill the screen.
--landscape
Don't split landscape images into two portrait images
--no-process
Apply no processing to the image
--no-sort
Don't sort the files found in the comic alphabetically by name. Instead use the order they were added to the
comic.
--output-format
The format that images in the created e-book are converted to. You can experiment to see which format gives
you optimal size and look on your device.
--right2left
Used for right-to-left publications like manga. Causes landscape pages to be split into portrait pages from right
to left.
--wide
Keep aspect ratio and scale image using screen height as image width for viewing in landscape mode.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--docx-inline-subsup
Render superscripts and subscripts so that they do not affect the line height.
--docx-no-cover
Normally, if a large image is present at the start of the document that looks like a cover, it will be removed from
the document and used as the cover for created e-book. This option turns off that behavior.
--docx-no-pagebreaks-between-notes
Do not insert a page break after every endnote.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--no-inline-fb2-toc
Do not insert a Table of Contents at the beginning of the book.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--breadth-first
Traverse links in HTML files breadth first. Normally, they are traversed depth first.
--dont-package
Normally this input plugin re-arranges all the input files into a standard folder hierarchy. Only use this option if
you know what you are doing as it can result in various nasty side effects in the rest of the conversion pipeline.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--max-levels
Maximum levels of recursion when following links in HTML files. Must be non-negative. 0 implies that no
links in the root HTML file are followed. Default is 5.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--new-pdf-engine
Use the new PDF conversion engine. Currently not operational.
--no-images
Do not extract images from the document
--unwrap-factor
Scale used to determine the length at which a line should be unwrapped. Valid values are a decimal between 0
and 1. The default is 0.45, just below the median line length.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
RB Input Options
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--ignore-wmf
Ignore WMF images instead of replacing them with a placeholder image.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--dont-download-recipe
Do not download latest version of builtin recipes from the calibre server
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--lrf
Optimize fetching for subsequent conversion to LRF.
--password
Password for sites that require a login to access content.
--test
Useful for recipe development. Forces max_articles_per_feed to 2 and downloads at most 2 feeds. You can
change the number of feeds and articles by supplying optional arguments. For example: --test (page 294) 3
1 will download at most 3 feeds and only 1 article per feed.
--username
Username for sites that require a login to access content.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--formatting-type
Formatting used within the document. * auto: Automatically decide which formatting processor to use * plain:
No formatting * heuristic: Use heuristics to determine chapter headings, italics, etc. * textile: Use the TexTile
markup language * markdown: Use the Markdown markup language To learn more about markdown see https:
//daringfireball.net/projects/markdown/
--input-encoding
Specify the character encoding of the input document. If set this option will override any encoding declared by
the document itself. Particularly useful for documents that do not declare an encoding or that have erroneous
encoding declarations.
--markdown-extensions
Enable extensions to markdown syntax. Extensions are formatting that is not part of the standard markdown
format. The extensions enabled by default: footnotes, tables, toc. To learn more about markdown extensions, see
https://python-markdown.github.io/extensions/ This should be a comma separated list of extensions to enable:
* abbr: Abbreviations * admonition: Support admonitions * attr_list: Add attribute to HTML tags * codehilite:
Add code highlighting via Pygments * def_list: Definition lists * extra: Enables various common extensions *
fenced_code: Alternative code block syntax * footnotes: Footnotes * legacy_attrs: Use legacy element attributes
* legacy_em: Use legacy underscore handling for connected words * meta: Metadata in the document * nl2br:
Treat newlines as hard breaks * sane_lists: Do not allow mixing list types * smarty: Use markdown's internal
smartypants parser * tables: Support tables * toc: Generate a table of contents * wikilinks: Wiki style links
--paragraph-type
Paragraph structure to assume. The value of "off" is useful for formatted documents such as Markdown or
Textile. Choices are: * auto: Try to auto detect paragraph type * block: Treat a blank line as a paragraph break
* single: Assume every line is a paragraph * print: Assume every line starting with 2+ spaces or a tab starts a
paragraph * unformatted: Most lines have hard line breaks, few/no blank lines or indents * off: Don't modify
the paragraph structure
--preserve-spaces
Normally extra spaces are condensed into a single space. With this option all spaces will be displayed.
--txt-in-remove-indents
Normally extra space at the beginning of lines is retained. With this option they will be removed.
--dont-compress
Disable compression of the file contents.
--extract-to
Extract the contents of the generated AZW3 file to the specified directory. The contents of the directory are first
deleted, so be careful.
--mobi-toc-at-start
When adding the Table of Contents to the book, add it at the start of the book instead of the end. Not recom-
mended.
--no-inline-toc
Don't add Table of Contents to the book. Useful if the book has its own table of contents.
--prefer-author-sort
When present, use author sort field as author.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--share-not-sync
Enable sharing of book content via Facebook etc. on the Kindle. WARNING: Using this feature means that the
book will not auto sync its last read position on multiple devices. Complain to Amazon.
--toc-title
Title for any generated in-line table of contents.
--docx-custom-page-size
Custom size of the document. Use the form widthxheight EG. 123x321 to specify the width and height (in pts).
This overrides any specified page-size.
--docx-no-cover
Do not insert the book cover as an image at the start of the document. If you use this option, the book cover will
be discarded.
--docx-no-toc
Do not insert the table of contents as a page at the start of the document.
--docx-page-margin-bottom
The size of the bottom page margin, in pts. Default is 72pt. Overrides the common bottom page margin setting,
unless set to zero.
--docx-page-margin-left
The size of the left page margin, in pts. Default is 72pt. Overrides the common left page margin setting.
--docx-page-margin-right
The size of the right page margin, in pts. Default is 72pt. Overrides the common right page margin setting,
unless set to zero.
--docx-page-margin-top
The size of the top page margin, in pts. Default is 72pt. Overrides the common top page margin setting, unless
set to zero.
--docx-page-size
The size of the page. Default is letter. Choices are [u'a0', u'a1', u'a2', u'a3', u'a4', u'a5', u'a6',
u'b0', u'b1', u'b2', u'b3', u'b4', u'b5', u'b6', u'legal', u'letter']
--extract-to
Extract the contents of the generated DOCX file to the specified directory. The contents of the directory are first
deleted, so be careful.
--preserve-cover-aspect-ratio
Preserve the aspect ratio of the cover image instead of stretching it out to cover the entire page.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--dont-split-on-page-breaks
Turn off splitting at page breaks. Normally, input files are automatically split at every page break into two files.
This gives an output e-book that can be parsed faster and with less resources. However, splitting is slow and if
your source file contains a very large number of page breaks, you should turn off splitting on page breaks.
--epub-flatten
This option is needed only if you intend to use the EPUB with FBReaderJ. It will flatten the file system inside
the EPUB, putting all files into the top level.
--epub-inline-toc
Insert an inline Table of Contents that will appear as part of the main book content.
--epub-toc-at-end
Put the inserted inline Table of Contents at the end of the book instead of the start.
--epub-version
The version of the EPUB file to generate. EPUB 2 is the most widely compatible, only use EPUB 3 if you know
you actually need it.
--extract-to
Extract the contents of the generated EPUB file to the specified directory. The contents of the directory are first
deleted, so be careful.
--flow-size
Split all HTML files larger than this size (in KB). This is necessary as most EPUB readers cannot handle large
file sizes. The default of 260KB is the size required for Adobe Digital Editions. Set to 0 to disable size based
splitting.
--no-default-epub-cover
Normally, if the input file has no cover and you don't specify one, a default cover is generated with the title,
authors, etc. This option disables the generation of this cover.
--no-svg-cover
Do not use SVG for the book cover. Use this option if your EPUB is going to be used on a device that does not
support SVG, like the iPhone or the JetBook Lite. Without this option, such devices will display the cover as a
blank page.
--preserve-cover-aspect-ratio
When using an SVG cover, this option will cause the cover to scale to cover the available screen area, but still
preserve its aspect ratio (ratio of width to height). That means there may be white borders at the sides or top
and bottom of the image, but the image will never be distorted. Without this option the image may be slightly
distorted, but there will be no borders.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--toc-title
Title for any generated in-line table of contents.
--fb2-genre
Genre for the book. Choices: sf_history, sf_action, sf_epic, sf_heroic, sf_detective, sf_cyberpunk, sf_space,
sf_social, sf_horror, sf_humor, sf_fantasy, sf, det_classic, det_police, det_action, det_irony, det_history,
det_espionage, det_crime, det_political, det_maniac, det_hard, thriller, detective, prose_classic, prose_history,
prose_contemporary, prose_counter, prose_rus_classic, prose_su_classics, love_contemporary, love_history,
love_detective, love_short, love_erotica, adv_western, adv_history, adv_indian, adv_maritime, adv_geo,
adv_animal, adventure, child_tale, child_verse, child_prose, child_sf, child_det, child_adv, child_education,
children, poetry, dramaturgy, antique_ant, antique_european, antique_russian, antique_east, antique_myths, an-
tique, sci_history, sci_psychology, sci_culture, sci_religion, sci_philosophy, sci_politics, sci_business, sci_juris,
sci_linguistic, sci_medicine, sci_phys, sci_math, sci_chem, sci_biology, sci_tech, science, comp_www,
comp_programming, comp_hard, comp_soft, comp_db, comp_osnet, computers, ref_encyc, ref_dict, ref_ref,
ref_guide, reference, nonf_biography, nonf_publicism, nonf_criticism, design, nonfiction, religion_rel, reli-
gion_esoterics, religion_self, religion, humor_anecdote, humor_prose, humor_verse, humor, home_cooking,
home_pets, home_crafts, home_entertain, home_health, home_garden, home_diy, home_sport, home_sex,
home See: http://www.fictionbook.org/index.php/Eng:FictionBook_2.1_genres for a complete list with descrip-
tions.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--sectionize
Specify how sections are created: * nothing: A single section * files: Section per file * toc: Section per entry
in the ToC If ToC based generation fails, adjust the "Structure detection" and/or "Table of Contents" settings
(turn on "Force use of auto-generated Table of Contents").
--extract-to
Extract the contents of the generated ZIP file to the specified directory. WARNING: The contents of the directory
will be deleted.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--template-css
CSS file used for the output instead of the default file
--template-html
Template used for the generation of the HTML contents of the book instead of the default file
--template-html-index
Template used for generation of the HTML index file instead of the default file
--htmlz-class-style
How to handle the CSS when using css-type = 'class'. Default is external. external: Use an external CSS file
inline: Use a <style> tag in the HTML file
--htmlz-css-type
Specify the handling of CSS. Default is class. class: Use CSS classes inline: Use the style attribute tag: Use
HTML tags wherever possible
--htmlz-title-filename
If set this option causes the file name of the HTML file inside the HTMLZ archive to be based on the book title.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--enable-autorotation
Enable auto-rotation of images that are wider than the screen width.
--header
Add a header to all the pages with title and author.
--header-format
Set the format of the header. %a is replaced by the author and %t by the title. Default is %t by %a
--header-separation
Add extra spacing below the header. Default is 0 pt.
--minimum-indent
Minimum paragraph indent (the indent of the first line of a paragraph) in pts. Default: 0
--mono-family
The monospace family of fonts to embed
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--render-tables-as-images
This option has no effect
--sans-family
The sans-serif family of fonts to embed
--serif-family
The serif family of fonts to embed
--text-size-multiplier-for-rendered-tables
Multiply the size of text in rendered tables by this factor. Default is 1.0
--wordspace
Set the space between words in pts. Default is 2.5
--dont-compress
Disable compression of the file contents.
--extract-to
Extract the contents of the generated MOBI file to the specified directory. The contents of the directory are first
deleted, so be careful.
--mobi-file-type
By default calibre generates MOBI files that contain the old MOBI 6 format. This format is compatible with all
devices. However, by changing this setting, you can tell calibre to generate MOBI files that contain both MOBI
6 and the new KF8 format, or only the new KF8 format. KF8 has more features than MOBI 6, but only works
with newer Kindles. Allowed values: old, both, new
--mobi-ignore-margins
Ignore margins in the input document. If False, then the MOBI output plugin will try to convert margins specified
in the input document, otherwise it will ignore them.
--mobi-keep-original-images
By default calibre converts all images to JPEG format in the output MOBI file. This is for maximum compat-
ibility as some older MOBI viewers have problems with other image formats. This option tells calibre not to
do this. Useful if your document contains lots of GIF/PNG images that become very large when converted to
JPEG.
--mobi-toc-at-start
When adding the Table of Contents to the book, add it at the start of the book instead of the end. Not recom-
mended.
--no-inline-toc
Don't add Table of Contents to the book. Useful if the book has its own table of contents.
--personal-doc
Tag for MOBI files to be marked as personal documents. This option has no effect on the conversion. It is used
only when sending MOBI files to a device. If the file being sent has the specified tag, it will be marked as a
personal document when sent to the Kindle.
--prefer-author-sort
When present, use author sort field as author.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--share-not-sync
Enable sharing of book content via Facebook etc. on the Kindle. WARNING: Using this feature means that the
book will not auto sync its last read position on multiple devices. Complain to Amazon.
--toc-title
Title for any generated in-line table of contents.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
--format, -f
Format to use inside the PDB container. Choices are: [u'doc', u'ereader', u'ztxt']
--inline-toc
Add Table of Contents to beginning of the book.
--pdb-output-encoding
Specify the character encoding of the output document. The default is cp1252. Note: This option is not honored
by all formats.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--custom-size
Custom size of the document. Use the form widthxheight e.g. 123x321 to specify the width and height. This
overrides any specified paper-size.
--paper-size
The size of the paper. This size will be overridden when a non default output profile is used. Default is letter.
Choices are a0, a1, a2, a3, a4, a5, a6, b0, b1, b2, b3, b4, b5, b6, legal, letter
--pdf-add-toc
Add a Table of Contents at the end of the PDF that lists page numbers. Useful if you want to print out the PDF.
If this PDF is intended for electronic use, use the PDF Outline instead.
--pdf-default-font-size
The default font size
--pdf-footer-template
An HTML template used to generate footers on every page. The strings _PAGENUM_, _TITLE_, _AUTHOR_
and _SECTION_ will be replaced by their current values.
--pdf-header-template
An HTML template used to generate headers on every page. The strings _PAGENUM_, _TITLE_, _AUTHOR_
and _SECTION_ will be replaced by their current values.
--pdf-hyphenate
Break long words at the end of lines. This can give the text at the right margin a more even appearance.
--pdf-mark-links
Surround all links with a red box, useful for debugging.
--pdf-mono-family
The font family used to render monospace fonts. Will work only if the font is available system-wide.
--pdf-mono-font-size
The default font size for monospaced text
--pdf-odd-even-offset
Shift the text horizontally by the specified offset (in pts). On odd numbered pages, it is shifted to the right and on
even numbered pages to the left. Use negative numbers for the opposite effect. Note that this setting is ignored
on pages where the margins are smaller than the specified offset. Shifting is done by setting the PDF CropBox,
not all software respects the CropBox.
--pdf-page-margin-bottom
The size of the bottom page margin, in pts. Default is 72pt. Overrides the common bottom page margin setting,
unless set to zero.
--pdf-page-margin-left
The size of the left page margin, in pts. Default is 72pt. Overrides the common left page margin setting.
--pdf-page-margin-right
The size of the right page margin, in pts. Default is 72pt. Overrides the common right page margin setting,
unless set to zero.
--pdf-page-margin-top
The size of the top page margin, in pts. Default is 72pt. Overrides the common top page margin setting, unless
set to zero.
--pdf-page-number-map
Adjust page numbers, as needed. Syntax is a JavaScript expression for the page number. For example, "if (n <
3) 0; else n - 3;", where n is current page number.
--pdf-page-numbers
Add page numbers to the bottom of every page in the generated PDF file. If you specify a footer template, it
will take precedence over this option.
--pdf-sans-family
The font family used to render sans-serif fonts. Will work only if the font is available system-wide.
--pdf-serif-family
The font family used to render serif fonts. Will work only if the font is available system-wide.
--pdf-standard-font
The font family used to render monospace fonts
--pdf-use-document-margins
Use the page margins specified in the input document via @page CSS rules. This will cause the margins
specified in the conversion settings to be ignored. If the document does not specify page margins, the conversion
settings will be used as a fallback.
--preserve-cover-aspect-ratio
Preserve the aspect ratio of the cover, instead of stretching it to fill the full first page of the generated pdf.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--toc-title
Title for generated table of contents.
--uncompressed-pdf
Generate an uncompressed PDF, useful for debugging.
--unit, -u
The unit of measure for page sizes. Default is inch. Choices are millimeter, centimeter, point, inch, pica, didot,
cicero, devicepixel Note: This does not override the unit for margins!
--use-profile-size
Instead of using the paper size specified in the PDF Output options, use a paper size corresponding to the current
output profile. Useful if you want to generate a PDF for viewing on a specific device.
--full-image-depth
Do not reduce the size or bit depth of images. Images have their size and depth reduced by default to accommo-
date applications that can not convert images on their own such as Dropbook.
--inline-toc
Add Table of Contents to beginning of the book.
--pml-output-encoding
Specify the character encoding of the output document. The default is cp1252.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
RB Output Options
--inline-toc
Add Table of Contents to beginning of the book.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--snb-dont-indent-first-line
Specify whether or not to insert two space characters to indent the first line of each paragraph.
--snb-full-screen
Resize all the images for full screen view.
--snb-hide-chapter-name
Specify whether or not to hide the chapter title for each chapter. Useful for image-only output (eg. comics).
--snb-insert-empty-line
Specify whether or not to insert an empty line between two paragraphs.
--snb-max-line-length
The maximum number of characters per line. This splits on the first space before the specified value. If no space
is found the line will be broken at the space after and will exceed the specified value. Also, there is a minimum
of 25 characters. Use 0 to disable line splitting.
--snb-output-encoding
Specify the character encoding of the output document. The default is utf-8.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--tcr-output-encoding
Specify the character encoding of the output document. The default is utf-8.
--force-max-line-length
Force splitting on the max-line-length value when no space is present. Also allows max-line-length to be below
the minimum
--inline-toc
Add Table of Contents to beginning of the book.
--keep-color
Do not remove font color from output. This is only useful when TXT output formatting is set to textile. Textile
is the only formatting that supports setting font color. If this option is not specified font color will not be set and
default to the color displayed by the reader (generally this is black).
--keep-image-references
Do not remove image references within the document. This is only useful when paired with a TXT output
formatting option that is not none because links are always removed with plain text output.
--keep-links
Do not remove links within the document. This is only useful when paired with a TXT output formatting option
that is not none because links are always removed with plain text output.
--max-line-length
The maximum number of characters per line. This splits on the first space before the specified value. If no space
is found the line will be broken at the space after and will exceed the specified value. Also, there is a minimum
of 25 characters. Use 0 to disable line splitting.
--newline, -n
Type of newline to use. Options are [u'old_mac', u'system', u'unix', u'windows']. Default is 'system'.
Use 'old_mac' for compatibility with Mac OS 9 and earlier. For macOS use 'unix'. 'system' will default to
the newline type used by this OS.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--txt-output-encoding
Specify the character encoding of the output document. The default is utf-8.
--txt-output-formatting
Formatting used within the document. * plain: Plain text * markdown: Markdown formatted text * textile:
TexTile formatted text
--force-max-line-length
Force splitting on the max-line-length value when no space is present. Also allows max-line-length to be below
the minimum
--inline-toc
Add Table of Contents to beginning of the book.
--keep-color
Do not remove font color from output. This is only useful when TXT output formatting is set to textile. Textile
is the only formatting that supports setting font color. If this option is not specified font color will not be set and
default to the color displayed by the reader (generally this is black).
--keep-image-references
Do not remove image references within the document. This is only useful when paired with a TXT output
formatting option that is not none because links are always removed with plain text output.
--keep-links
Do not remove links within the document. This is only useful when paired with a TXT output formatting option
that is not none because links are always removed with plain text output.
--max-line-length
The maximum number of characters per line. This splits on the first space before the specified value. If no space
is found the line will be broken at the space after and will exceed the specified value. Also, there is a minimum
of 25 characters. Use 0 to disable line splitting.
--newline, -n
Type of newline to use. Options are [u'old_mac', u'system', u'unix', u'windows']. Default is 'system'.
Use 'old_mac' for compatibility with Mac OS 9 and earlier. For macOS use 'unix'. 'system' will default to
the newline type used by this OS.
--pretty-print
If specified, the output plugin will try to create output that is as human readable as possible. May not have any
effect for some output plugins.
--txt-output-encoding
Specify the character encoding of the output document. The default is utf-8.
--txt-output-formatting
Formatting used within the document. * plain: Plain text * markdown: Markdown formatted text * textile:
TexTile formatted text
12.1.8 ebook-edit
Launch the calibre edit book tool. You can optionally also specify the names of files inside the book which will be
opened for editing automatically.
Whenever you pass arguments to ebook-edit that have spaces in them, enclose the arguments in quotation marks.
For example: “/some path/with spaces”
[options]
--detach
Detach from the controlling terminal, if any (Linux only)
--help, -h
show this help message and exit
--version
show program's version number and exit
12.1.9 ebook-meta
[options]
--author-sort
String to be used when sorting by author. If unspecified, and the author(s) are specified, it will be auto-generated
from the author(s).
--authors, -a
Set the authors. Multiple authors should be separated by the & character. Author names should be in the order
Firstname Lastname.
--book-producer, -k
Set the book producer.
--category
Set the book category.
--comments, -c
Set the e-book description.
--cover
Set the cover to the specified file.
--date, -d
Set the published date.
--from-opf
Read metadata from the specified OPF file and use it to set metadata in the e-book. Metadata specified on the
command line will override metadata read from the OPF file
--get-cover
Get the cover from the e-book and save it at as the specified file.
--help, -h
show this help message and exit
--identifier
Set the identifiers for the book, can be specified multiple times. For example: --identifier (page 306)
uri:https://acme.com --identifier (page 306) isbn:12345 To remove an identifier, specify no value,
--identifier (page 306) isbn: Note that for EPUB files, an identifier marked as the package identifier
cannot be removed.
--index, -i
Set the index of the book in this series.
--isbn
Set the ISBN of the book.
--language, -l
Set the language.
--lrf-bookid
Set the BookID in LRF files
--publisher, -p
Set the e-book publisher.
--rating, -r
Set the rating. Should be a number between 1 and 5.
--series, -s
Set the series this e-book belongs to.
--tags
Set the tags for the book. Should be a comma separated list.
--title, -t
Set the title.
--title-sort
The version of the title to be used for sorting. If unspecified, and the title is specified, it will be auto-generated
from the title.
--to-opf
Specify the name of an OPF file. The metadata will be written to the OPF file.
--version
show program's version number and exit
12.1.10 ebook-polish
Polishing books is all about putting the shine of perfection onto your carefully crafted e-books.
Polishing tries to minimize the changes to the internal code of your e-book. Unlike conversion, it does not flatten CSS,
rename files, change font sizes, adjust margins, etc. Every action performs only the minimum set of changes needed
for the desired effect.
You should use this tool as the last step in your e-book creation process.
Note that polishing only works on files in the AZW3 or EPUB formats.
Whenever you pass arguments to ebook-polish that have spaces in them, enclose the arguments in quotation
marks. For example: “/some path/with spaces”
[options]
--add-soft-hyphens, -H
Add soft hyphens to all words in the book. This allows the book to be rendered better when the text is justified,
in readers that do not support hyphenation.
--compress-images, -i
Losslessly compress images in the book, to reduce the filesize, without affecting image quality.
--cover, -c
Path to a cover image. Changes the cover specified in the e-book. If no cover is present, or the cover is not
properly identified, inserts a new cover.
--embed-fonts, -e
Embed all fonts that are referenced in the document and are not already embedded. This will scan your computer
for the fonts, and if they are found, they will be embedded into the document. Please ensure that you have the
proper license for embedding the fonts used in this document.
--help, -h
show this help message and exit
--jacket, -j
Insert a "book jacket" page at the start of the book that contains all the book metadata such as title, tags, authors,
series, comments, etc. Any previous book jacket will be replaced.
--opf, -o
Path to an OPF file. The metadata in the book is updated from the OPF file.
--remove-jacket
Remove a previous inserted book jacket page.
--remove-soft-hyphens
Remove soft hyphens from all text in the book.
--remove-unused-css, -u
Remove all unused CSS rules from stylesheets and <style> tags. Some books created from production templates
can have a large number of extra CSS rules that dont match any actual content. These extra rules can slow down
readers that need to parse them all.
--smarten-punctuation, -p
Convert plain text dashes, ellipsis, quotes, multiple hyphens, etc. into their typographically correct equivalents.
Note that the algorithm can sometimes generate incorrect results, especially when single quotes at the start of
contractions are involved.
--subset-fonts, -f
Subsetting fonts means reducing an embedded font to contain only the characters used from that font in the
book. This greatly reduces the size of the font files (halving the font file sizes is common). For example, if the
book uses a specific font for headers, then subsetting will reduce that font to contain only the characters present
in the actual headers in the book. Or if the book embeds the bold and italic versions of a font, but bold and
italic text is relatively rare, or absent altogether, then the bold and italic fonts can either be reduced to only a few
characters or completely removed. The only downside to subsetting fonts is that if, at a later date you decide to
add more text to your books, the newly added text might not be covered by the subset font.
--upgrade-book, -U
Upgrade the internal structures of the book, if possible. For instance, upgrades EPUB 2 books to EPUB 3 books.
--verbose
Produce more verbose output, useful for debugging.
--version
show program's version number and exit
12.1.11 ebook-viewer
View an e-book.
Whenever you pass arguments to ebook-viewer that have spaces in them, enclose the arguments in quotation
marks. For example: “/some path/with spaces”
[options]
--continue
Continue reading at the previously opened book
--detach
Detach from the controlling terminal, if any (Linux only)
--force-reload
Force reload of all opened books
--full-screen, --fullscreen, -f
If specified, viewer window will try to open full screen when started.
--help, -h
show this help message and exit
--open-at
The position at which to open the specified book. The position is a location or position you can get by using
the Go to->Location action in the viewer controls. Alternately, you can use the form toc:something and it will
open at the location of the first Table of Contents entry that contains the string "something". The form toc-
href:something will match the href (internal link destination) of toc nodes. The matching is exact, If you want to
match a substring, use the form toc-href-contains:something. The form ref:something will use Reference mode
references.
--raise-window
If specified, viewer window will try to come to the front when started.
--version
show program's version number and exit
12.1.12 fetch-ebook-metadata
fetch-ebook-metadata [options]
Fetch book metadata from online sources. You must specify at least one of title, authors or ISBN.
Whenever you pass arguments to fetch-ebook-metadata that have spaces in them, enclose the arguments in
quotation marks. For example: “/some path/with spaces”
[options]
--allowed-plugin, -p
Specify the name of a metadata download plugin to use. By default, all metadata plugins will be used. Can
be specified multiple times for multiple plugins. All plugin names: Google, Google Images, Amazon.com,
Edelweiss, Open Library, Overdrive, Douban Books, OZON.ru, Big Book Search
--authors, -a
Book author(s)
--cover, -c
Specify a filename. The cover, if available, will be saved to it. Without this option, no cover will be downloaded.
--help, -h
show this help message and exit
--identifier, -I
Identifiers such as ASIN/goodreads id etc. Can be specified multiple times for multiple identifiers. For example:
--identifier (page 310) asin:B0082BAJA0
--isbn, -i
Book ISBN
--opf, -o
Output the metadata in OPF format instead of human readable text.
--timeout, -d
Timeout in seconds. Default is 30
--title, -t
Book title
--verbose, -v
Print the log to the console (stderr)
--version
show program's version number and exit
12.1.13 lrf2lrs
lrf2lrs book.lrf
[options]
--dont-output-resources
Do not save embedded image and font files to disk
--help, -h
show this help message and exit
--output, -o
Output LRS file
--verbose
Be more verbose
--version
show program's version number and exit
12.1.14 lrfviewer
[options]
--disable-hyphenation
Disable hyphenation. Should significantly speed up rendering.
--help, -h
show this help message and exit
--profile
Profile the LRF renderer
--verbose
Print more information about the rendering process
--version
show program's version number and exit
--visual-debug
Turn on visual aids to debugging the rendering engine
--white-background
By default the background is off white as I find this easier on the eyes. Use this option to make the background
pure white.
12.1.15 lrs2lrf
[options]
--help, -h
show this help message and exit
--lrs
Convert LRS to LRS, useful for debugging.
--output, -o
Path to output file
--verbose
Verbose processing
--version
show program's version number and exit
12.1.16 web2disk
web2disk URL
[options]
--base-dir, -d
Base directory into which URL is saved. Default is .
--delay
Minimum interval in seconds between consecutive fetches. Default is 0 s
--dont-download-stylesheets
Do not download CSS stylesheets.
--encoding
The character encoding for the websites you are trying to download. The default is to try and guess the encoding.
--filter-regexp
Any link that matches this regular expression will be ignored. This option can be specified multiple times, in
which case as long as any regexp matches a link, it will be ignored. By default, no links are ignored. If both
filter regexp and match regexp are specified, then filter regexp is applied first.
--help, -h
show this help message and exit
--match-regexp
Only links that match this regular expression will be followed. This option can be specified multiple times, in
which case as long as a link matches any one regexp, it will be followed. By default all links are followed.
--max-files, -n
The maximum number of files to download. This only applies to files from <a href> tags. Default is
9223372036854775807
--max-recursions, -r
Maximum number of levels to recurse i.e. depth of links to follow. Default 1
--timeout, -t
Timeout in seconds to wait for a response from the server. Default: 10.0 s
--verbose
Show detailed output information. Useful for debugging
--version
show program's version number and exit
• ebook-device
• markdown-calibre
You can see usage for undocumented commands by executing them without arguments in a terminal.
calibre is completely open source, licensed under the GNU GPL v3100 . This means that you are free to download
and modify the program to your heart’s content. In this section, you will learn how to get a calibre development
environment set up on the operating system of your choice. calibre is written primarily in Python101 with some C/C++
code for speed and system interfacing. Note that calibre is not compatible with Python 3 and requires at least Python
2.7.9.
Contents
100 https://www.gnu.org/licenses/gpl.html
101 https://www.python.org
313
calibre User Manual, Release 4.21.0
calibre has its roots in the Unix world, which means that its design is highly modular. The modules interact with each
other via well defined interfaces. This makes adding new features and fixing bugs in calibre very easy, resulting in
a frenetic pace of development. Because of its roots, calibre has a comprehensive command line interface for all its
functions, documented in Command Line Interface (page ??).
The modular design of calibre is expressed via Plugins. There is a tutorial (page 227) on writing calibre plugins. For
example, adding support for a new device to calibre typically involves writing less than a 100 lines of code in the form
of a device driver plugin. You can browse the built-in drivers102 . Similarly, adding support for new conversion formats
involves writing input/output format plugins. Another example of the modular design is the recipe system (page 25)
for fetching news. For more examples of plugins designed to add features to calibre, see the Index of plugins103 .
All the calibre python code is in the calibre package. This package contains the following main sub-packages
• devices - All the device drivers. Just look through some of the built-in drivers to get an idea for how they work.
– For details, see: devices.interface which defines the interface supported by device drivers and
devices.usbms which defines a generic driver that connects to a USBMS device. All USBMS based
drivers in calibre inherit from it.
• e-books - All the e-book conversion/metadata code. A good starting point is calibre.ebooks.
conversion.cli which is the module powering the ebook-convert command. The conversion pro-
cess is controlled via conversion.plumber. The format independent code is all in ebooks.oeb and the
format dependent code is in ebooks.format_name.
– Metadata reading, writing, and downloading is all in ebooks.metadata
– Conversion happens in a pipeline, for the structure of the pipeline, see Introduction (page 63). The pipeline
consists of an input plugin, various transforms and an output plugin. The code that constructs and drives the
pipeline is in plumber.py. The pipeline works on a representation of an e-book that is like an unzipped
epub, with manifest, spine, toc, guide, html content, etc. The class that manages this representation is
OEBBook in ebooks.oeb.base. The various transformations that are applied to the book during
conversions live in oeb/transforms/*.py. And the input and output plugins live in conversion/
plugins/*.py.
– E-book editing happens using a different container object. It is documented in API documentation for the
e-book editing tools (page 327).
• db - The database back-end. See API documentation for the database interface (page 321) for the interface to
the calibre library.
• Content server: srv is the calibre Content server.
102 https://github.com/kovidgoyal/calibre/tree/master/src/calibre/devices
103 https://www.mobileread.com/forums/showthread.php?p=1362767#post1362767
• gui2 - The Graphical User Interface. GUI initialization happens in gui2.main and gui2.ui. The e-book-
viewer is in gui2.viewer. The e-book editor is in gui2.tweak_book.
If you want to locate the entry points for all the various calibre executables, look at the entry_points structure in
linux.py104 .
If you need help understanding the code, post in the development forum105 and you will most likely get help from one
of calibre’s many developers.
You can get the calibre source code in two ways, using a version control system or directly downloading a tarball106 .
calibre uses Git107 , a distributed version control system. Git is available on all the platforms calibre supports. After
installing Git, you can get the calibre source code with the command:
On Windows you will need the complete path name, that will be something like C:\Program Files\Git\git.
exe.
calibre is a very large project with a very long source control history, so the above can take a while (10 mins to an hour
depending on your internet speed).
If you want to get the code faster, the source code for the latest release is always available as an archive108 .
To update a branch to the latest code, use the command:
If you only plan to make a few small changes, you can make your changes and create a “merge directive” which you
can then attach to a ticket in the calibre bug tracker110 . To do this, make your changes, then run:
This will create a my-changes file in the current directory, simply attach that to a ticket on the calibre bug tracker111 .
Note that this will include all the commits you have made. If you only want to send some commits, you have to change
origin/master above. To send only the last commit, use:
To send the last n commits, replace 1 with n, for example, for the last 3 commits:
104 https://github.com/kovidgoyal/calibre/blob/master/src/calibre/linux.py
105 https://www.mobileread.com/forums/forumdisplay.php?f=240
106 https://calibre-ebook.com/dist/src
107 https://www.git-scm.com/
108 https://calibre-ebook.com/dist/src
109 https://github.com/kovidgoyal/calibre
110 https://bugs.launchpad.net/calibre
111 https://bugs.launchpad.net/calibre
Replace <username> above with your GitHub username. That will get your fork checked out locally.
• You can make changes and commit them whenever you like. When you are ready to have your work merged,
do a:
git push
You should also keep an eye on the calibre development forum115 . Before making major changes, you should discuss
them in the forum or contact Kovid directly (his email address is all over the source code).
Note: You must also get the calibre source code separately as described above.
Install calibre normally, using the Windows installer. Then open a Command Prompt and change to the previously
checked out calibre code directory. For example:
cd C:\Users\kovid\work\calibre
calibre is the directory that contains the src and resources sub-directories.
The next step is to set the environment variable CALIBRE_DEVELOP_FROM to the absolute path of the src directory.
So, following the example above, it would be C:\Users\kovid\work\calibre\src. Here is a short guide116
to setting environment variables on Windows.
112 https://github.com
113 https://help.github.com/articles/set-up-git
114 https://help.github.com/articles/generating-ssh-keys
115 https://www.mobileread.com/forums/forumdisplay.php?f=240
116 https://docs.python.org/using/windows.html#excursus-setting-environment-variables
Once you have set the environment variable, open a new command prompt and check that it was correctly set by using
the command:
echo %CALIBRE_DEVELOP_FROM%
Setting this environment variable means that calibre will now load all its Python code from the specified location.
That’s it! You are now ready to start hacking on the calibre code. For example, open the file
src\calibre\__init__.py in your favorite editor and add the line:
near the top of the file. Now run the command calibredb. The very first line of output should be Hello,
world!.
You can also setup a calibre development environment inside the free Microsoft Visual Studio, if you like, following
the instructions here117 .
Note: You must also get the calibre source code separately as described above.
Install calibre normally using the provided .dmg. Then open a Terminal and change to the previously checked out
calibre code directory, for example:
cd /Users/kovid/work/calibre
calibre is the directory that contains the src and resources sub-directories. The calibre command line tools are found
inside the calibre app bundle, in /Applications/calibre.app/Contents/MacOS you should add this di-
rectory to your PATH environment variable, if you want to run the command line tools easily.
The next step is to create a bash script that will set the environment variable CALIBRE_DEVELOP_FROM to the
absolute path of the src directory when running calibre in debug mode.
Create a plain text file:
#!/bin/sh
export CALIBRE_DEVELOP_FROM="/Users/kovid/work/calibre/src"
calibre-debug -g
Save this file as /usr/bin/calibre-develop, then set its permissions so that it can be executed:
chmod +x /usr/bin/calibre-develop
calibre-develop
You should see some diagnostic information in the Terminal window as calibre starts up, and you should see an asterisk
after the version number in the GUI window, indicating that you are running from source.
117 https://www.mobileread.com/forums/showthread.php?t=251201
Note: You must also get the calibre source code separately as described above.
calibre is primarily developed on Linux. You have two choices in setting up the development environment. You can
install the calibre binary as normal and use that as a runtime environment to do your development. This approach is
similar to that used in Windows and macOS. Alternatively, you can install calibre from source. Instructions for setting
up a development environment from source are in the INSTALL file in the source tree. Here we will address using the
binary as a runtime, which is the recommended method.
Install calibre using the binary installer. Then open a terminal and change to the previously checked out calibre code
directory, for example:
cd /home/kovid/work/calibre
calibre is the directory that contains the src and resources sub-directories.
The next step is to set the environment variable CALIBRE_DEVELOP_FROM to the absolute path of the src directory.
So, following the example above, it would be /home/kovid/work/calibre/src. How to set environment
variables depends on your Linux distribution and what shell you are using.
Once you have set the environment variable, open a new terminal and check that it was correctly set by using the
command:
echo $CALIBRE_DEVELOP_FROM
Setting this environment variable means that calibre will now load all its Python code from the specified location.
That’s it! You are now ready to start hacking on the calibre code. For example, open the file src/calibre/
__init__.py in your favorite editor and add the line:
near the top of the file. Now run the command calibredb. The very first line of output should be Hello,
world!.
The calibre source tree is very stable and rarely breaks, but if you feel the need to run from source on a separate test
library and run the released calibre version with your everyday library, you can achieve this easily using .bat files or
shell scripts to launch calibre. The example below shows how to do this on Windows using .bat files (the instructions
for other platforms are the same, just use a shell script instead of a .bat file)
To launch the release version of calibre with your everyday library:
calibre-normal.bat:
calibre-dev.bat:
set CALIBRE_DEVELOP_FROM=C:\path\to\calibre\checkout\src
calibre.exe "--with-library=C:\path\to\test\library folder"
Python is a dynamically typed language with excellent facilities for introspection. Kovid wrote the core calibre code
without once using a debugger. There are many strategies to debug calibre code:
This is Kovid’s favorite way to debug. Simply insert print statements at points of interest and run your program in the
terminal. For example, you can start the GUI from the terminal as:
calibre-debug -g
calibre-debug -w /path/to/file/to/be/viewed
calibre-debug -t /path/to/be/edited
You can insert the following two lines of code to start an interactive Python session at that point:
When running from the command line, this will start an interactive Python interpreter with access to all locally defined
variables (variables in the local scope). The interactive prompt even has TAB completion for object properties and you
can use the various Python facilities for introspection, such as dir(), type(), repr(), etc.
You can use the builtin Python debugger (pdb) as a remote debugger from the command line. First, start the remote
debugger at the point in the calibre code you are interested in, like this:
Then run calibre, either as normal, or using one of the calibre-debug commands described in the previous section.
Once the above point in the code is reached, calibre will freeze, waiting for the debugger to connect.
Now open a terminal or command prompt and use the following command to start the debugging session:
You can read about how to use the Python debugger in the Python stdlib docs for the pdb module118 .
118 https://docs.python.org/library/pdb.html#debugger-commands
Note: By default, the remote debugger will try to connect on port 4444. You can change it, by passing the
port parameter to both the set_trace() and the cli() functions above, like this: set_trace(port=1234) and
cli(port=1234).
Note: The Python debugger cannot handle multiple threads, so you have to call set_trace once per thread, each time
with a different port number.
It is possible to use the builtin debugger in your favorite Python IDE, if it supports remote debugging. The first
step is to add the calibre src checkout to the PYTHONPATH in your IDE. In other words, the directory you set as
CALIBRE_DEVELOP_FROM above, must also be in the PYTHONPATH of your IDE.
Then place the IDE’s remote debugger module into the src subdirectory of the calibre source code checkout. Add
whatever code is needed to launch the remote debugger to calibre at the point of interest, for example in the main
function. Then run calibre as normal. Your IDE should now be able to connect to the remote debugger running inside
calibre.
The calibre-debug command provides a couple of handy switches to execute your own code, with access to the
calibre modules:
is great for testing a little snippet of code on the command line. It works in the same way as the -c switch to the Python
interpreter:
calibre-debug myscript.py
can be used to execute your own Python script. It works in the same way as passing the script to the Python interpreter,
except that the calibre environment is fully initialized, so you can use all the calibre code in your script. To use
command line arguments with your script, use the form:
It is possible to directly use calibre functions/code in your Python project. Two ways exist to do this:
If you have a binary install of calibre, you can use the Python interpreter bundled with calibre, like this:
In addition to using the above technique, if you do a source install on Linux, you can also directly import calibre, as
follows:
import init_calibre
import calibre
print calibre.__version__
It is essential that you import the init_calibre module before any other calibre modules/packages as it sets up the
interpreter to run calibre code.
This API is thread safe (it uses a multiple reader, single writer locking scheme). You can access this API like this:
If you are in a calibre plugin that is part of the main calibre GUI, you get access to it like this instead:
db = self.gui.current_db.new_api
class calibre.db.cache.Cache(backend)
An in-memory cache of the metadata.db file from a calibre library. This class also serves as a threadsafe API
for accessing the database. The in-memory cache is maintained in normal form for maximum performance.
SQLITE is simply used as a way to read and write from metadata.db robustly. All table read-
ing/sorting/searching/caching logic is re-implemented. This was necessary for maximum performance and
flexibility.
add_books(books, add_duplicates=True, apply_import_tags=True, preserve_uuid=False,
run_hooks=True, dbapi=None)
Add the specified books to the library. Books should be an iterable of 2-tuples, each 2-tuple of the form
(mi, format_map) where mi is a Metadata object and format_map is a dictionary of the form {fmt:
path_or_stream}, for example: {'EPUB': '/path/to/file.epub'}.
Returns a pair of lists: ids, duplicates. ids contains the book ids for all newly created books in
the database. duplicates contains the (mi, format_map) for all books that already exist in the
database as per the simple duplicate detection heuristic used by has_book() (page 325).
add_custom_book_data(name, val_map, delete_first=False)
Add data for name where val_map is a map of book_ids to values. If delete_first is True, all previously
stored data for name will be removed.
add_format(book_id, fmt, stream_or_path, replace=True, run_hooks=True, dbapi=None)
Add a format to the specified book. Return True if the format was added successfully.
Parameters
• replace – If True replace existing format, otherwise if the format already exists, return
False.
• run_hooks – If True, file type plugins are run on the format before and after being
added.
• dbapi – Internal use only.
all_book_ids(type=<type ’frozenset’>)
Frozen set of all known book ids.
all_field_for(field, book_ids, default_value=None)
Same as field_for, except that it operates on multiple books at once
all_field_ids(name)
Frozen set of ids for all values in the field name.
all_field_names(field)
Frozen set of all fields names (should only be used for many-one and many-many fields)
author_data(author_ids=None)
Return author data as a dictionary with keys: name, sort, link
If no authors with the specified ids are found an empty dictionary is returned. If author_ids is None, data
for all authors is returned.
author_sort_from_authors(authors, key_func=<function lower>)
Given a list of authors, return the author_sort string for the authors, preferring the author sort associated
with the author over the computed string.
books_for_field(name, item_id)
Return all the books associated with the item identified by item_id, where the item belongs to the field
name.
Returned value is a set of book ids, or the empty set if the item or the field does not exist.
books_in_virtual_library(vl, search_restriction=None)
Return the set of books in the specified virtual library
copy_cover_to(book_id, dest, use_hardlink=False, report_file_size=None)
Copy the cover to the file like object dest. Returns False if no cover exists or dest is the same file as
the current cover. dest can also be a path in which case the cover is copied to it if and only if the path is
different from the current path (taking case sensitivity into account).
copy_format_to(book_id, fmt, dest, use_hardlink=False, report_file_size=None)
Copy the format fmt to the file like object dest. If the specified format does not exist, raises
NoSuchFormat error. dest can also be a path (to a file), in which case the format is copied to it, iff
the path is different from the current path (taking case sensitivity into account).
cover(book_id, as_file=False, as_image=False, as_path=False)
Return the cover image or None. By default, returns the cover as a bytestring.
WARNING: Using as_path will copy the cover to a temp file and return the path to the temp file. You
should delete the temp file when you are done with it.
Parameters
• as_file – If True return the image as an open file object (a SpooledTemporaryFile)
• as_image – If True return the image as a QImage object
• as_path – If True return the image as a path pointing to a temporary file
data_for_find_identical_books()
Return data that can be used to implement find_identical_books() (page 323) in a worker process
without access to the db. See db.utils for an implementation.
data_for_has_book()
Return data suitable for use in has_book() (page 325). This can be used for an implementation of
has_book() (page 325) in a worker process without access to the db.
delete_custom_book_data(name, book_ids=())
Delete data for name. By default deletes all data, if you only want to delete data for some book ids, pass
in a list of book ids.
embed_metadata(book_ids, only_fmts=None, report_error=None, report_progress=None)
Update metadata in all formats of the specified book_ids to current metadata in the database.
fast_field_for(field_obj, book_id, default_value=None)
Same as field_for, except that it avoids the extra lookup to get the field object
field_for(name, book_id, default_value=None)
Return the value of the field name for the book identified by book_id. If no such book exists or it has
no defined value for the field name or no such field exists, then default_value is returned.
default_value is not used for title, title_sort, authors, author_sort and series_index. This is because
these always have values in the db. default_value is used for all custom columns.
The returned value for is_multiple fields are always tuples, even when no values are found (in other words,
default_value is ignored). The exception is identifiers for which the returned value is always a dict. The
returned tuples are always in link order, that is, the order in which they were created.
field_ids_for(name, book_id)
Return the ids (as a tuple) for the values that the field name has on the book identified by book_id. If
there are no values, or no such book, or no such field, an empty tuple is returned.
find_identical_books(mi, search_restriction=u”, book_ids=None)
Finds books that have a superset of the authors in mi and the same title (title is fuzzy matched). See also
data_for_find_identical_books() (page 322).
format(book_id, fmt, as_file=False, as_path=False, preserve_filename=False)
Return the e-book format as a bytestring or None if the format doesn’t exist, or we don’t have permission
to write to the e-book file.
Parameters
• as_file – If True the e-book format is returned as a file object. Note that the file object
is a SpooledTemporaryFile, so if what you want to do is copy the format to another file,
use copy_format_to() (page 322) instead for performance.
• as_path – Copies the format file to a temp file and returns the path to the temp file
• preserve_filename – If True and returning a path the filename is the same as that
used in the library. Note that using this means that repeated calls yield the same temp file
(which is re-created each time)
format_abspath(book_id, fmt)
Return absolute path to the e-book file of format format. You should almost never use this, as it breaks the
threadsafe promise of this API. Instead use, copy_format_to() (page 322).
Currently used only in calibredb list, the viewer, edit book, compare_format to original format, open with,
bulk metadata edit and the catalogs (via get_data_as_dict()).
Apart from the viewer, open with and edit book, I don’t believe any of the others do any file write I/O with
the results of this call.
format_hash(book_id, fmt)
Return the hash of the specified format for the specified book. The kind of hash is backend dependent, but
is usually SHA-256.
get_usage_count_by_id(field)
Return a mapping of id to usage count for all values of the specified field, which must be a many-one or
many-many field.
has_book(mi)
Return True iff the database contains an entry with the same title as the passed in Metadata object. The
comparison is case-insensitive. See also data_for_has_book() (page 322).
has_format(book_id, fmt)
Return True iff the format exists on disk
has_id(book_id)
Return True iff the specified book_id exists in the db
init()
Initialize this cache with data from the backend.
multisort(fields, ids_to_sort=None, virtual_fields=None)
Return a list of sorted book ids. If ids_to_sort is None, all book ids are returned.
fields must be a list of 2-tuples of the form (field_name, ascending=True or False). The most significant
field is the first 2-tuple.
pref(name, default=None)
Return the value for the specified preference or the value specified as default if the preference is not
set.
read_backup(book_id)
Return the OPF metadata backup for the book as a bytestring or None if no such backup exists.
remove_books(book_ids, permanent=False)
Remove the books specified by the book_ids from the database and delete their format files. If
permanent is False, then the format files are placed in the recycle bin.
remove_formats(formats_map, db_only=False)
Remove the specified formats from the specified books.
Parameters
• formats_map – A mapping of book_id to a list of formats to be removed from the book.
• db_only – If True, only remove the record for the format from the db, do not delete the
actual format file from the filesystem.
remove_items(field, item_ids, restrict_to_book_ids=None)
Delete all items in the specified field with the specified ids. Returns the set of affected book ids.
restrict_to_book_ids is an optional set of books ids. If specified the items will only be removed
from those books.
rename_items(field, item_id_to_new_name_map, change_index=True, restrict_to_book_ids=None)
Rename items from a many-one or many-many field such as tags or series.
Parameters
• change_index – When renaming in a series-like field also change the series_index
values.
• restrict_to_book_ids – An optional set of book ids for which the rename is to be
performed, defaults to all books.
restore_book(book_id, mi, last_modified, path, formats)
Restore the book entry in the database for a book that already exists on the filesystem
restore_original_format(book_id, original_fmt)
Restore the specified format from the previously saved ORIGINAL_FORMAT, if any. Return True on
success. The ORIGINAL_FORMAT is deleted after a successful restore.
safe_read_lock
A safe read lock is a lock that does nothing if the thread already has a write lock, otherwise it acquires
a read lock. This is necessary to prevent DowngradeLockErrors, which can happen when updating the
search cache in the presence of composite columns. Updating the search cache holds an exclusive lock,
but searching a composite column involves reading field values via ProxyMetadata which tries to get a
shared lock. There may be other scenarios that trigger this as well.
This property returns a new lock object on every access. This lock object is not recursive (for performance)
and must only be used in a with statement as with cache.safe_read_lock: otherwise bad things
will happen.
save_original_format(book_id, fmt)
Save a copy of the specified format as ORIGINAL_FORMAT, overwriting any existing ORIGI-
NAL_FORMAT.
search(query, restriction=u”, virtual_fields=None, book_ids=None)
Search the database for the specified query, returning a set of matched book ids.
Parameters
• restriction – A restriction that is ANDed to the specified query. Note that restrictions
are cached, therefore the search for a AND b will be slower than a with restriction b.
• virtual_fields – Used internally (virtual fields such as on_device to search over).
• book_ids – If not None, a set of book ids for which books will be searched instead of
searching all books.
set_conversion_options(options, fmt=u’PIPE’)
options must be a map of the form {book_id:conversion_options}
set_cover(book_id_data_map)
Set the cover for this book. data can be either a QImage, QPixmap, file object or bytestring. It can also be
None, in which case any existing cover is removed.
set_field(name, book_id_to_val_map, allow_case_change=True, do_path_update=True)
Set the values of the field specified by name. Returns the set of all book ids that were affected by the
change.
Parameters
• book_id_to_val_map – Mapping of book_ids to values that should be applied.
• allow_case_change – If True, the case of many-one or many-many fields will be
changed. For example, if a book has the tag tag1 and you set the tag for another book to
Tag1 then the both books will have the tag Tag1 if allow_case_change is True, otherwise
they will both have the tag tag1.
• do_path_update – Used internally, you should never change it.
set_metadata(book_id, mi, ignore_errors=False, force_changes=False, set_title=True,
set_authors=True, allow_case_change=False)
Set metadata for the book id from the Metadata object mi
Setting force_changes=True will force set_metadata to update fields even if mi contains empty values. In
this case, ‘None’ is distinguished from ‘empty’. If mi.XXX is None, the XXX is not replaced, otherwise
it is. The tags, identifiers, and cover attributes are special cases. Tags and identifiers cannot be set to None
so they will always be replaced if force_changes is true. You must ensure that mi contains the values you
want the book to have. Covers are always changed if a new cover is provided, but are never deleted. Also
note that force_changes has no effect on setting title or authors.
set_pref(name, val)
Set the specified preference to the specified value. See also pref() (page 325).
tags_older_than(tag, delta=None, must_have_tag=None, must_have_authors=None)
Return the ids of all books having the tag tag that are older than the specified time. tag comparison is
case insensitive.
Parameters
• delta – A timedelta object or None. If None, then all ids with the tag are returned.
• must_have_tag – If not None the list of matches will be restricted to books that have
this tag
• must_have_authors – A list of authors. If not None the list of matches will be re-
stricted to books that have these authors (case insensitive).
user_categories_for_books(book_ids, proxy_metadata_map=None)
Return the user categories for the specified books. proxy_metadata_map is optional and is useful for a
performance boost, in contexts where a ProxyMetadata object for the books already exists. It should be a
mapping of book_ids to their corresponding ProxyMetadata objects.
If you are writing a plugin for the E-book editor, you get the current container for the book being edited like this:
• Clones: the container object supports efficient on-disk cloning, which is used to implement checkpoints
in the e-book editor. In order to make this work, you should never access files on the filesystem directly.
Instead, use raw_data() (page 330) or open() (page 329) to read/write to component files in the book.
When converting between hrefs and names use the methods provided by this class, they assume all hrefs are
quoted.
abspath_to_name(fullpath, root=None)
Convert an absolute path to a canonical name relative to root
Parameters root – The base directory. By default the root for this container object is used.
add_file(name, data, media_type=None, spine_index=None, modify_name_if_needed=False, pro-
cess_manifest_item=None)
Add a file to this container. Entries for the file are automatically created in the OPF manifest and spine (if
the file is a text document)
add_name_to_manifest(name, process_manifest_item=None)
Add an entry to the manifest for a file with the specified name. Returns the manifest id.
add_properties(name, *properties)
Add the specified properties to the manifest item identified by name.
apply_unique_properties(name, *properties)
Ensure that the specified properties are set on only the manifest item identified by name. You can pass
None as the name to remove the property from all items.
book_type = u'oeb'
The type of book (epub for EPUB files and azw3 for AZW3 files)
commit(outpath=None, keep_parsed=False)
Commit all dirtied parsed objects to the filesystem and write out the e-book file at outpath.
Parameters
• output – The path to write the saved e-book file to. If None, the path of the original
book file is used.
• keep_parsed – If True the parsed representations of committed items are kept in the
cache.
commit_item(name, keep_parsed=False)
Commit a parsed object to disk (it is serialized and written to the underlying file). If keep_parsed is
True the parsed representation is retained in the cache. See also: parsed() (page 330)
dirty(name)
Mark the parsed object corresponding to name as dirty. See also: parsed() (page 330).
exists(name)
True iff a file/directory corresponding to the canonical name exists. Note that this function suffers from
the limitations of the underlying OS filesystem, in particular case (in)sensitivity. So on a case insensi-
tive filesystem this will return True even if the case of name is different from the case of the underlying
filesystem file. See also has_name() (page 329)
filesize(name)
Return the size in bytes of the file represented by the specified canonical name. Automatically handles
dirtied parsed objects. See also: parsed() (page 330)
generate_item(name, id_prefix=None, media_type=None, unique_href=True)
Add an item to the manifest with href derived from the given name. Ensures uniqueness of href and id
automatically. Returns generated item.
get_file_path_for_processing(name, allow_modification=True)
Similar to open() except that it returns a file path, instead of an open file object.
guide_type_map
Mapping of guide type to canonical name
has_name(name)
Return True iff a file with the same canonical name as that specified exists. Unlike exists() (page 328)
this method is always case-sensitive.
href_to_name(href, base=None)
Convert an href (relative to base) to a name. base must be a name or None, in which case self.root is used.
insert_into_xml(parent, item, index=None)
Insert item into parent (or append if index is None), fixing indentation. Only works with self closing items.
is_dir = False
If this container represents an unzipped book (a directory)
iterlinks(name, get_line_numbers=True)
Iterate over all links in name. If get_line_numbers is True the yields results of the form (link, line_number,
offset). Where line_number is the line_number at which the link occurs and offset is the number of
characters from the start of the line. Note that offset could actually encompass several lines if not zero.
make_name_unique(name)
Ensure that name does not already exist in this book. If it does, return a modified version that does not
exist.
manifest_has_name(name)
Return True if the manifest has an entry corresponding to name
manifest_id_map
Mapping of manifest id to canonical names
manifest_items_of_type(predicate)
The names of all manifest items whose media-type matches predicate. predicate can be a set, a list, a string
or a function taking a single argument, which will be called with the media-type.
manifest_items_with_property(property_name)
All manifest items that have the specified property
manifest_type_map
Mapping of manifest media-type to list of canonical names of that media-type
mi
The metadata of this book as a Metadata object. Note that this object is constructed on the fly every time
this property is requested, so use it sparingly.
name_to_abspath(name)
Convert a canonical name to an absolute OS dependant path
name_to_href(name, base=None)
Convert a name to a href relative to base, which must be a name or None in which case self.root is used as
the base
names_that_must_not_be_changed
Set of names that must never be renamed. Depends on the e-book file format.
names_that_must_not_be_removed
Set of names that must never be deleted from the container. Depends on the e-book file format.
names_that_need_not_be_manifested
Set of names that are allowed to be missing from the manifest. Depends on the e-book file format.
open(name, mode=u’rb’)
Open the file pointed to by name for direct read/write. Note that this will commit the file if it is dirtied
and remove it from the parse cache. You must finish with this file before accessing the parsed version of it
again, or bad things will happen.
opf
The parsed OPF file
opf_get_or_create(name)
Convenience method to either return the first XML element with the specified name or create it under the
opf:package element and then return it, if it does not already exist.
opf_version
The version set on the OPF’s <package> element
opf_version_parsed
The version set on the OPF’s <package> element as a tuple of integers
opf_xpath(expr)
Convenience method to evaluate an XPath expression on the OPF file, has the opf: and dc: namespace
prefixes pre-defined.
parsed(name)
Return a parsed representation of the file specified by name. For HTML and XML files an lxml tree
is returned. For CSS files a css_parser stylesheet is returned. Note that parsed objects are cached for
performance. If you make any changes to the parsed object, you must call dirty() (page 328) so that
the container knows to update the cache. See also replace() (page 330).
raw_data(name, decode=True, normalize_to_nfc=True)
Return the raw data corresponding to the file specified by name
Parameters
• decode – If True and the file has a text based MIME type, decode it and return a unicode
object instead of raw bytes.
• normalize_to_nfc – If True the returned unicode object is normalized to the NFC
normal form as is required for the EPUB and AZW3 file formats.
relpath(path, base=None)
Convert an absolute path (with os separators) to a path relative to base (defaults to self.root). The relative
path is not a name. Use abspath_to_name() (page 328) for that.
remove_from_spine(spine_items, remove_if_no_longer_in_spine=True)
Remove the specified items (by canonical name) from the spine. If
remove_if_no_longer_in_spine is True, the items are also deleted from the book, not just
from the spine.
remove_from_xml(item)
Removes item from parent, fixing indentation (works only with self closing items)
remove_item(name, remove_from_guide=True)
Remove the item identified by name from this container. This removes all references to the item in the
OPF manifest, guide and spine as well as from any internal caches.
rename(current_name, new_name)
Renames a file from current_name to new_name. It automatically rebases all links inside the file if the
directory the file is in changes. Note however, that links are not updated in the other files that could
reference this file. This is for performance, such updates should be done once, in bulk.
replace(name, obj)
Replace the parsed object corresponding to name with obj, which must be a similar object, i.e. an lxml
tree for HTML/XML or a css_parser stylesheet for a CSS file.
replace_links(name, replace_func)
Replace all links in name using replace_func, which must be a callable that accepts a URL and returns the
replaced URL. It must also have a ‘replaced’ attribute that is set to True if any actual replacement is done.
Convenient ways of creating such callables are using the LinkReplacer and LinkRebaser classes.
serialize_item(name)
Convert a parsed object (identified by canonical name) into a bytestring. See parsed() (page 330).
set_spine(spine_items)
Set the spine to be spine_items where spine_items is an iterable of the form (name, linear). Will raise an
error if one of the names is not present in the manifest.
spine_items
An iterator yielding the path for every item in the books’ spine. See also: spine_iter (page 331) and
spine_items (page 331).
spine_iter
An iterator that yields item, name is_linear for every item in the books’ spine. item is the lxml element,
name is the canonical file name and is_linear is True if the item is linear. See also: spine_names
(page 331) and spine_items (page 331).
spine_names
An iterator yielding name and is_linear for every item in the books’ spine. See also: spine_iter
(page 331) and spine_items (page 331).
calibre.ebooks.oeb.polish.replace.replace_links(container, link_map,
frag_map=<function <lambda>>,
replace_in_opf=False)
Replace links to files in the container. Will iterate over all files in the container and change the specified links in
them.
Parameters
• link_map – A mapping of old canonical name to new canonical name. For example:
{'images/old.png': 'images/new.png'}
• frag_map – A callable that takes two arguments (name, anchor) and returns a new
anchor. This is useful if you need to change the anchors in HTML files. By default, it does
nothing.
• replace_in_opf – If False, links are not replaced in the OPF file.
calibre.ebooks.oeb.polish.replace.rename_files(container, file_map)
Rename files in the container, automatically updating all links to them.
Parameters file_map – A mapping of old canonical name to new canonical name, for example:
{'text/chapter1.html': 'chapter1.html'}.
calibre.ebooks.oeb.polish.replace.get_recommended_folders(container, names)
Return the folders that are recommended for the given filenames. The recommendation is based on where the
majority of files of the same type are located in the container. If no files of a particular type are present, the
recommended folder is assumed to be the folder containing the OPF file.
calibre.ebooks.oeb.polish.pretty.fix_html(container, raw)
Fix any parsing errors in the HTML represented as a string in raw. Fixing is done using the HTML5 parsing
algorithm.
calibre.ebooks.oeb.polish.pretty.fix_all_html(container)
Fix any parsing errors in all HTML files in the container. Fixing is done using the HTML5 parsing algorithm.
calibre.ebooks.oeb.polish.pretty.pretty_html(container, name, raw)
Pretty print the HTML represented as a string in raw
calibre.ebooks.oeb.polish.pretty.pretty_css(container, name, raw)
Pretty print the CSS represented as a string in raw
calibre.ebooks.oeb.polish.pretty.pretty_xml(container, name, raw)
Pretty print the XML represented as a string in raw. If name is the name of the OPF, extra OPF-specific prettying
is performed.
calibre.ebooks.oeb.polish.pretty.pretty_all(container)
Pretty print all HTML/CSS/XML files in the container
calibre.ebooks.oeb.polish.jacket.remove_jacket(container)
Remove an existing jacket, if any. Returns False if no existing jacket was found.
calibre.ebooks.oeb.polish.jacket.add_or_replace_jacket(container)
Either create a new jacket from the book’s metadata or replace an existing jacket. Returns True if an existing
jacket was replaced.
Managing covers
calibre.ebooks.oeb.polish.toc.from_xpaths(container, xpaths)
Generate a Table of Contents from a list of XPath expressions. Each expression in the list corresponds to a
level of the generate ToC. For example: ['//h:h1', '//h:h2', '//h:h3'] will generate a three level
Table of Contents from the <h1>, <h2> and <h3> tags.
calibre.ebooks.oeb.polish.toc.from_links(container)
Generate a Table of Contents from links in the book.
calibre.ebooks.oeb.polish.toc.from_files(container)
Generate a Table of Contents from files in the book.
calibre.ebooks.oeb.polish.toc.create_inline_toc(container, title=None)
Create an inline (HTML) Table of Contents from an existing NCX Table of Contents.
Parameters title – The title for this table of contents.
class calibre.gui2.tweak_book.plugin.Tool
Bases: object
The base class for individual tools in an Edit Book plugin. Useful members include:
• self.plugin: A reference to the calibre.customize.Plugin (page 228) object to which this
tool belongs.
• self. boss (page 334)
• self. gui (page 334)
Methods that must be overridden in sub classes:
• create_action() (page 335)
• register_shortcut() (page 335)
name = None
Set this to a unique name it will be used as a key
allowed_in_toolbar = True
If True the user can choose to place this tool in the plugins toolbar
allowed_in_menu = True
If True the user can choose to place this tool in the plugins menu
toolbar_button_popup_mode = u'delayed'
The popup mode for the menu (if any) of the toolbar button. Possible values are ‘delayed’, ‘instant’,
‘button’
boss
The calibre.gui2.tweak_book.boss.Boss (page 335) object. Used to control the user inter-
face.
gui
The main window of the user interface
current_container
Return the current calibre.ebooks.oeb.polish.container.Container (page 327) object
that represents the book being edited.
register_shortcut(qaction, unique_name, default_keys=(), short_text=None, description=None,
**extra_data)
Register a keyboard shortcut that will trigger the specified qaction. This keyboard shortcut will become
automatically customizable by the user in the Keyboard section of the editor preferences.
Parameters
• qaction – A QAction object, it will be triggered when the configured key combination
is pressed by the user.
• unique_name – A unique name for this shortcut/action. It will be used internally, it
must not be shared by any other actions in this plugin.
• default_keys – A list of the default keyboard shortcuts. If not specified no default
shortcuts will be set. If the shortcuts specified here conflict with either builtin short-
cuts or shortcuts from user configuration/other plugins, they will be ignored. In that
case, users will have to configure the shortcuts manually via Preferences. For example:
default_keys=('Ctrl+J', 'F9').
• short_text – An optional short description of this action. If not specified the text from
the QAction will be used.
• description – An optional longer description of this action, it will be used in the
preferences entry for this shortcut.
create_action(for_toolbar=True)
Create a QAction that will be added to either the plugins toolbar or the plugins menu depending on
for_toolbar. For example:
See also:
Method register_shortcut() (page 335).
The e-book editor’s user interface is controlled by a single global Boss object. This has many useful methods that can
be used in plugin code to perform common tasks.
add_savepoint(msg)
Create a restore checkpoint with the name specified as msg
apply_container_update_to_gui(mark_as_modified=True)
Update all the components of the user interface to reflect the latest data in the current book container.
Parameters mark_as_modified – If True, the book will be marked as modified, so the user
will be prompted to save it when quitting.
close_editor(name)
Close the editor that is editing the file specified by name
commit_all_editors_to_container()
Commit any changes that the user has made to files open in editors to the container. You should call this
method before performing any actions on the current container
currently_editing
Return the name of the file being edited currently or None if no file is being edited
edit_file(name, syntax=None, use_template=None)
Open the file specified by name in an editor
Parameters
• syntax – The media type of the file, for example, 'text/html'. If not specified it is
guessed from the file extension.
• use_template – A template to initialize the opened editor with
open_book(path=None, edit_file=None, clear_notify_data=True, open_folder=False)
Open the e-book at path for editing. Will show an error if the e-book is not in a supported format or the
current book has unsaved changes.
Parameters edit_file – The name of a file inside the newly opened book to start editing.
Can also be a list of names.
rewind_savepoint()
Undo the previous creation of a restore checkpoint, useful if you create a checkpoint, then abort the oper-
ation with no changes
save_book()
Save the book. Saving is performed in the background
set_modified()
Mark the book as having been modified
show_current_diff(allow_revert=True, to_container=None)
Show the changes to the book from its last checkpointed state
Parameters
• allow_revert – If True the diff dialog will have a button to allow the user to revert all
changes
• to_container – A container object to compare the current container to. If None, the
previously checkpointed container is used
show_editor(name)
Show the editor that is editing the file specified by name
sync_preview_to_editor()
Sync the position of the preview panel to the current cursor position in the current editor
Digital rights management (DRM) is a generic term for access control technologies that can be used by hardware
manufacturers, publishers, copyright holders and individuals to try to impose limitations on the usage of digital content
and devices. It is also, sometimes, disparagingly described as Digital Restrictions Management. The term is used
to describe any technology which inhibits uses (legitimate or otherwise) of digital content that were not desired or
foreseen by the content provider. The term generally doesn’t refer to other forms of copy protection which can be
circumvented without modifying the file or device, such as serial numbers or key-files. It can also refer to restrictions
associated with specific instances of digital works or devices. DRM technologies attempt to control use of digital
media by preventing access, copying or conversion to other formats by end users. See wikipedia119 .
When you buy an e-book with DRM you don’t really own it but have purchased the permission to use it in a manner
dictated to you by the seller. DRM limits what you can do with e-books you have “bought”. Often people who buy
books with DRM are unaware of the extent of these restrictions. These restrictions prevent you from reformatting the
e-book to your liking, including making stylistic changes like adjusting the font sizes, although there is software that
empowers you to do such things for non DRM books. People are often surprised that an e-book they have bought in
a particular format cannot be converted to another format if the e-book has DRM. So if you have an Amazon Kindle
and buy a book sold by Barnes and Nobles, you should know that if that e-book has DRM you will not be able to read
it on your Kindle. Notice that I am talking about a book you buy, not steal or pirate but BUY.
Publishers of DRMed e-books argue that the DRM is all for the sake of authors and to protect their artistic integrity
and prevent piracy. But DRM does NOT prevent piracy. People who want to pirate content or use pirated content still
do it and succeed. The three major DRM schemes for e-books today are run by Amazon, Adobe and Barnes and Noble
and all three DRM schemes have been cracked. All DRM does is inconvenience legitimate users. It can be argued that
it actually harms authors as people who would have bought the book choose to find a pirated version as they are not
119 https://en.wikipedia.org/wiki/Digital_rights_management
339
calibre User Manual, Release 4.21.0
willing to put up with DRM. Those that would pirate in the absence of DRM do so in its presence as well. To reiterate,
the key point is that DRM does not prevent piracy. So DRM is not only pointless and harmful to buyers of e-books
but also a waste of money.
Although digital content can be used to make information as well as creative works easily available to everyone and
empower humanity, this is not in the interests of some publishers who want to steer people away from this possibility
of freedom simply to maintain their relevance in world developing so fast that they cant keep up.
calibre is open source software while DRM by its very nature is closed. If calibre were to support opening or viewing
DRM files it could be trivially modified to be used as a tool for DRM removal which is illegal under today’s laws.
Open source software and DRM are a clash of principles. While DRM is all about controlling the user open source
software is about empowering the user. The two simply can not coexist.
We firmly believe that authors and other content providers should be compensated for their efforts, but DRM is not
the way to go about it. We are developing this database of DRM-free e-books from various sources to help you find
DRM-free alternatives and to help independent authors and publishers of DRM-free e-books publicize their content.
We hope you will find this useful and we request that you do not pirate the content made available to you here.
As somebody who reads and buys e-books you can help fight DRM. Do not buy e-books with DRM. There are some
publishers who publish DRM-free e-books. Make an effort to see if they carry the e-book you are looking for. If
you like books by certain independent authors that sell DRM-free e-books and you can afford it make donations to
them. This is money well spent as their e-books tend to be cheaper (there may be exceptions) than the ones you
would buy from publishers of DRMed books and would probably work on all devices you own in the future saving
you the cost of buying the e-book again. Do not discourage publishers and authors of DRM-free e-books by pirating
their content. Content providers deserve compensation for their efforts. Do not punish them for trying to make your
reading experience better by making available DRM-free e-books. In the long run this is detrimental to you. If
you have bought books from sellers that carry both DRMed as well as DRM-free books, not knowing if they carry
DRM or not make it a point to leave a comment or review on the website informing future buyers of its DRM status.
Many sellers do not think it important to clearly indicate to their buyers if an e-book carries DRM or not. Here
<https://www.defectivebydesign.org/guide/ebooks> you will find a Guide to DRM-free living.
Glossary
RSS RSS (Really Simple Syndication) is a web feed format that is used to publish frequently updated content, like
news articles, blog posts, etc. It is a format that is particularly suited to being read by computers, and is therefore
the preferred way of getting content from the web into an e-book. There are many other feed formats in use
on the Internet, and calibre understands most of them. In particular, it has good support for the ATOM format,
which is commonly used for blogs.
recipe A recipe is a set of instructions that teach calibre how to convert an online news source, such as a magazine
or a blog, into an e-book. A recipe is essentially Python120 code. As such, it is capable of converting arbitrarily
complex news sources into e-books. At the simplest level, it is just a set of variables, such as URLs, that give
calibre enough information to go out onto the Internet and download the news.
HTML HTML (Hyper Text Mark-Up Language), a subset of Standard Generalized Mark-Up Language (SGML) for
electronic publishing, is the specific standard used for the World Wide Web.
CSS CSS (Cascading Style Sheets) is a language used to describe how an HTML document should be rendered (visual
styling).
API API (Application Programming Interface) is a source code interface that a library provides to support requests
for services to be made of it by computer programs.
LRF LRF The e-book format that is read by the SONY e-book readers.
URL URL (Uniform Resource Locator) for example: http://example.com
regexp Regular expressions provide a concise and flexible means for identifying strings of text of interest, such as
particular characters, words, or patterns of characters. See regexp syntax121 for the syntax of regular expressions
used in Python.
120 https://www.python.org
121 https://docs.python.org/library/re.html
341
calibre User Manual, Release 4.21.0
c
calibre.customize, 227
calibre.customize.conversion, 235
calibre.db.cache, 321
calibre.devices.interface, 237
calibre.ebooks.metadata.book.base, 184
calibre.ebooks.metadata.sources.base,
232
calibre.ebooks.oeb.polish.container, 327
calibre.ebooks.oeb.polish.cover, 333
calibre.ebooks.oeb.polish.css, 333
calibre.ebooks.oeb.polish.jacket, 332
calibre.ebooks.oeb.polish.pretty, 332
calibre.ebooks.oeb.polish.replace, 331
calibre.ebooks.oeb.polish.split, 332
calibre.ebooks.oeb.polish.toc, 334
calibre.gui2.tweak_book.boss, 335
calibre.gui2.tweak_book.plugin.Tool, 334
calibre.utils.formatter_functions, 172
calibre.web.feeds.news, 47
343
calibre User Manual, Release 4.21.0
Symbols -attachment, -a
-access-log calibre-smtp command line option,
calibre-server command line option, 270
266 -auth-mode
-add calibre-server command line option,
calibredb-add command line option, 267
274 -author-sort
-add-plugin, -a ebook-convert command line option,
calibre-customize command line 289
option, 264 ebook-meta command line option, 306
-add-simple-plugin -authors
calibre-debug command line option, ebook-convert command line option,
265 289
-add-soft-hyphens, -H -authors, -a
ebook-polish command line option, calibredb-add command line option,
307 273
-ajax-timeout ebook-meta command line option, 306
calibre-server command line option, fetch-ebook-metadata command line
266 option, 309
-all -auto-reload
calibredb-backup_metadata command calibre-server command line option,
line option, 281 267
calibredb-export command line -ban-after
option, 276 calibre-server command line option,
-allowed-plugin, -p 267
fetch-ebook-metadata command line -ban-for
option, 309 calibre-server command line option,
-append, -a 267
calibredb-set_custom command line -base-dir, -d
option, 279 web2disk command line option, 312
-as-opf -base-font-size
calibredb-show_metadata command ebook-convert command line option,
line option, 275 284
-ascending -book-list-mode
calibredb-list command line option, calibre-server command line option,
272 267
-asciiize -book-producer
ebook-convert command line option, ebook-convert command line option,
284 289
-book-producer, -k
345
calibre User Manual, Release 4.21.0
346 Index
calibre User Manual, Release 4.21.0
Index 347
calibre User Manual, Release 4.21.0
348 Index
calibre User Manual, Release 4.21.0
-explode-book, -x -fork, -f
calibre-debug command line option, calibre-smtp command line option,
265 270
-export-all-calibre-data -format, -f
calibre-debug command line option, ebook-convert-pdb-output command
265 line option, 301
-extra-css -formats
ebook-convert command line option, calibredb-export command line
285 option, 276
-extract-to -formatting-type
ebook-convert-azw3-output command ebook-convert-txt-input command
line option, 296 line option, 295
ebook-convert-docx-output command -from-opf
line option, 297 ebook-meta command line option, 306
ebook-convert-epub-output command -full-image-depth
line option, 297 ebook-convert-pml-output command
ebook-convert-html-output command line option, 303
line option, 298 -full-screen, -fullscreen, -f
ebook-convert-mobi-output command ebook-viewer command line option,
line option, 300 309
-fb2-genre -generate-authors
ebook-convert-fb2-output command calibredb-catalog command line
line option, 298 option, 277
-field, -f -generate-descriptions
calibredb-set_metadata command calibredb-catalog command line
line option, 275 option, 277
-fields, -f -generate-genres
calibredb-list command line option, calibredb-catalog command line
272 option, 277
-filter-css -generate-recently-added
ebook-convert command line option, calibredb-catalog command line
285 option, 277
-filter-regexp -generate-series
web2disk command line option, 312 calibredb-catalog command line
-flow-size option, 277
ebook-convert-epub-output command -generate-titles
line option, 297 calibredb-catalog command line
-font-size-mapping option, 277
ebook-convert command line option, -genre-source-field
285 calibredb-catalog command line
-for-machine option, 277
calibredb-list command line option, -get-cover
273 ebook-meta command line option, 306
-force, -f -gui, -g
calibredb-remove_custom_column calibre-debug command line option,
command line option, 279 265
-force-max-line-length -gui-debug
ebook-convert-txt-output command calibre-debug command line option,
line option, 304 265
ebook-convert-txtz-output command -header
line option, 304 ebook-convert-lrf-output command
-force-reload line option, 299
ebook-viewer command line option, -header-format
309 ebook-convert-lrf-output command
Index 349
calibre User Manual, Release 4.21.0
350 Index
calibre User Manual, Release 4.21.0
Index 351
calibre User Manual, Release 4.21.0
352 Index
calibre User Manual, Release 4.21.0
Index 353
calibre User Manual, Release 4.21.0
354 Index
calibre User Manual, Release 4.21.0
Index 355
calibre User Manual, Release 4.21.0
356 Index
calibre User Manual, Release 4.21.0
Index 357
calibre User Manual, Release 4.21.0
358 Index
calibre User Manual, Release 4.21.0
Index 359
calibre User Manual, Release 4.21.0
360 Index
calibre User Manual, Release 4.21.0
bre.utils.formatter_functions), 176 C
BuiltinRawList (class in cali- Cache (class in calibre.db.cache), 321
bre.utils.formatter_functions), 177 cached_cover_url_is_reliable (cali-
BuiltinRe (class in calibre.utils.formatter_functions), bre.ebooks.metadata.sources.base.Source
183 attribute), 232
BuiltinReGroup (class in cali- calibre command line option
bre.utils.formatter_functions), 183 -detach, 263
BuiltinSelect (class in cali- -help, -h, 263
bre.utils.formatter_functions), 179 -ignore-plugins, 263
BuiltinSeriesSort (class in cali- -no-update-check, 263
bre.utils.formatter_functions), 177 -shutdown-running-calibre, -s, 263
BuiltinShorten (class in cali- -start-in-tray, 264
bre.utils.formatter_functions), 183 -verbose, -v, 264
BuiltinStrcat (class in cali- -version, 264
bre.utils.formatter_functions), 183 -with-library, 264
BuiltinStrcatMax (class in cali- calibre-customize command line option
bre.utils.formatter_functions), 183 -add-plugin, -a, 264
BuiltinStrcmp (class in cali- -build-plugin, -b, 264
bre.utils.formatter_functions), 182 -customize-plugin, 264
BuiltinStrInList (class in cali- -disable-plugin, 264
bre.utils.formatter_functions), 179 -enable-plugin, 264
BuiltinStrlen (class in cali- -help, -h, 264
bre.utils.formatter_functions), 183 -list-plugins, -l, 264
BuiltinSubitems (class in cali- -remove-plugin, -r, 264
bre.utils.formatter_functions), 180 -version, 264
BuiltinSublist (class in cali- calibre-debug command line option
bre.utils.formatter_functions), 181 -add-simple-plugin, 265
BuiltinSubstr (class in cali- -command, -c, 265
bre.utils.formatter_functions), 184 -debug-device-driver, -d, 265
BuiltinSubtract (class in cali- -default-programs, 265
bre.utils.formatter_functions), 172 -diff, 265
BuiltinSwapAroundArticles (class in cali- -edit-book, -t, 265
bre.utils.formatter_functions), 184 -exec-file, -e, 265
BuiltinSwapAroundComma (class in cali- -explode-book, -x, 265
bre.utils.formatter_functions), 184 -export-all-calibre-data, 265
BuiltinSwitch (class in cali- -gui, -g, 265
bre.utils.formatter_functions), 178 -gui-debug, 265
BuiltinTemplate (class in cali- -help, -h, 265
bre.utils.formatter_functions), 181 -implode-book, -i, 266
BuiltinTest (class in cali- -import-calibre-data, 266
bre.utils.formatter_functions), 178 -inspect-mobi, -m, 266
BuiltinTitlecase (class in cali- -paths, 266
bre.utils.formatter_functions), 182 -reinitialize-db, 266
BuiltinToday (class in cali- -run-plugin, -r, 266
bre.utils.formatter_functions), 173 -shutdown-running-calibre, -s, 266
BuiltinTransliterate (class in cali- -subset-font, -f, 266
bre.utils.formatter_functions), 184 -test-build, 266
BuiltinUppercase (class in cali- -version, 266
bre.utils.formatter_functions), 182 -viewer, -w, 266
BuiltinUserCategories (class in cali- calibre-server command line option
bre.utils.formatter_functions), 177 -access-log, 266
BuiltinVirtualLibraries (class in cali- -ajax-timeout, 266
bre.utils.formatter_functions), 177 -auth-mode, 267
-auto-reload, 267
Index 361
calibre User Manual, Release 4.21.0
362 Index
calibre User Manual, Release 4.21.0
Index 363
calibre User Manual, Release 4.21.0
364 Index
calibre User Manual, Release 4.21.0
Index 365
calibre User Manual, Release 4.21.0
366 Index
calibre User Manual, Release 4.21.0
Index 367
calibre User Manual, Release 4.21.0
368 Index
calibre User Manual, Release 4.21.0
Index 369
calibre User Manual, Release 4.21.0
370 Index
calibre User Manual, Release 4.21.0
Index 371
calibre User Manual, Release 4.21.0
372 Index
calibre User Manual, Release 4.21.0
Index 373
calibre User Manual, Release 4.21.0
374 Index
calibre User Manual, Release 4.21.0
Index 375
calibre User Manual, Release 4.21.0
376 Index
calibre User Manual, Release 4.21.0
Index 377
calibre User Manual, Release 4.21.0
V
VENDOR_ID (calibre.devices.interface.DevicePlugin at-
tribute), 237
version (calibre.customize.Plugin attribute), 228
VIRTUAL_BOOK_EXTENSION_MESSAGE (cali-
bre.devices.interface.DevicePlugin attribute),
238
VIRTUAL_BOOK_EXTENSIONS (cali-
bre.devices.interface.DevicePlugin attribute),
238
W
WANTS_UPDATED_THUMBNAILS (cali-
bre.devices.interface.DevicePlugin attribute),
237
web2disk command line option
-base-dir, -d, 312
-delay, 312
-dont-download-stylesheets, 312
-encoding, 312
-filter-regexp, 312
-help, -h, 312
-match-regexp, 312
-max-files, -n, 312
-max-recursions, -r, 312
-timeout, -t, 312
-verbose, 312
-version, 312
WINDOWS_CARD_A_MEM (cali-
bre.devices.usbms.device.Device attribute),
245
WINDOWS_CARD_B_MEM (cali-
bre.devices.usbms.device.Device attribute),
245
WINDOWS_MAIN_MEM (cali-
bre.devices.usbms.device.Device attribute),
245
378 Index