# SOME DESCRIPTIVE TITLE. # Copyright (C) Kovid Goyal # This file is distributed under the same license as the calibre package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: calibre 9.15.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2026-09-18 07:37+0530\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../../home/kovid/work/calibre/manual/develop.rst:4 msgid "Setting up a calibre development environment" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:6 msgid "calibre is completely open source, licensed under the `GNU GPL v3 `_. 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 `Python `_ with some C/C++ code for speed and system interfacing. Note that calibre requires at least Python 3.8." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:14 msgid "Contents" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:17 msgid "Design philosophy" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:19 msgid "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 :doc:`generated/en/cli-index`." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:24 msgid "The modular design of calibre is expressed via ``Plugins``. There is a :ref:`tutorial ` on writing calibre plugins. For example, adding support for a new device to calibre typically involves writing fewer than 100 lines of code in the form of a device driver plugin. You can browse the `built-in drivers `_. Similarly, adding support for new conversion formats involves writing input/output format plugins. Another example of the modular design is the :ref:`recipe system ` for fetching news. For more examples of plugins designed to add features to calibre, see the `Index of plugins `_." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:34 msgid "Code layout" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:36 msgid "All the calibre Python code is in the ``calibre`` package. This package contains the following main sub-packages" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:38 msgid "devices - All the device drivers. Just look through some of the built-in drivers to get an idea for how they work." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:40 msgid "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." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:43 msgid "e-books - All the e-book conversion/metadata code. A good starting point is ``calibre.ebooks.conversion.cli`` which is the module powering the :command:`ebook-convert` command. The conversion process is controlled via ``conversion.plumber``. The format independent code is all in ``ebooks.oeb`` and the format dependent code is in ``ebooks.format_name``." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:47 msgid "Metadata reading, writing, and downloading is all in ``ebooks.metadata``" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:48 msgid "Conversion happens in a pipeline, for the structure of the pipeline, see :ref:`conversion-introduction`. The pipeline consists of an input plugin, various transforms and an output plugin. The code that constructs and drives the pipeline is in :file:`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 :file:`oeb/transforms/*.py`. And the input and output plugins live in :file:`conversion/plugins/*.py`." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:58 msgid "E-book editing happens using a different container object. It is documented in :ref:`polish_api`." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:61 msgid "db - The database back-end. See :ref:`db_api` for the interface to the calibre library." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:63 msgid "Content server: ``srv`` is the calibre Content server." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:65 msgid "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``." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:67 msgid "If you want to locate the entry points for all the various calibre executables, look at the ``entry_points`` structure in `linux.py `_." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:71 msgid "If you need help understanding the code, post in the `development forum `_ and you will most likely get help from one of calibre's many developers." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:75 msgid "Getting the code" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:77 msgid "You can get the calibre source code in two ways, using a version control system or directly downloading a :website_base:`tarball `." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:80 msgid "calibre uses `Git `_, 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::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:86 msgid "On Windows you will need the complete path name, that will be something like :file:`C:\\\\Program Files\\\\Git\\\\git.exe`." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:88 msgid "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)." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:91 msgid "If you want to get the code faster, the source code for the latest release is always available as an :website_base:`archive `." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:94 msgid "To update a branch to the latest code, use the command::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:98 msgid "You can also browse the code at `GitHub `_." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:101 msgid "Submitting your changes to be included" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:103 msgid "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 tracker `_. To do this, make your changes, then run::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:111 msgid "This will create a :file:`my-changes` file in the current folder, simply attach that to a ticket on the calibre `bug tracker `_. 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::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:119 msgid "To send the last *n* commits, replace *1* with *n*, for example, for the last 3 commits::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:124 msgid "Be careful to not include merges when using ``HEAD~n``." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:126 msgid "If you plan to do a lot of development on calibre, then the best method is to create a `GitHub `__ account. Below is a basic guide to setting up your own fork of calibre in a way that will allow you to submit pull requests for inclusion into the main calibre repository:" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:131 msgid "Setup git on your machine as described in this article: `Setup Git `_" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:132 msgid "Setup ssh keys for authentication to GitHub, as described here: `Generating SSH keys `_" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:133 msgid "Go to https://github.com/kovidgoyal/calibre and click the :guilabel:`Fork` button." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:134 msgid "In a Terminal do::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:139 msgid "Replace above with your GitHub username. That will get your fork checked out locally." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:140 msgid "You can make changes and commit them whenever you like. When you are ready to have your work merged, do a::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:144 msgid "and go to ``https://github.com//calibre`` and click the :guilabel:`Pull Request` button to generate a pull request that can be merged." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:145 msgid "You can update your local copy with code from the main repo at any time by doing::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:150 msgid "You should also keep an eye on the calibre `development forum `_. Before making major changes, you should discuss them in the forum or contact Kovid directly (his email address is all over the source code)." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:156 msgid "Windows development environment" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:158 #: ../../../home/kovid/work/calibre/manual/develop.rst:192 #: ../../../home/kovid/work/calibre/manual/develop.rst:229 msgid "You must also get the calibre source code separately as described above." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:160 msgid "Install calibre normally, using the `Windows installer `__. Then open a Command Prompt and change to the previously checked out calibre code folder. For example::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:165 #: ../../../home/kovid/work/calibre/manual/develop.rst:241 msgid "calibre is the folder that contains the src and resources sub-folders." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:167 msgid "The next step is to set the environment variable ``CALIBRE_DEVELOP_FROM`` to the absolute path of the src folder. So, following the example above, it would be ``C:\\Users\\kovid\\work\\calibre\\src``. `Here is a short guide `_ to setting environment variables on Windows." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:172 msgid "Once you have set the environment variable, open a new command prompt and check that it was correctly set by using the command::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:177 #: ../../../home/kovid/work/calibre/manual/develop.rst:260 msgid "Setting this environment variable means that calibre will now load all its Python code from the specified location." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:179 msgid "That's it! You are now ready to start hacking on the calibre code. For example, open the file :file:`src\\\\calibre\\\\__init__.py` in your favorite editor and add the line::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:184 #: ../../../home/kovid/work/calibre/manual/develop.rst:267 msgid "near the top of the file. Now run the command :command:`calibredb`. The very first line of output should be ``Hello, world!``." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:186 msgid "You can also setup a calibre development environment inside the free Microsoft Visual Studio, if you like, following the instructions `here `_." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:190 msgid "macOS development environment" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:194 msgid "Install calibre normally using the `provided .dmg `__. Then open a Terminal and change to the previously checked out calibre code folder, for example::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:199 msgid "calibre is the folder that contains the src and resources sub-folders. The calibre command line tools are found inside the calibre app bundle, in :file:`/Applications/calibre.app/Contents/MacOS` you should add this folder to your PATH environment variable, if you want to run the command line tools easily." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:205 msgid "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 folder when running calibre in debug mode." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:208 msgid "Create a plain text file::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:214 msgid "Save this file as :file:`/usr/local/bin/calibre-develop`, then set its permissions so that it can be executed::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:218 msgid "Once you have done this, run::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:222 msgid "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." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:227 msgid "Linux development environment" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:231 msgid "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." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:237 msgid "Install calibre using the `binary installer `_. Then open a terminal and change to the previously checked out calibre code folder, for example::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:243 msgid "The next step is to set the environment variable ``CALIBRE_DEVELOP_FROM`` to the absolute path of the src folder. 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." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:248 msgid "It is recommended to use the binary installer provided from upstream. Should you insist on using a package provided by your distribution, use the ``CALIBRE_PYTHON_PATH`` and ``CALIBRE_RESOURCES_PATH`` variables instead. You can get these by running ``calibre-debug --paths``. But note that distribution calibre packages are often terminally broken and are completely unsupported." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:255 msgid "Once you have set the environment variable, open a new terminal and check that it was correctly set by using the command::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:262 msgid "That's it! You are now ready to start hacking on the calibre code. For example, open the file :file:`src/calibre/__init__.py` in your favorite editor and add the line::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:270 msgid "Having separate \"normal\" and \"development\" calibre installs on the same computer" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:272 msgid "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)" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:277 msgid "To launch the release version of calibre with your everyday library:" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:279 msgid "calibre-normal.bat::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:283 msgid "calibre-dev.bat::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:290 msgid "Debugging tips" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:292 msgid "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:" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:297 msgid "Using print statements" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:299 msgid "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::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:304 msgid "Similarly, you can start the E-book viewer as::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:308 msgid "The e-book editor can be started as::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:313 msgid "Using an interactive Python interpreter" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:315 msgid "You can insert the following two lines of code to start an interactive Python session at that point::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:320 msgid "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 :kbd:`Tab` completion for object properties and you can use the various Python facilities for introspection, such as :func:`dir`, :func:`type`, :func:`repr`, etc." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:326 msgid "Using the Python debugger as a remote debugger" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:328 msgid "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::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:335 msgid "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." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:339 msgid "Now open a terminal or command prompt and use the following command to start the debugging session::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:344 msgid "You can read about how to use the Python debugger in the `Python stdlib docs for the pdb module `_." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:348 msgid "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)``." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:354 msgid "The Python debugger cannot handle multiple threads, so you have to call set_trace once per thread, each time with a different port number." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:358 msgid "Using the debugger in your favorite Python IDE" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:360 msgid "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 folder you set as ``CALIBRE_DEVELOP_FROM`` above, must also be in the ``PYTHONPATH`` of your IDE." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:365 msgid "Then place the IDE's remote debugger module into the :file:`src` sub-folder 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." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:372 msgid "Executing arbitrary scripts in the calibre Python environment" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:374 msgid "The :command:`calibre-debug` command provides a couple of handy switches to execute your own code, with access to the calibre modules::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:379 msgid "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::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:383 msgid "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::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:388 msgid "The ``--`` causes all subsequent arguments to be passed to your script." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:392 msgid "Running the calibre test suite" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:394 msgid "The calibre test suite can be run by::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:400 msgid "Using calibre in your projects" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:402 msgid "It is possible to directly use calibre functions/code in your Python project. Two ways exist to do this:" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:405 msgid "Binary install of calibre" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:407 msgid "If you have a binary install of calibre, you can use the Python interpreter bundled with calibre, like this::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:412 msgid "Source install on Linux" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:414 msgid "In addition to using the above technique, if you do a source install on Linux, you can also directly import calibre, as follows::" msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:422 msgid "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." msgstr "" #: ../../../home/kovid/work/calibre/manual/develop.rst:426 msgid "API documentation for various parts of calibre" msgstr ""