Debian Codegraph @

translations/manual/develop.pot

raw
1 # SOME DESCRIPTIVE TITLE.
2 # Copyright (C) Kovid Goyal
3 # This file is distributed under the same license as the calibre package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5 #
6 #, fuzzy
7 msgid ""
8 msgstr ""
9 "Project-Id-Version: calibre 9.15.0\n"
10 "Report-Msgid-Bugs-To: \n"
11 "POT-Creation-Date: 2026-09-18 07:37+0530\n"
12 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
13 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
14 "Language-Team: LANGUAGE <[email protected]>\n"
15 "MIME-Version: 1.0\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: 8bit\n"
18
19 #: ../../../home/kovid/work/calibre/manual/develop.rst:4
20 msgid "Setting up a calibre development environment"
21 msgstr ""
22
23 #: ../../../home/kovid/work/calibre/manual/develop.rst:6
24 msgid "calibre is completely open source, licensed under the `GNU GPL v3 <https://www.gnu.org/licenses/gpl.html>`_. 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 <https://www.python.org>`_ with some C/C++ code for speed and system interfacing. Note that calibre requires at least Python 3.8."
25 msgstr ""
26
27 #: ../../../home/kovid/work/calibre/manual/develop.rst:14
28 msgid "Contents"
29 msgstr ""
30
31 #: ../../../home/kovid/work/calibre/manual/develop.rst:17
32 msgid "Design philosophy"
33 msgstr ""
34
35 #: ../../../home/kovid/work/calibre/manual/develop.rst:19
36 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`."
37 msgstr ""
38
39 #: ../../../home/kovid/work/calibre/manual/develop.rst:24
40 msgid "The modular design of calibre is expressed via ``Plugins``. There is a :ref:`tutorial <customize>` 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 <https://github.com/kovidgoyal/calibre/tree/master/src/calibre/devices>`_. Similarly, adding support for new conversion formats involves writing input/output format plugins. Another example of the modular design is the :ref:`recipe system <news>` for fetching news. For more examples of plugins designed to add features to calibre, see the `Index of plugins <https://www.mobileread.com/forums/showthread.php?p=1362767#post1362767>`_."
41 msgstr ""
42
43 #: ../../../home/kovid/work/calibre/manual/develop.rst:34
44 msgid "Code layout"
45 msgstr ""
46
47 #: ../../../home/kovid/work/calibre/manual/develop.rst:36
48 msgid "All the calibre Python code is in the ``calibre`` package. This package contains the following main sub-packages"
49 msgstr ""
50
51 #: ../../../home/kovid/work/calibre/manual/develop.rst:38
52 msgid "devices - All the device drivers. Just look through some of the built-in drivers to get an idea for how they work."
53 msgstr ""
54
55 #: ../../../home/kovid/work/calibre/manual/develop.rst:40
56 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."
57 msgstr ""
58
59 #: ../../../home/kovid/work/calibre/manual/develop.rst:43
60 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``."
61 msgstr ""
62
63 #: ../../../home/kovid/work/calibre/manual/develop.rst:47
64 msgid "Metadata reading, writing, and downloading is all in ``ebooks.metadata``"
65 msgstr ""
66
67 #: ../../../home/kovid/work/calibre/manual/develop.rst:48
68 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`."
69 msgstr ""
70
71 #: ../../../home/kovid/work/calibre/manual/develop.rst:58
72 msgid "E-book editing happens using a different container object. It is documented in :ref:`polish_api`."
73 msgstr ""
74
75 #: ../../../home/kovid/work/calibre/manual/develop.rst:61
76 msgid "db - The database back-end. See :ref:`db_api` for the interface to the calibre library."
77 msgstr ""
78
79 #: ../../../home/kovid/work/calibre/manual/develop.rst:63
80 msgid "Content server: ``srv`` is the calibre Content server."
81 msgstr ""
82
83 #: ../../../home/kovid/work/calibre/manual/develop.rst:65
84 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``."
85 msgstr ""
86
87 #: ../../../home/kovid/work/calibre/manual/develop.rst:67
88 msgid "If you want to locate the entry points for all the various calibre executables, look at the ``entry_points`` structure in `linux.py <https://github.com/kovidgoyal/calibre/blob/master/src/calibre/linux.py>`_."
89 msgstr ""
90
91 #: ../../../home/kovid/work/calibre/manual/develop.rst:71
92 msgid "If you need help understanding the code, post in the `development forum <https://www.mobileread.com/forums/forumdisplay.php?f=240>`_ and you will most likely get help from one of calibre's many developers."
93 msgstr ""
94
95 #: ../../../home/kovid/work/calibre/manual/develop.rst:75
96 msgid "Getting the code"
97 msgstr ""
98
99 #: ../../../home/kovid/work/calibre/manual/develop.rst:77
100 msgid "You can get the calibre source code in two ways, using a version control system or directly downloading a :website_base:`tarball <dist/src>`."
101 msgstr ""
102
103 #: ../../../home/kovid/work/calibre/manual/develop.rst:80
104 msgid "calibre uses `Git <https://www.git-scm.com/>`_, 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::"
105 msgstr ""
106
107 #: ../../../home/kovid/work/calibre/manual/develop.rst:86
108 msgid "On Windows you will need the complete path name, that will be something like :file:`C:\\\\Program Files\\\\Git\\\\git.exe`."
109 msgstr ""
110
111 #: ../../../home/kovid/work/calibre/manual/develop.rst:88
112 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)."
113 msgstr ""
114
115 #: ../../../home/kovid/work/calibre/manual/develop.rst:91
116 msgid "If you want to get the code faster, the source code for the latest release is always available as an :website_base:`archive <dist/src>`."
117 msgstr ""
118
119 #: ../../../home/kovid/work/calibre/manual/develop.rst:94
120 msgid "To update a branch to the latest code, use the command::"
121 msgstr ""
122
123 #: ../../../home/kovid/work/calibre/manual/develop.rst:98
124 msgid "You can also browse the code at `GitHub <https://github.com/kovidgoyal/calibre>`_."
125 msgstr ""
126
127 #: ../../../home/kovid/work/calibre/manual/develop.rst:101
128 msgid "Submitting your changes to be included"
129 msgstr ""
130
131 #: ../../../home/kovid/work/calibre/manual/develop.rst:103
132 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 <https://bugs.launchpad.net/calibre>`_. To do this, make your changes, then run::"
133 msgstr ""
134
135 #: ../../../home/kovid/work/calibre/manual/develop.rst:111
136 msgid "This will create a :file:`my-changes` file in the current folder, simply attach that to a ticket on the calibre `bug tracker <https://bugs.launchpad.net/calibre>`_. 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::"
137 msgstr ""
138
139 #: ../../../home/kovid/work/calibre/manual/develop.rst:119
140 msgid "To send the last *n* commits, replace *1* with *n*, for example, for the last 3 commits::"
141 msgstr ""
142
143 #: ../../../home/kovid/work/calibre/manual/develop.rst:124
144 msgid "Be careful to not include merges when using ``HEAD~n``."
145 msgstr ""
146
147 #: ../../../home/kovid/work/calibre/manual/develop.rst:126
148 msgid "If you plan to do a lot of development on calibre, then the best method is to create a `GitHub <https://github.com>`__ 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:"
149 msgstr ""
150
151 #: ../../../home/kovid/work/calibre/manual/develop.rst:131
152 msgid "Setup git on your machine as described in this article: `Setup Git <https://help.github.com/articles/set-up-git>`_"
153 msgstr ""
154
155 #: ../../../home/kovid/work/calibre/manual/develop.rst:132
156 msgid "Setup ssh keys for authentication to GitHub, as described here: `Generating SSH keys <https://help.github.com/articles/generating-ssh-keys>`_"
157 msgstr ""
158
159 #: ../../../home/kovid/work/calibre/manual/develop.rst:133
160 msgid "Go to https://github.com/kovidgoyal/calibre and click the :guilabel:`Fork` button."
161 msgstr ""
162
163 #: ../../../home/kovid/work/calibre/manual/develop.rst:134
164 msgid "In a Terminal do::"
165 msgstr ""
166
167 #: ../../../home/kovid/work/calibre/manual/develop.rst:139
168 msgid "Replace <username> above with your GitHub username. That will get your fork checked out locally."
169 msgstr ""
170
171 #: ../../../home/kovid/work/calibre/manual/develop.rst:140
172 msgid "You can make changes and commit them whenever you like. When you are ready to have your work merged, do a::"
173 msgstr ""
174
175 #: ../../../home/kovid/work/calibre/manual/develop.rst:144
176 msgid "and go to ``https://github.com/<username>/calibre`` and click the :guilabel:`Pull Request` button to generate a pull request that can be merged."
177 msgstr ""
178
179 #: ../../../home/kovid/work/calibre/manual/develop.rst:145
180 msgid "You can update your local copy with code from the main repo at any time by doing::"
181 msgstr ""
182
183 #: ../../../home/kovid/work/calibre/manual/develop.rst:150
184 msgid "You should also keep an eye on the calibre `development forum <https://www.mobileread.com/forums/forumdisplay.php?f=240>`_. Before making major changes, you should discuss them in the forum or contact Kovid directly (his email address is all over the source code)."
185 msgstr ""
186
187 #: ../../../home/kovid/work/calibre/manual/develop.rst:156
188 msgid "Windows development environment"
189 msgstr ""
190
191 #: ../../../home/kovid/work/calibre/manual/develop.rst:158
192 #: ../../../home/kovid/work/calibre/manual/develop.rst:192
193 #: ../../../home/kovid/work/calibre/manual/develop.rst:229
194 msgid "You must also get the calibre source code separately as described above."
195 msgstr ""
196
197 #: ../../../home/kovid/work/calibre/manual/develop.rst:160
198 msgid "Install calibre normally, using the `Windows installer <https://calibre-ebook.com/download_windows>`__. Then open a Command Prompt and change to the previously checked out calibre code folder. For example::"
199 msgstr ""
200
201 #: ../../../home/kovid/work/calibre/manual/develop.rst:165
202 #: ../../../home/kovid/work/calibre/manual/develop.rst:241
203 msgid "calibre is the folder that contains the src and resources sub-folders."
204 msgstr ""
205
206 #: ../../../home/kovid/work/calibre/manual/develop.rst:167
207 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 <https://docs.python.org/using/windows.html#excursus-setting-environment-variables>`_ to setting environment variables on Windows."
208 msgstr ""
209
210 #: ../../../home/kovid/work/calibre/manual/develop.rst:172
211 msgid "Once you have set the environment variable, open a new command prompt and check that it was correctly set by using the command::"
212 msgstr ""
213
214 #: ../../../home/kovid/work/calibre/manual/develop.rst:177
215 #: ../../../home/kovid/work/calibre/manual/develop.rst:260
216 msgid "Setting this environment variable means that calibre will now load all its Python code from the specified location."
217 msgstr ""
218
219 #: ../../../home/kovid/work/calibre/manual/develop.rst:179
220 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::"
221 msgstr ""
222
223 #: ../../../home/kovid/work/calibre/manual/develop.rst:184
224 #: ../../../home/kovid/work/calibre/manual/develop.rst:267
225 msgid "near the top of the file. Now run the command :command:`calibredb`. The very first line of output should be ``Hello, world!``."
226 msgstr ""
227
228 #: ../../../home/kovid/work/calibre/manual/develop.rst:186
229 msgid "You can also setup a calibre development environment inside the free Microsoft Visual Studio, if you like, following the instructions `here <https://www.mobileread.com/forums/showthread.php?t=251201>`_."
230 msgstr ""
231
232 #: ../../../home/kovid/work/calibre/manual/develop.rst:190
233 msgid "macOS development environment"
234 msgstr ""
235
236 #: ../../../home/kovid/work/calibre/manual/develop.rst:194
237 msgid "Install calibre normally using the `provided .dmg <https://calibre-ebook.com/download_osx>`__. Then open a Terminal and change to the previously checked out calibre code folder, for example::"
238 msgstr ""
239
240 #: ../../../home/kovid/work/calibre/manual/develop.rst:199
241 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."
242 msgstr ""
243
244 #: ../../../home/kovid/work/calibre/manual/develop.rst:205
245 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."
246 msgstr ""
247
248 #: ../../../home/kovid/work/calibre/manual/develop.rst:208
249 msgid "Create a plain text file::"
250 msgstr ""
251
252 #: ../../../home/kovid/work/calibre/manual/develop.rst:214
253 msgid "Save this file as :file:`/usr/local/bin/calibre-develop`, then set its permissions so that it can be executed::"
254 msgstr ""
255
256 #: ../../../home/kovid/work/calibre/manual/develop.rst:218
257 msgid "Once you have done this, run::"
258 msgstr ""
259
260 #: ../../../home/kovid/work/calibre/manual/develop.rst:222
261 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."
262 msgstr ""
263
264 #: ../../../home/kovid/work/calibre/manual/develop.rst:227
265 msgid "Linux development environment"
266 msgstr ""
267
268 #: ../../../home/kovid/work/calibre/manual/develop.rst:231
269 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."
270 msgstr ""
271
272 #: ../../../home/kovid/work/calibre/manual/develop.rst:237
273 msgid "Install calibre using the `binary installer <https://calibre-ebook.com/download_linux>`_. Then open a terminal and change to the previously checked out calibre code folder, for example::"
274 msgstr ""
275
276 #: ../../../home/kovid/work/calibre/manual/develop.rst:243
277 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."
278 msgstr ""
279
280 #: ../../../home/kovid/work/calibre/manual/develop.rst:248
281 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."
282 msgstr ""
283
284 #: ../../../home/kovid/work/calibre/manual/develop.rst:255
285 msgid "Once you have set the environment variable, open a new terminal and check that it was correctly set by using the command::"
286 msgstr ""
287
288 #: ../../../home/kovid/work/calibre/manual/develop.rst:262
289 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::"
290 msgstr ""
291
292 #: ../../../home/kovid/work/calibre/manual/develop.rst:270
293 msgid "Having separate \"normal\" and \"development\" calibre installs on the same computer"
294 msgstr ""
295
296 #: ../../../home/kovid/work/calibre/manual/develop.rst:272
297 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)"
298 msgstr ""
299
300 #: ../../../home/kovid/work/calibre/manual/develop.rst:277
301 msgid "To launch the release version of calibre with your everyday library:"
302 msgstr ""
303
304 #: ../../../home/kovid/work/calibre/manual/develop.rst:279
305 msgid "calibre-normal.bat::"
306 msgstr ""
307
308 #: ../../../home/kovid/work/calibre/manual/develop.rst:283
309 msgid "calibre-dev.bat::"
310 msgstr ""
311
312 #: ../../../home/kovid/work/calibre/manual/develop.rst:290
313 msgid "Debugging tips"
314 msgstr ""
315
316 #: ../../../home/kovid/work/calibre/manual/develop.rst:292
317 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:"
318 msgstr ""
319
320 #: ../../../home/kovid/work/calibre/manual/develop.rst:297
321 msgid "Using print statements"
322 msgstr ""
323
324 #: ../../../home/kovid/work/calibre/manual/develop.rst:299
325 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::"
326 msgstr ""
327
328 #: ../../../home/kovid/work/calibre/manual/develop.rst:304
329 msgid "Similarly, you can start the E-book viewer as::"
330 msgstr ""
331
332 #: ../../../home/kovid/work/calibre/manual/develop.rst:308
333 msgid "The e-book editor can be started as::"
334 msgstr ""
335
336 #: ../../../home/kovid/work/calibre/manual/develop.rst:313
337 msgid "Using an interactive Python interpreter"
338 msgstr ""
339
340 #: ../../../home/kovid/work/calibre/manual/develop.rst:315
341 msgid "You can insert the following two lines of code to start an interactive Python session at that point::"
342 msgstr ""
343
344 #: ../../../home/kovid/work/calibre/manual/develop.rst:320
345 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."
346 msgstr ""
347
348 #: ../../../home/kovid/work/calibre/manual/develop.rst:326
349 msgid "Using the Python debugger as a remote debugger"
350 msgstr ""
351
352 #: ../../../home/kovid/work/calibre/manual/develop.rst:328
353 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::"
354 msgstr ""
355
356 #: ../../../home/kovid/work/calibre/manual/develop.rst:335
357 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."
358 msgstr ""
359
360 #: ../../../home/kovid/work/calibre/manual/develop.rst:339
361 msgid "Now open a terminal or command prompt and use the following command to start the debugging session::"
362 msgstr ""
363
364 #: ../../../home/kovid/work/calibre/manual/develop.rst:344
365 msgid "You can read about how to use the Python debugger in the `Python stdlib docs for the pdb module <https://docs.python.org/library/pdb.html#debugger-commands>`_."
366 msgstr ""
367
368 #: ../../../home/kovid/work/calibre/manual/develop.rst:348
369 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)``."
370 msgstr ""
371
372 #: ../../../home/kovid/work/calibre/manual/develop.rst:354
373 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."
374 msgstr ""
375
376 #: ../../../home/kovid/work/calibre/manual/develop.rst:358
377 msgid "Using the debugger in your favorite Python IDE"
378 msgstr ""
379
380 #: ../../../home/kovid/work/calibre/manual/develop.rst:360
381 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."
382 msgstr ""
383
384 #: ../../../home/kovid/work/calibre/manual/develop.rst:365
385 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."
386 msgstr ""
387
388 #: ../../../home/kovid/work/calibre/manual/develop.rst:372
389 msgid "Executing arbitrary scripts in the calibre Python environment"
390 msgstr ""
391
392 #: ../../../home/kovid/work/calibre/manual/develop.rst:374
393 msgid "The :command:`calibre-debug` command provides a couple of handy switches to execute your own code, with access to the calibre modules::"
394 msgstr ""
395
396 #: ../../../home/kovid/work/calibre/manual/develop.rst:379
397 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::"
398 msgstr ""
399
400 #: ../../../home/kovid/work/calibre/manual/develop.rst:383
401 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::"
402 msgstr ""
403
404 #: ../../../home/kovid/work/calibre/manual/develop.rst:388
405 msgid "The ``--`` causes all subsequent arguments to be passed to your script."
406 msgstr ""
407
408 #: ../../../home/kovid/work/calibre/manual/develop.rst:392
409 msgid "Running the calibre test suite"
410 msgstr ""
411
412 #: ../../../home/kovid/work/calibre/manual/develop.rst:394
413 msgid "The calibre test suite can be run by::"
414 msgstr ""
415
416 #: ../../../home/kovid/work/calibre/manual/develop.rst:400
417 msgid "Using calibre in your projects"
418 msgstr ""
419
420 #: ../../../home/kovid/work/calibre/manual/develop.rst:402
421 msgid "It is possible to directly use calibre functions/code in your Python project. Two ways exist to do this:"
422 msgstr ""
423
424 #: ../../../home/kovid/work/calibre/manual/develop.rst:405
425 msgid "Binary install of calibre"
426 msgstr ""
427
428 #: ../../../home/kovid/work/calibre/manual/develop.rst:407
429 msgid "If you have a binary install of calibre, you can use the Python interpreter bundled with calibre, like this::"
430 msgstr ""
431
432 #: ../../../home/kovid/work/calibre/manual/develop.rst:412
433 msgid "Source install on Linux"
434 msgstr ""
435
436 #: ../../../home/kovid/work/calibre/manual/develop.rst:414
437 msgid "In addition to using the above technique, if you do a source install on Linux, you can also directly import calibre, as follows::"
438 msgstr ""
439
440 #: ../../../home/kovid/work/calibre/manual/develop.rst:422
441 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."
442 msgstr ""
443
444 #: ../../../home/kovid/work/calibre/manual/develop.rst:426
445 msgid "API documentation for various parts of calibre"
446 msgstr ""