Debian Codegraph @

translations/manual/pl/develop.po

raw
1 # SOME DESCRIPTIVE TITLE.
2 # Copyright (C) Kovid Goyal
3 # This file is distributed under the same license as the calibre package.
4 #
5 # Translators:
6 # Marcin Malinowski <[email protected]>, 2015
7 # Przemysław Siekiera <[email protected]>, 2018
8 msgid ""
9 msgstr ""
10 "Project-Id-Version: calibre\n"
11 "Report-Msgid-Bugs-To: \n"
12 "POT-Creation-Date: 2022-02-17 05:40+0000\n"
13 "PO-Revision-Date: 2022-02-16 05:39+0000\n"
14 "Last-Translator: Kovid Goyal <[email protected]>\n"
15 "Language-Team: Polish (http://www.transifex.com/calibre/calibre/language/pl/)\n"
16 "MIME-Version: 1.0\n"
17 "Content-Type: text/plain; charset=UTF-8\n"
18 "Content-Transfer-Encoding: 8bit\n"
19 "Language: pl\n"
20 "Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
21
22 #: ../../__w/calibre/calibre/manual/develop.rst:4
23 msgid "Setting up a calibre development environment"
24 msgstr "Konfigurowanie środowiska programistycznego dla calibre"
25
26 #: ../../__w/calibre/calibre/manual/develop.rst:6
27 msgid ""
28 "calibre is completely open source, licensed under the `GNU GPL v3 "
29 "<https://www.gnu.org/licenses/gpl.html>`_. This means that you are free to "
30 "download and modify the program to your heart's content. In this section, "
31 "you will learn how to get a calibre development environment set up on the "
32 "operating system of your choice. calibre is written primarily in `Python "
33 "<https://www.python.org>`_ with some C/C++ code for speed and system "
34 "interfacing. Note that calibre requires at least Python 3.8."
35 msgstr ""
36
37 #: ../../__w/calibre/calibre/manual/develop.rst:14
38 msgid "Contents"
39 msgstr "Spis treści"
40
41 #: ../../__w/calibre/calibre/manual/develop.rst:17
42 msgid "Design philosophy"
43 msgstr ""
44
45 #: ../../__w/calibre/calibre/manual/develop.rst:19
46 msgid ""
47 "calibre has its roots in the Unix world, which means that its design is "
48 "highly modular. The modules interact with each other via well defined "
49 "interfaces. This makes adding new features and fixing bugs in calibre very "
50 "easy, resulting in a frenetic pace of development. Because of its roots, "
51 "calibre has a comprehensive command line interface for all its functions, "
52 "documented in :doc:`generated/en/cli-index`."
53 msgstr ""
54
55 #: ../../__w/calibre/calibre/manual/develop.rst:24
56 msgid ""
57 "The modular design of calibre is expressed via ``Plugins``. There is a "
58 ":ref:`tutorial <customize>` on writing calibre plugins. For example, adding "
59 "support for a new device to calibre typically involves writing less than a "
60 "100 lines of code in the form of a device driver plugin. You can browse the "
61 "`built-in drivers "
62 "<https://github.com/kovidgoyal/calibre/tree/master/src/calibre/devices>`_. "
63 "Similarly, adding support for new conversion formats involves writing "
64 "input/output format plugins. Another example of the modular design is the "
65 ":ref:`recipe system <news>` for fetching news. For more examples of plugins "
66 "designed to add features to calibre, see the `Index of plugins "
67 "<https://www.mobileread.com/forums/showthread.php?p=1362767#post1362767>`_."
68 msgstr ""
69
70 #: ../../__w/calibre/calibre/manual/develop.rst:34
71 msgid "Code layout"
72 msgstr ""
73
74 #: ../../__w/calibre/calibre/manual/develop.rst:36
75 msgid ""
76 "All the calibre python code is in the ``calibre`` package. This package "
77 "contains the following main sub-packages"
78 msgstr ""
79
80 #: ../../__w/calibre/calibre/manual/develop.rst:38
81 msgid ""
82 "devices - All the device drivers. Just look through some of the built-in "
83 "drivers to get an idea for how they work."
84 msgstr ""
85
86 #: ../../__w/calibre/calibre/manual/develop.rst:40
87 msgid ""
88 "For details, see: ``devices.interface`` which defines the interface "
89 "supported by device drivers and ``devices.usbms`` which defines a generic "
90 "driver that connects to a USBMS device. All USBMS based drivers in calibre "
91 "inherit from it."
92 msgstr ""
93
94 #: ../../__w/calibre/calibre/manual/develop.rst:43
95 msgid ""
96 "e-books - All the e-book conversion/metadata code. A good starting point is"
97 " ``calibre.ebooks.conversion.cli`` which is the module powering the "
98 ":command:`ebook-convert` command. The conversion process is controlled via "
99 "``conversion.plumber``. The format independent code is all in ``ebooks.oeb``"
100 " and the format dependent code is in ``ebooks.format_name``."
101 msgstr ""
102
103 #: ../../__w/calibre/calibre/manual/develop.rst:47
104 msgid ""
105 "Metadata reading, writing, and downloading is all in ``ebooks.metadata``"
106 msgstr ""
107
108 #: ../../__w/calibre/calibre/manual/develop.rst:48
109 msgid ""
110 "Conversion happens in a pipeline, for the structure of the pipeline, see "
111 ":ref:`conversion-introduction`. The pipeline consists of an input plugin, "
112 "various transforms and an output plugin. The code that constructs and drives"
113 " the pipeline is in :file:`plumber.py`. The pipeline works on a "
114 "representation of an e-book that is like an unzipped epub, with manifest, "
115 "spine, toc, guide, html content, etc. The class that manages this "
116 "representation is OEBBook in ``ebooks.oeb.base``. The various "
117 "transformations that are applied to the book during conversions live in "
118 ":file:`oeb/transforms/*.py`. And the input and output plugins live in "
119 ":file:`conversion/plugins/*.py`."
120 msgstr ""
121
122 #: ../../__w/calibre/calibre/manual/develop.rst:58
123 msgid ""
124 "E-book editing happens using a different container object. It is documented "
125 "in :ref:`polish_api`."
126 msgstr ""
127
128 #: ../../__w/calibre/calibre/manual/develop.rst:61
129 msgid ""
130 "db - The database back-end. See :ref:`db_api` for the interface to the "
131 "calibre library."
132 msgstr ""
133
134 #: ../../__w/calibre/calibre/manual/develop.rst:63
135 msgid "Content server: ``srv`` is the calibre Content server."
136 msgstr ""
137
138 #: ../../__w/calibre/calibre/manual/develop.rst:65
139 msgid ""
140 "gui2 - The Graphical User Interface. GUI initialization happens in "
141 "``gui2.main`` and ``gui2.ui``. The e-book-viewer is in ``gui2.viewer``. The "
142 "e-book editor is in ``gui2.tweak_book``."
143 msgstr ""
144
145 #: ../../__w/calibre/calibre/manual/develop.rst:67
146 msgid ""
147 "If you want to locate the entry points for all the various calibre "
148 "executables, look at the ``entry_points`` structure in `linux.py "
149 "<https://github.com/kovidgoyal/calibre/blob/master/src/calibre/linux.py>`_."
150 msgstr ""
151
152 #: ../../__w/calibre/calibre/manual/develop.rst:71
153 msgid ""
154 "If you need help understanding the code, post in the `development forum "
155 "<https://www.mobileread.com/forums/forumdisplay.php?f=240>`_ and you will "
156 "most likely get help from one of calibre's many developers."
157 msgstr ""
158
159 #: ../../__w/calibre/calibre/manual/develop.rst:75
160 msgid "Getting the code"
161 msgstr ""
162
163 #: ../../__w/calibre/calibre/manual/develop.rst:77
164 msgid ""
165 "You can get the calibre source code in two ways, using a version control "
166 "system or directly downloading a :website_base:`tarball <dist/src>`."
167 msgstr ""
168
169 #: ../../__w/calibre/calibre/manual/develop.rst:80
170 msgid ""
171 "calibre uses `Git <https://www.git-scm.com/>`_, a distributed version "
172 "control system. Git is available on all the platforms calibre supports. "
173 "After installing Git, you can get the calibre source code with the command::"
174 msgstr ""
175
176 #: ../../__w/calibre/calibre/manual/develop.rst:86
177 msgid ""
178 "On Windows you will need the complete path name, that will be something like"
179 " :file:`C:\\\\Program Files\\\\Git\\\\git.exe`."
180 msgstr ""
181
182 #: ../../__w/calibre/calibre/manual/develop.rst:88
183 msgid ""
184 "calibre is a very large project with a very long source control history, so "
185 "the above can take a while (10 mins to an hour depending on your internet "
186 "speed)."
187 msgstr ""
188
189 #: ../../__w/calibre/calibre/manual/develop.rst:91
190 msgid ""
191 "If you want to get the code faster, the source code for the latest release "
192 "is always available as an :website_base:`archive <dist/src>`."
193 msgstr ""
194
195 #: ../../__w/calibre/calibre/manual/develop.rst:94
196 msgid "To update a branch to the latest code, use the command::"
197 msgstr "Aby zaktualizować gałąź ostatniego kodu, użyj komendy: "
198
199 #: ../../__w/calibre/calibre/manual/develop.rst:98
200 msgid ""
201 "You can also browse the code at `GitHub "
202 "<https://github.com/kovidgoyal/calibre>`_."
203 msgstr ""
204
205 #: ../../__w/calibre/calibre/manual/develop.rst:101
206 msgid "Submitting your changes to be included"
207 msgstr ""
208
209 #: ../../__w/calibre/calibre/manual/develop.rst:103
210 msgid ""
211 "If you only plan to make a few small changes, you can make your changes and "
212 "create a \"merge directive\" which you can then attach to a ticket in the "
213 "calibre `bug tracker <https://bugs.launchpad.net/calibre>`_. To do this, "
214 "make your changes, then run::"
215 msgstr ""
216
217 #: ../../__w/calibre/calibre/manual/develop.rst:111
218 msgid ""
219 "This will create a :file:`my-changes` file in the current folder, simply "
220 "attach that to a ticket on the calibre `bug tracker "
221 "<https://bugs.launchpad.net/calibre>`_. Note that this will include *all* "
222 "the commits you have made. If you only want to send some commits, you have "
223 "to change ``origin/master`` above. To send only the last commit, use::"
224 msgstr ""
225
226 #: ../../__w/calibre/calibre/manual/develop.rst:119
227 msgid ""
228 "To send the last *n* commits, replace *1* with *n*, for example, for the "
229 "last 3 commits::"
230 msgstr ""
231
232 #: ../../__w/calibre/calibre/manual/develop.rst:124
233 msgid "Be careful to not include merges when using ``HEAD~n``."
234 msgstr ""
235
236 #: ../../__w/calibre/calibre/manual/develop.rst:126
237 msgid ""
238 "If you plan to do a lot of development on calibre, then the best method is "
239 "to create a `GitHub <https://github.com>`__ account. Below is a basic guide "
240 "to setting up your own fork of calibre in a way that will allow you to "
241 "submit pull requests for inclusion into the main calibre repository:"
242 msgstr ""
243
244 #: ../../__w/calibre/calibre/manual/develop.rst:131
245 msgid ""
246 "Setup git on your machine as described in this article: `Setup Git "
247 "<https://help.github.com/articles/set-up-git>`_"
248 msgstr ""
249
250 #: ../../__w/calibre/calibre/manual/develop.rst:132
251 msgid ""
252 "Setup ssh keys for authentication to GitHub, as described here: `Generating "
253 "SSH keys <https://help.github.com/articles/generating-ssh-keys>`_"
254 msgstr ""
255
256 #: ../../__w/calibre/calibre/manual/develop.rst:133
257 msgid ""
258 "Go to https://github.com/kovidgoyal/calibre and click the :guilabel:`Fork` "
259 "button."
260 msgstr ""
261
262 #: ../../__w/calibre/calibre/manual/develop.rst:134
263 msgid "In a Terminal do::"
264 msgstr "W terminalu::"
265
266 #: ../../__w/calibre/calibre/manual/develop.rst:139
267 msgid ""
268 "Replace <username> above with your GitHub username. That will get your fork "
269 "checked out locally."
270 msgstr ""
271
272 #: ../../__w/calibre/calibre/manual/develop.rst:140
273 msgid ""
274 "You can make changes and commit them whenever you like. When you are ready "
275 "to have your work merged, do a::"
276 msgstr ""
277
278 #: ../../__w/calibre/calibre/manual/develop.rst:144
279 msgid ""
280 "and go to ``https://github.com/<username>/calibre`` and click the "
281 ":guilabel:`Pull Request` button to generate a pull request that can be "
282 "merged."
283 msgstr ""
284
285 #: ../../__w/calibre/calibre/manual/develop.rst:145
286 msgid ""
287 "You can update your local copy with code from the main repo at any time by "
288 "doing::"
289 msgstr ""
290
291 #: ../../__w/calibre/calibre/manual/develop.rst:150
292 msgid ""
293 "You should also keep an eye on the calibre `development forum "
294 "<https://www.mobileread.com/forums/forumdisplay.php?f=240>`_. Before making "
295 "major changes, you should discuss them in the forum or contact Kovid "
296 "directly (his email address is all over the source code)."
297 msgstr ""
298
299 #: ../../__w/calibre/calibre/manual/develop.rst:156
300 msgid "Windows development environment"
301 msgstr ""
302
303 #: ../../__w/calibre/calibre/manual/develop.rst:158
304 #: ../../__w/calibre/calibre/manual/develop.rst:192
305 #: ../../__w/calibre/calibre/manual/develop.rst:228
306 msgid ""
307 "You must also get the calibre source code separately as described above."
308 msgstr ""
309
310 #: ../../__w/calibre/calibre/manual/develop.rst:160
311 msgid ""
312 "Install calibre normally, using the Windows installer. Then open a Command "
313 "Prompt and change to the previously checked out calibre code folder. For "
314 "example::"
315 msgstr ""
316
317 #: ../../__w/calibre/calibre/manual/develop.rst:165
318 #: ../../__w/calibre/calibre/manual/develop.rst:240
319 msgid "calibre is the folder that contains the src and resources sub-folders."
320 msgstr ""
321
322 #: ../../__w/calibre/calibre/manual/develop.rst:167
323 msgid ""
324 "The next step is to set the environment variable ``CALIBRE_DEVELOP_FROM`` to"
325 " the absolute path of the src folder. So, following the example above, it "
326 "would be ``C:\\Users\\kovid\\work\\calibre\\src``. `Here is a short guide "
327 "<https://docs.python.org/using/windows.html#excursus-setting-environment-"
328 "variables>`_ to setting environment variables on Windows."
329 msgstr ""
330
331 #: ../../__w/calibre/calibre/manual/develop.rst:172
332 msgid ""
333 "Once you have set the environment variable, open a new command prompt and "
334 "check that it was correctly set by using the command::"
335 msgstr ""
336
337 #: ../../__w/calibre/calibre/manual/develop.rst:177
338 #: ../../__w/calibre/calibre/manual/develop.rst:251
339 msgid ""
340 "Setting this environment variable means that calibre will now load all its "
341 "Python code from the specified location."
342 msgstr ""
343
344 #: ../../__w/calibre/calibre/manual/develop.rst:179
345 msgid ""
346 "That's it! You are now ready to start hacking on the calibre code. For "
347 "example, open the file :file:`src\\\\calibre\\\\__init__.py` in your "
348 "favorite editor and add the line::"
349 msgstr ""
350
351 #: ../../__w/calibre/calibre/manual/develop.rst:184
352 #: ../../__w/calibre/calibre/manual/develop.rst:258
353 msgid ""
354 "near the top of the file. Now run the command :command:`calibredb`. The very"
355 " first line of output should be ``Hello, world!``."
356 msgstr ""
357
358 #: ../../__w/calibre/calibre/manual/develop.rst:186
359 msgid ""
360 "You can also setup a calibre development environment inside the free "
361 "Microsoft Visual Studio, if you like, following the instructions `here "
362 "<https://www.mobileread.com/forums/showthread.php?t=251201>`_."
363 msgstr ""
364
365 #: ../../__w/calibre/calibre/manual/develop.rst:190
366 msgid "macOS development environment"
367 msgstr ""
368
369 #: ../../__w/calibre/calibre/manual/develop.rst:194
370 msgid ""
371 "Install calibre normally using the provided .dmg. Then open a Terminal and "
372 "change to the previously checked out calibre code folder, for example::"
373 msgstr ""
374
375 #: ../../__w/calibre/calibre/manual/develop.rst:199
376 msgid ""
377 "calibre is the folder that contains the src and resources sub-folders. The "
378 "calibre command line tools are found inside the calibre app bundle, in "
379 ":file:`/Applications/calibre.app/Contents/MacOS` you should add this folder "
380 "to your PATH environment variable, if you want to run the command line tools"
381 " easily."
382 msgstr ""
383
384 #: ../../__w/calibre/calibre/manual/develop.rst:205
385 msgid ""
386 "The next step is to create a bash script that will set the environment "
387 "variable ``CALIBRE_DEVELOP_FROM`` to the absolute path of the src folder "
388 "when running calibre in debug mode."
389 msgstr ""
390
391 #: ../../__w/calibre/calibre/manual/develop.rst:207
392 msgid "Create a plain text file::"
393 msgstr "Stwórz zwykły plik tekstowy"
394
395 #: ../../__w/calibre/calibre/manual/develop.rst:213
396 msgid ""
397 "Save this file as :file:`/usr/local/bin/calibre-develop`, then set its "
398 "permissions so that it can be executed::"
399 msgstr ""
400
401 #: ../../__w/calibre/calibre/manual/develop.rst:217
402 msgid "Once you have done this, run::"
403 msgstr "Jeśli to zrobiłeś, uruchom: "
404
405 #: ../../__w/calibre/calibre/manual/develop.rst:221
406 msgid ""
407 "You should see some diagnostic information in the Terminal window as calibre"
408 " starts up, and you should see an asterisk after the version number in the "
409 "GUI window, indicating that you are running from source."
410 msgstr ""
411
412 #: ../../__w/calibre/calibre/manual/develop.rst:226
413 msgid "Linux development environment"
414 msgstr ""
415
416 #: ../../__w/calibre/calibre/manual/develop.rst:230
417 msgid ""
418 "calibre is primarily developed on Linux. You have two choices in setting up "
419 "the development environment. You can install the calibre binary as normal "
420 "and use that as a runtime environment to do your development. This approach "
421 "is similar to that used in Windows and macOS. Alternatively, you can install"
422 " calibre from source. Instructions for setting up a development environment "
423 "from source are in the INSTALL file in the source tree. Here we will address"
424 " using the binary as a runtime, which is the recommended method."
425 msgstr ""
426
427 #: ../../__w/calibre/calibre/manual/develop.rst:236
428 msgid ""
429 "Install calibre using the binary installer. Then open a terminal and change "
430 "to the previously checked out calibre code folder, for example::"
431 msgstr ""
432
433 #: ../../__w/calibre/calibre/manual/develop.rst:242
434 msgid ""
435 "The next step is to set the environment variable ``CALIBRE_DEVELOP_FROM`` to"
436 " the absolute path of the src folder. So, following the example above, it "
437 "would be ``/home/kovid/work/calibre/src``. How to set environment variables "
438 "depends on your Linux distribution and what shell you are using."
439 msgstr ""
440
441 #: ../../__w/calibre/calibre/manual/develop.rst:246
442 msgid ""
443 "Once you have set the environment variable, open a new terminal and check "
444 "that it was correctly set by using the command::"
445 msgstr ""
446
447 #: ../../__w/calibre/calibre/manual/develop.rst:253
448 msgid ""
449 "That's it! You are now ready to start hacking on the calibre code. For "
450 "example, open the file :file:`src/calibre/__init__.py` in your favorite "
451 "editor and add the line::"
452 msgstr ""
453
454 #: ../../__w/calibre/calibre/manual/develop.rst:261
455 msgid ""
456 "Having separate \"normal\" and \"development\" calibre installs on the same "
457 "computer"
458 msgstr ""
459
460 #: ../../__w/calibre/calibre/manual/develop.rst:263
461 msgid ""
462 "The calibre source tree is very stable and rarely breaks, but if you feel "
463 "the need to run from source on a separate test library and run the released "
464 "calibre version with your everyday library, you can achieve this easily "
465 "using .bat files or shell scripts to launch calibre. The example below shows"
466 " how to do this on Windows using .bat files (the instructions for other "
467 "platforms are the same, just use a shell script instead of a .bat file)"
468 msgstr ""
469
470 #: ../../__w/calibre/calibre/manual/develop.rst:268
471 msgid "To launch the release version of calibre with your everyday library:"
472 msgstr ""
473
474 #: ../../__w/calibre/calibre/manual/develop.rst:270
475 msgid "calibre-normal.bat::"
476 msgstr ""
477
478 #: ../../__w/calibre/calibre/manual/develop.rst:274
479 msgid "calibre-dev.bat::"
480 msgstr ""
481
482 #: ../../__w/calibre/calibre/manual/develop.rst:281
483 msgid "Debugging tips"
484 msgstr "Wskazówki debugowania"
485
486 #: ../../__w/calibre/calibre/manual/develop.rst:283
487 msgid ""
488 "Python is a dynamically typed language with excellent facilities for "
489 "introspection. Kovid wrote the core calibre code without once using a "
490 "debugger. There are many strategies to debug calibre code:"
491 msgstr ""
492
493 #: ../../__w/calibre/calibre/manual/develop.rst:288
494 msgid "Using print statements"
495 msgstr ""
496
497 #: ../../__w/calibre/calibre/manual/develop.rst:290
498 msgid ""
499 "This is Kovid's favorite way to debug. Simply insert print statements at "
500 "points of interest and run your program in the terminal. For example, you "
501 "can start the GUI from the terminal as::"
502 msgstr ""
503
504 #: ../../__w/calibre/calibre/manual/develop.rst:295
505 msgid "Similarly, you can start the E-book viewer as::"
506 msgstr ""
507
508 #: ../../__w/calibre/calibre/manual/develop.rst:299
509 msgid "The e-book-editor can be started as::"
510 msgstr ""
511
512 #: ../../__w/calibre/calibre/manual/develop.rst:304
513 msgid "Using an interactive Python interpreter"
514 msgstr ""
515
516 #: ../../__w/calibre/calibre/manual/develop.rst:306
517 msgid ""
518 "You can insert the following two lines of code to start an interactive "
519 "Python session at that point::"
520 msgstr ""
521
522 #: ../../__w/calibre/calibre/manual/develop.rst:311
523 msgid ""
524 "When running from the command line, this will start an interactive Python "
525 "interpreter with access to all locally defined variables (variables in the "
526 "local scope). The interactive prompt even has :kbd:`Tab` completion for "
527 "object properties and you can use the various Python facilities for "
528 "introspection, such as :func:`dir`, :func:`type`, :func:`repr`, etc."
529 msgstr ""
530
531 #: ../../__w/calibre/calibre/manual/develop.rst:317
532 msgid "Using the Python debugger as a remote debugger"
533 msgstr ""
534
535 #: ../../__w/calibre/calibre/manual/develop.rst:319
536 msgid ""
537 "You can use the builtin Python debugger (pdb) as a remote debugger from the "
538 "command line. First, start the remote debugger at the point in the calibre "
539 "code you are interested in, like this::"
540 msgstr ""
541
542 #: ../../__w/calibre/calibre/manual/develop.rst:326
543 msgid ""
544 "Then run calibre, either as normal, or using one of the calibre-debug "
545 "commands described in the previous section. Once the above point in the code"
546 " is reached, calibre will freeze, waiting for the debugger to connect."
547 msgstr ""
548
549 #: ../../__w/calibre/calibre/manual/develop.rst:330
550 msgid ""
551 "Now open a terminal or command prompt and use the following command to start"
552 " the debugging session::"
553 msgstr ""
554
555 #: ../../__w/calibre/calibre/manual/develop.rst:335
556 msgid ""
557 "You can read about how to use the Python debugger in the `Python stdlib docs"
558 " for the pdb module <https://docs.python.org/library/pdb.html#debugger-"
559 "commands>`_."
560 msgstr ""
561
562 #: ../../__w/calibre/calibre/manual/develop.rst:339
563 msgid ""
564 "By default, the remote debugger will try to connect on port 4444. You can "
565 "change it, by passing the port parameter to both the set_trace() and the "
566 "cli() functions above, like this: ``set_trace(port=1234)`` and "
567 "``cli(port=1234)``."
568 msgstr ""
569
570 #: ../../__w/calibre/calibre/manual/develop.rst:345
571 msgid ""
572 "The Python debugger cannot handle multiple threads, so you have to call "
573 "set_trace once per thread, each time with a different port number."
574 msgstr ""
575
576 #: ../../__w/calibre/calibre/manual/develop.rst:349
577 msgid "Using the debugger in your favorite Python IDE"
578 msgstr ""
579
580 #: ../../__w/calibre/calibre/manual/develop.rst:351
581 msgid ""
582 "It is possible to use the builtin debugger in your favorite Python IDE, if "
583 "it supports remote debugging. The first step is to add the calibre src "
584 "checkout to the ``PYTHONPATH`` in your IDE. In other words, the folder you "
585 "set as ``CALIBRE_DEVELOP_FROM`` above, must also be in the ``PYTHONPATH`` of"
586 " your IDE."
587 msgstr ""
588
589 #: ../../__w/calibre/calibre/manual/develop.rst:356
590 msgid ""
591 "Then place the IDE's remote debugger module into the :file:`src` sub-folder "
592 "of the calibre source code checkout. Add whatever code is needed to launch "
593 "the remote debugger to calibre at the point of interest, for example in the "
594 "main function. Then run calibre as normal. Your IDE should now be able to "
595 "connect to the remote debugger running inside calibre."
596 msgstr ""
597
598 #: ../../__w/calibre/calibre/manual/develop.rst:363
599 msgid "Executing arbitrary scripts in the calibre Python environment"
600 msgstr ""
601
602 #: ../../__w/calibre/calibre/manual/develop.rst:365
603 msgid ""
604 "The :command:`calibre-debug` command provides a couple of handy switches to "
605 "execute your own code, with access to the calibre modules::"
606 msgstr ""
607
608 #: ../../__w/calibre/calibre/manual/develop.rst:370
609 msgid ""
610 "is great for testing a little snippet of code on the command line. It works "
611 "in the same way as the -c switch to the Python interpreter::"
612 msgstr ""
613
614 #: ../../__w/calibre/calibre/manual/develop.rst:374
615 msgid ""
616 "can be used to execute your own Python script. It works in the same way as "
617 "passing the script to the Python interpreter, except that the calibre "
618 "environment is fully initialized, so you can use all the calibre code in "
619 "your script. To use command line arguments with your script, use the form::"
620 msgstr ""
621
622 #: ../../__w/calibre/calibre/manual/develop.rst:379
623 msgid ""
624 "The ``--`` causes all subsequent arguments to be passed to your script."
625 msgstr ""
626
627 #: ../../__w/calibre/calibre/manual/develop.rst:383
628 msgid "Using calibre in your projects"
629 msgstr "Używanie calibre w twoich projektach"
630
631 #: ../../__w/calibre/calibre/manual/develop.rst:385
632 msgid ""
633 "It is possible to directly use calibre functions/code in your Python "
634 "project. Two ways exist to do this:"
635 msgstr ""
636
637 #: ../../__w/calibre/calibre/manual/develop.rst:388
638 msgid "Binary install of calibre"
639 msgstr ""
640
641 #: ../../__w/calibre/calibre/manual/develop.rst:390
642 msgid ""
643 "If you have a binary install of calibre, you can use the Python interpreter "
644 "bundled with calibre, like this::"
645 msgstr ""
646
647 #: ../../__w/calibre/calibre/manual/develop.rst:395
648 msgid "Source install on Linux"
649 msgstr ""
650
651 #: ../../__w/calibre/calibre/manual/develop.rst:397
652 msgid ""
653 "In addition to using the above technique, if you do a source install on "
654 "Linux, you can also directly import calibre, as follows::"
655 msgstr ""
656
657 #: ../../__w/calibre/calibre/manual/develop.rst:405
658 msgid ""
659 "It is essential that you import the init_calibre module before any other "
660 "calibre modules/packages as it sets up the interpreter to run calibre code."
661 msgstr ""
662
663 #: ../../__w/calibre/calibre/manual/develop.rst:409
664 msgid "API documentation for various parts of calibre"
665 msgstr ""