Debian Codegraph @

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