Debian Codegraph @

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