Debian Codegraph @

translations/manual/conversion.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/conversion.rst:4
20 msgid "E-book conversion"
21 msgstr ""
22
23 #: ../../../home/kovid/work/calibre/manual/conversion.rst:6
24 msgid "calibre has a conversion system that is designed to be very easy to use. Normally, you just add a book to calibre, click convert and calibre will try hard to generate output that is as close as possible to the input. However, calibre accepts a very large number of input formats, not all of which are as suitable as others for conversion to e-books. In the case of such input formats, or if you just want greater control over the conversion system, calibre has a lot of options to fine tune the conversion process. Note however that calibre's conversion system is not a substitute for a full blown e-book editor. To edit e-books, I recommend first converting them to EPUB or AZW3 using calibre and then using the :guilabel:`Edit book` feature to get them into perfect shape. You can then use the edited e-book as input for conversion into other formats in calibre."
25 msgstr ""
26
27 #: ../../../home/kovid/work/calibre/manual/conversion.rst:18
28 msgid "This document will refer mainly to the conversion settings as found in the conversion dialog, pictured below. All these settings are also available via command line interface to conversion, documented at :doc:`generated/en/ebook-convert`. In calibre, you can obtain help on any individual setting by holding your mouse over it, a tooltip will appear describing the setting."
29 msgstr ""
30
31 #: ../../../home/kovid/work/calibre/manual/conversion.rst:24
32 msgid "E-book conversion dialog"
33 msgstr ""
34
35 #: ../../../home/kovid/work/calibre/manual/conversion.rst:31
36 #: ../../../home/kovid/work/calibre/manual/conversion.rst:95
37 msgid "Contents"
38 msgstr ""
39
40 #: ../../../home/kovid/work/calibre/manual/conversion.rst:36
41 msgid "Introduction"
42 msgstr ""
43
44 #: ../../../home/kovid/work/calibre/manual/conversion.rst:42
45 msgid "The first thing to understand about the conversion system is that it is designed as a pipeline. Schematically, it looks like this:"
46 msgstr ""
47
48 #: ../../../home/kovid/work/calibre/manual/conversion.rst:45
49 msgid "The conversion pipeline"
50 msgstr ""
51
52 #: ../../../home/kovid/work/calibre/manual/conversion.rst:49
53 msgid "The input format is first converted to XHTML by the appropriate *Input plugin*. This HTML is then *transformed*. In the last step, the processed XHTML is converted to the specified output format by the appropriate *Output plugin*. The results of the conversion can vary greatly, based on the input format. Some formats convert much better than others. A list of the best source formats for conversion is available :ref:`here <best-source-formats>`."
54 msgstr ""
55
56 #: ../../../home/kovid/work/calibre/manual/conversion.rst:56
57 msgid "The transforms that act on the XHTML output are where all the work happens. There are various transforms, for example, to insert book metadata as a page at the start of the book, to detect chapter headings and automatically create a Table of Contents, to proportionally adjust font sizes, et cetera. It is important to remember that all the transforms act on the XHTML output by the *Input plugin*, not on the input file itself. So, for example, if you ask calibre to convert an RTF file to EPUB, it will first be converted to XHTML internally, the various transforms will be applied to the XHTML and then the *Output plugin* will create the EPUB file, automatically generating all metadata, Table of Contents, et cetera."
58 msgstr ""
59
60 #: ../../../home/kovid/work/calibre/manual/conversion.rst:65
61 msgid "You can see this process in action by using the debug option |dbgi|. Just specify the path to a folder for the debug output. During conversion, calibre will place the XHTML generated by the various stages of the conversion pipeline in different sub-folders. The four sub-folders are:"
62 msgstr ""
63
64 #: ../../../home/kovid/work/calibre/manual/conversion.rst:38
65 msgid "Debug icon"
66 msgstr ""
67
68 #: ../../../home/kovid/work/calibre/manual/conversion.rst:70
69 msgid "Stages of the conversion pipeline"
70 msgstr ""
71
72 #: ../../../home/kovid/work/calibre/manual/conversion.rst:73
73 msgid "Folder"
74 msgstr ""
75
76 #: ../../../home/kovid/work/calibre/manual/conversion.rst:73
77 msgid "Description"
78 msgstr ""
79
80 #: ../../../home/kovid/work/calibre/manual/conversion.rst:75
81 msgid "input"
82 msgstr ""
83
84 #: ../../../home/kovid/work/calibre/manual/conversion.rst:75
85 msgid "This contains the HTML output by the Input plugin. Use this to debug the Input plugin."
86 msgstr ""
87
88 #: ../../../home/kovid/work/calibre/manual/conversion.rst:76
89 msgid "parsed"
90 msgstr ""
91
92 #: ../../../home/kovid/work/calibre/manual/conversion.rst:76
93 msgid "The result of pre-processing and converting to XHTML the output from the Input plugin. Use to debug structure detection."
94 msgstr ""
95
96 #: ../../../home/kovid/work/calibre/manual/conversion.rst:77
97 msgid "structure"
98 msgstr ""
99
100 #: ../../../home/kovid/work/calibre/manual/conversion.rst:77
101 msgid "Post structure detection, but before CSS flattening and font size conversion. Use to debug font size conversion and CSS transforms."
102 msgstr ""
103
104 #: ../../../home/kovid/work/calibre/manual/conversion.rst:78
105 msgid "processed"
106 msgstr ""
107
108 #: ../../../home/kovid/work/calibre/manual/conversion.rst:78
109 msgid "Just before the e-book is passed to the Output plugin. Use to debug the Output plugin."
110 msgstr ""
111
112 #: ../../../home/kovid/work/calibre/manual/conversion.rst:81
113 msgid "If you want to edit the input document a little before having calibre convert it, the best thing to do is edit the files in the :file:`input` sub-folder, then zip it up, and use the ZIP file as the input format for subsequent conversions. To do this use the :guilabel:`Edit meta information` dialog to add the ZIP file as a format for the book and then, in the top left corner of the conversion dialog, select ZIP as the input format."
114 msgstr ""
115
116 #: ../../../home/kovid/work/calibre/manual/conversion.rst:87
117 msgid "This document will deal mainly with the various transforms that operate on the intermediate XHTML and how to control them. At the end are some tips specific to each input/output format."
118 msgstr ""
119
120 #: ../../../home/kovid/work/calibre/manual/conversion.rst:91
121 msgid "Look & feel"
122 msgstr ""
123
124 #: ../../../home/kovid/work/calibre/manual/conversion.rst:97
125 msgid "This group of options controls various aspects of the look and feel of the converted e-book."
126 msgstr ""
127
128 #: ../../../home/kovid/work/calibre/manual/conversion.rst:102
129 msgid "Fonts"
130 msgstr ""
131
132 #: ../../../home/kovid/work/calibre/manual/conversion.rst:104
133 msgid "One of the nicest features of the e-reading experience is the ability to easily adjust font sizes to suit individual needs and lighting conditions. calibre has sophisticated algorithms to ensure that all the books it outputs have consistent font sizes, no matter what font sizes are specified in the input document."
134 msgstr ""
135
136 #: ../../../home/kovid/work/calibre/manual/conversion.rst:109
137 msgid "The base font size of a document is the most common font size in that document, i.e., the size of the bulk of text in that document. When you specify a :guilabel:`Base font size`, calibre automatically rescales all font sizes in the document proportionately, so that the most common font size becomes the specified base font size and other font sizes are rescaled appropriately. By choosing a larger base font size, you can make the fonts in the document larger and vice versa. When you set the base font size, for best results, you should also set the font size key."
138 msgstr ""
139
140 #: ../../../home/kovid/work/calibre/manual/conversion.rst:117
141 msgid "Normally, calibre will automatically choose a base font size appropriate to the output profile you have chosen (see :ref:`page-setup`). However, you can override this here in case the default is not suitable for you."
142 msgstr ""
143
144 #: ../../../home/kovid/work/calibre/manual/conversion.rst:121
145 msgid "The :guilabel:`Font size key` option lets you control how non-base font sizes are rescaled. The font rescaling algorithm works using a font size key, which is simply a comma-separated list of font sizes. The font size key tells calibre how many \"steps\" bigger or smaller a given font size should be compared to the base font size. The idea is that there should be a limited number of font sizes in a document. For example, one size for the body text, a couple of sizes for different levels of headings and a couple of sizes for super/sub scripts and footnotes. The font size key allows calibre to compartmentalize the font sizes in the input documents into separate \"bins\" corresponding to the different logical font sizes."
146 msgstr ""
147
148 #: ../../../home/kovid/work/calibre/manual/conversion.rst:130
149 msgid "Let's illustrate with an example. Suppose the source document we are converting was produced by someone with excellent eyesight and has a base font size of 8pt. That means the bulk of the text in the document is sized at 8pts, while headings are somewhat larger (say 10 and 12pt) and footnotes somewhat smaller at 6pt. Now if we use the following settings::"
150 msgstr ""
151
152 #: ../../../home/kovid/work/calibre/manual/conversion.rst:139
153 msgid "The output document will have a base font size of 12pt, headings of 14 and 16pt and footnotes of 8pt. Now suppose we want to make the largest heading size stand out more and make the footnotes a little larger as well. To achieve this, the font key should be changed to::"
154 msgstr ""
155
156 #: ../../../home/kovid/work/calibre/manual/conversion.rst:145
157 msgid "The largest headings will now become 18pt, while the footnotes will become 9pt. You can play with these settings to try and figure out what would be optimum for you by using the font rescaling wizard, which can be accessed by clicking the little button next to the :guilabel:`Font size key` setting."
158 msgstr ""
159
160 #: ../../../home/kovid/work/calibre/manual/conversion.rst:150
161 msgid "All the font size rescaling in the conversion can also be disabled here, if you would like to preserve the font sizes in the input document."
162 msgstr ""
163
164 #: ../../../home/kovid/work/calibre/manual/conversion.rst:153
165 msgid "A related setting is :guilabel:`Line height`. Line height controls the vertical height of lines. By default, (a line height of 0), no manipulation of line heights is performed. If you specify a non-default value, line heights will be set in all locations that don't specify their own line heights. However, this is something of a blunt weapon and should be used sparingly. If you want to adjust the line heights for some section of the input, it's better to use the :ref:`Extra CSS <extra-css>`."
166 msgstr ""
167
168 #: ../../../home/kovid/work/calibre/manual/conversion.rst:160
169 msgid "In this section you can also tell calibre to embed any referenced fonts into the book. This will allow the fonts to work on reader devices even if they are not available on the device."
170 msgstr ""
171
172 #: ../../../home/kovid/work/calibre/manual/conversion.rst:165
173 msgid "Text"
174 msgstr ""
175
176 #: ../../../home/kovid/work/calibre/manual/conversion.rst:167
177 msgid "Text can be either justified or not. Justified text has extra spaces between words to give a smooth right margin. Some people prefer justified text, others do not. Normally, calibre will preserve the justification in the original document. If you want to override it you can use the :guilabel:`Text justification` option in this section."
178 msgstr ""
179
180 #: ../../../home/kovid/work/calibre/manual/conversion.rst:173
181 msgid "You can also tell calibre to :guilabel:`Smarten punctuation` which will replace plain quotes, dashes and ellipses with their typographically correct alternatives. Note that this algorithm is not perfect so it is worth reviewing the results. The reverse, namely, :guilabel:`Unsmarted punctuation` is also available."
182 msgstr ""
183
184 #: ../../../home/kovid/work/calibre/manual/conversion.rst:178
185 msgid "Finally, there is :guilabel:`Input character encoding`. Older documents sometimes don't specify their character encoding. When converted, this can result in non-English characters or special characters like smart quotes being corrupted. calibre tries to auto-detect the character encoding of the source document, but it does not always succeed. You can force it to assume a particular character encoding by using this setting. `cp1252` is a common encoding for documents produced using Windows software. You should also read :ref:`char-encoding-faq` for more on encoding issues."
186 msgstr ""
187
188 #: ../../../home/kovid/work/calibre/manual/conversion.rst:188
189 msgid "Layout"
190 msgstr ""
191
192 #: ../../../home/kovid/work/calibre/manual/conversion.rst:190
193 msgid "Normally, paragraphs in XHTML are rendered with a blank line between them and no leading text indent. calibre has a couple of options to control this. :guilabel:`Remove spacing between paragraphs` forcefully ensure that all paragraphs have no inter paragraph spacing. It also sets the text indent to 1.5em (can be changed) to mark the start of every paragraph. :guilabel:`Insert blank line` does the opposite, guaranteeing that there is exactly one blank line between each pair of paragraphs. Both these options are very comprehensive, removing spacing, or inserting it for *all* paragraphs (technically <p> and <div> tags). This is so that you can just set the option and be sure that it performs as advertised, irrespective of how messy the input file is. The one exception is when the input file uses hard line breaks to implement inter-paragraph spacing."
194 msgstr ""
195
196 #: ../../../home/kovid/work/calibre/manual/conversion.rst:201
197 msgid "If you want to remove the spacing between all paragraphs, except a select few, don't use these options. Instead add the following CSS code to :ref:`Extra CSS <extra-css>`::"
198 msgstr ""
199
200 #: ../../../home/kovid/work/calibre/manual/conversion.rst:207
201 msgid "Then, in your source document, mark the paragraphs that need spacing with `class=\"spacious\"`. If your input document is not in HTML, use the Debug option, described in the Introduction to get HTML (use the :file:`input` sub-folder)."
202 msgstr ""
203
204 #: ../../../home/kovid/work/calibre/manual/conversion.rst:211
205 msgid "Another useful option is :guilabel:`Linearize tables`. Some badly designed documents use tables to control the layout of text on the page. When converted these documents often have text that runs off the page and other artifacts. This option will extract the content from the tables and present it in a linear fashion. Note that this option linearizes *all* tables, so only use it if you are sure the input document does not use tables for legitimate purposes, like presenting tabular information."
206 msgstr ""
207
208 #: ../../../home/kovid/work/calibre/manual/conversion.rst:220
209 msgid "Styling"
210 msgstr ""
211
212 #: ../../../home/kovid/work/calibre/manual/conversion.rst:224
213 msgid "The :guilabel:`Extra CSS` option allows you to specify arbitrary CSS that will be applied to all HTML files in the input. This CSS is applied with very high priority and so should override most CSS present in the **input document** itself. You can use this setting to fine tune the presentation/layout of your document. For example, if you want all paragraphs of class `endnote` to be right aligned, just add::"
214 msgstr ""
215
216 #: ../../../home/kovid/work/calibre/manual/conversion.rst:233
217 msgid "or if you want to change the indentation of all paragraphs::"
218 msgstr ""
219
220 #: ../../../home/kovid/work/calibre/manual/conversion.rst:237
221 msgid ":guilabel:`Extra CSS` is a very powerful option, but you do need an understanding of how CSS works to use it to its full potential. You can use the debug pipeline option described above to see what CSS is present in your input document."
222 msgstr ""
223
224 #: ../../../home/kovid/work/calibre/manual/conversion.rst:241
225 msgid "A simpler option is to use :guilabel:`Filter style information`. This allows you to remove all CSS properties of the specified types from the document. For example, you can use it to remove all colors or fonts."
226 msgstr ""
227
228 #: ../../../home/kovid/work/calibre/manual/conversion.rst:246
229 msgid "Transform styles"
230 msgstr ""
231
232 #: ../../../home/kovid/work/calibre/manual/conversion.rst:248
233 msgid "This is the most powerful styling related facility. You can use it to define rules that change styles based on various conditions. For example you can use it to change all green colors to blue, or remove all bold styling from the text or color all headings a certain color, etc."
234 msgstr ""
235
236 #: ../../../home/kovid/work/calibre/manual/conversion.rst:254
237 msgid "Transform HTML"
238 msgstr ""
239
240 #: ../../../home/kovid/work/calibre/manual/conversion.rst:256
241 msgid "Similar to transform styles, but allows you to make changes to the HTML content of the book. You can replace one tag with another, add classes or other attributes to tags based on their content, etc."
242 msgstr ""
243
244 #: ../../../home/kovid/work/calibre/manual/conversion.rst:265
245 msgid "Page setup"
246 msgstr ""
247
248 #: ../../../home/kovid/work/calibre/manual/conversion.rst:267
249 msgid "The :guilabel:`Page setup` options are for controlling screen layout, like margins and screen sizes. There are options to setup page margins, which will be used by the output plugin, if the selected output format supports page margins. In addition, you should choose an Input profile and an output profile. Both sets of profiles basically deal with how to interpret measurements in the input/output documents, screen sizes and default font rescaling keys."
250 msgstr ""
251
252 #: ../../../home/kovid/work/calibre/manual/conversion.rst:274
253 msgid "If you know that the file you are converting was intended to be used on a particular device/software platform, choose the corresponding input profile, otherwise just choose the default input profile. If you know the files you are producing are meant for a particular device type, choose the corresponding output profile. Otherwise, choose one of the Generic output profiles. If you are converting to MOBI or AZW3 then you will almost always want to choose one of the Kindle output profiles. Otherwise, your best bet for modern E-book reading devices is to choose the :guilabel:`Generic e-ink HD` output profile."
254 msgstr ""
255
256 #: ../../../home/kovid/work/calibre/manual/conversion.rst:283
257 msgid "The output profile also controls the screen size. This will cause, for example, images to be auto-resized to be fit to the screen in some output formats. So choose a profile of a device that has a screen size similar to your device."
258 msgstr ""
259
260 #: ../../../home/kovid/work/calibre/manual/conversion.rst:291
261 msgid "Heuristic processing"
262 msgstr ""
263
264 #: ../../../home/kovid/work/calibre/manual/conversion.rst:293
265 msgid "Heuristic processing provides a variety of functions which can be used to try and detect and correct common problems in poorly formatted input documents. Use these functions if your input document suffers from poor formatting. Because these functions rely on common patterns, be aware that in some cases an option may lead to worse results, so use with care. As an example, several of these options will remove all non-breaking-space entities, or may include false positive matches relating to the function."
266 msgstr ""
267
268 #: ../../../home/kovid/work/calibre/manual/conversion.rst:299
269 msgid ":guilabel:`Enable heuristic processing`"
270 msgstr ""
271
272 #: ../../../home/kovid/work/calibre/manual/conversion.rst:300
273 msgid "This option activates calibre's :guilabel:`Heuristic processing` stage of the conversion pipeline. This must be enabled in order for various sub-functions to be applied"
274 msgstr ""
275
276 #: ../../../home/kovid/work/calibre/manual/conversion.rst:303
277 msgid ":guilabel:`Unwrap lines`"
278 msgstr ""
279
280 #: ../../../home/kovid/work/calibre/manual/conversion.rst:304
281 msgid "Enabling this option will cause calibre to attempt to detect and correct hard line breaks that exist within a document using punctuation clues and line length. calibre will first attempt to detect whether hard line breaks exist, if they do not appear to exist calibre will not attempt to unwrap lines. The line-unwrap factor can be reduced if you want to 'force' calibre to unwrap lines."
282 msgstr ""
283
284 #: ../../../home/kovid/work/calibre/manual/conversion.rst:309
285 msgid ":guilabel:`Line-unwrap factor`"
286 msgstr ""
287
288 #: ../../../home/kovid/work/calibre/manual/conversion.rst:310
289 msgid "This option controls the algorithm calibre uses to remove hard line breaks. For example, if the value of this option is 0.4, that means calibre will remove hard line breaks from the end of lines whose lengths are less than the length of 40% of all lines in the document. If your document only has a few line breaks which need correction, then this value should be reduced to somewhere between 0.1 and 0.2."
290 msgstr ""
291
292 #: ../../../home/kovid/work/calibre/manual/conversion.rst:315
293 msgid ":guilabel:`Detect and markup unformatted chapter headings and sub headings`"
294 msgstr ""
295
296 #: ../../../home/kovid/work/calibre/manual/conversion.rst:316
297 msgid "If your document does not have chapter headings and titles formatted differently from the rest of the text, calibre can use this option to attempt to detect them and surround them with heading tags. <h2> tags are used for chapter headings; <h3> tags are used for any titles that are detected."
298 msgstr ""
299
300 #: ../../../home/kovid/work/calibre/manual/conversion.rst:320
301 msgid "This function will not create a TOC, but in many cases it will cause calibre's default chapter detection settings to correctly detect chapters and build a TOC. Adjust the XPath under Structure detection if a TOC is not automatically created. If there are no other headings used in the document then setting \"//h:h2\" under Structure detection would be the easiest way to create a TOC for the document."
302 msgstr ""
303
304 #: ../../../home/kovid/work/calibre/manual/conversion.rst:325
305 msgid "The inserted headings are not formatted, to apply formatting use the :guilabel:`Extra CSS` option under the Look and Feel conversion settings. For example, to center heading tags, use the following::"
306 msgstr ""
307
308 #: ../../../home/kovid/work/calibre/manual/conversion.rst:330
309 msgid ":guilabel:`Renumber sequences of <h1> or <h2> tags`"
310 msgstr ""
311
312 #: ../../../home/kovid/work/calibre/manual/conversion.rst:331
313 msgid "Some publishers format chapter headings using multiple <h1> or <h2> tags sequentially. calibre's default conversion settings will cause such titles to be split into two pieces. This option will re-number the heading tags to prevent splitting."
314 msgstr ""
315
316 #: ../../../home/kovid/work/calibre/manual/conversion.rst:335
317 msgid ":guilabel:`Delete blank lines between paragraphs`"
318 msgstr ""
319
320 #: ../../../home/kovid/work/calibre/manual/conversion.rst:336
321 msgid "This option will cause calibre to analyze blank lines included within the document. If every paragraph is interleaved with a blank line, then calibre will remove all those blank paragraphs. Sequences of multiple blank lines will be considered scene breaks and retained as a single paragraph. This option differs from the :guilabel:`Remove paragraph spacing` option under :guilabel:`Look and Feel` in that it actually modifies the HTML content, while the other option modifies the document styles. This option can also remove paragraphs which were inserted using calibre's :guilabel:`Insert blank line` option."
322 msgstr ""
323
324 #: ../../../home/kovid/work/calibre/manual/conversion.rst:346
325 msgid ":guilabel:`Ensure scene breaks are consistently formatted`"
326 msgstr ""
327
328 #: ../../../home/kovid/work/calibre/manual/conversion.rst:347
329 msgid "With this option calibre will attempt to detect common scene-break markers and ensure that they are center aligned. 'Soft' scene break markers, i.e. scene breaks only defined by extra white space, are styled to ensure that they will not be displayed in conjunction with page breaks."
330 msgstr ""
331
332 #: ../../../home/kovid/work/calibre/manual/conversion.rst:351
333 msgid ":guilabel:`Replace scene breaks`"
334 msgstr ""
335
336 #: ../../../home/kovid/work/calibre/manual/conversion.rst:352
337 msgid "If this option is configured then calibre will replace scene break markers it finds with the replacement text specified by the user. Please note that some ornamental characters may not be supported across all reading devices."
338 msgstr ""
339
340 #: ../../../home/kovid/work/calibre/manual/conversion.rst:355
341 msgid "In general you should avoid using HTML tags, calibre will discard any tags and use pre-defined markup. <hr /> tags, i.e. horizontal rules, and <img> tags are exceptions. Horizontal rules can optionally be specified with styles, if you choose to add your own style be sure to include the 'width' setting, otherwise the style information will be discarded. Image tags can used, but calibre does not provide the ability to add the image during conversion, this must be done after the fact using the 'Edit book' feature."
342 msgstr ""
343
344 #: ../../../home/kovid/work/calibre/manual/conversion.rst:361
345 msgid "Example image tag (place the image within an 'Images' folder inside the EPUB after conversion):"
346 msgstr ""
347
348 #: ../../../home/kovid/work/calibre/manual/conversion.rst:362
349 msgid "<img style=\"width:10%\" src=\"../Images/scenebreak.png\" />"
350 msgstr ""
351
352 #: ../../../home/kovid/work/calibre/manual/conversion.rst:364
353 msgid "Example horizontal rule with styles:"
354 msgstr ""
355
356 #: ../../../home/kovid/work/calibre/manual/conversion.rst:365
357 msgid "<hr style=\"width:20%;padding-top: 1px;border-top: 2px ridge black;border-bottom: 2px groove black;\"/>"
358 msgstr ""
359
360 #: ../../../home/kovid/work/calibre/manual/conversion.rst:367
361 msgid ":guilabel:`Remove unnecessary hyphens`"
362 msgstr ""
363
364 #: ../../../home/kovid/work/calibre/manual/conversion.rst:368
365 msgid "calibre will analyze all hyphenated content in the document when this option is enabled. The document itself is used as a dictionary for analysis. This allows calibre to accurately remove hyphens for any words in the document in any language, along with made-up and obscure scientific words. The primary drawback is words appearing only a single time in the document will not be changed. Analysis happens in two passes, the first pass analyzes line endings. Lines are only unwrapped if the word exists with or without a hyphen in the document. The second pass analyzes all hyphenated words throughout the document, hyphens are removed if the word exists elsewhere in the document without a match."
366 msgstr ""
367
368 #: ../../../home/kovid/work/calibre/manual/conversion.rst:375
369 msgid ":guilabel:`Italicize common words and patterns`"
370 msgstr ""
371
372 #: ../../../home/kovid/work/calibre/manual/conversion.rst:376
373 msgid "When enabled, calibre will look for common words and patterns that denote italics and italicize them. Examples are common text conventions such as ~word~ or phrases that should generally be italicized, e.g. latin phrases like 'etc.' or 'et cetera'."
374 msgstr ""
375
376 #: ../../../home/kovid/work/calibre/manual/conversion.rst:379
377 msgid ":guilabel:`Replace entity indents with CSS indents`"
378 msgstr ""
379
380 #: ../../../home/kovid/work/calibre/manual/conversion.rst:380
381 msgid "Some documents use a convention of defining text indents using non-breaking space entities. When this option is enabled calibre will attempt to detect this sort of formatting and convert them to a 3% text indent using CSS."
382 msgstr ""
383
384 #: ../../../home/kovid/work/calibre/manual/conversion.rst:386
385 msgid "Search & replace"
386 msgstr ""
387
388 #: ../../../home/kovid/work/calibre/manual/conversion.rst:388
389 msgid "These options are useful primarily for conversion of PDF documents or OCR conversions, though they can also be used to fix many document specific problems. As an example, some conversions can leave behind page headers and footers in the text. These options use regular expressions to try and detect headers, footers, or other arbitrary text and remove or replace them. Remember that they operate on the intermediate XHTML produced by the conversion pipeline. There is a wizard to help you customize the regular expressions for your document. Click the magic wand beside the expression box, and click the 'Test' button after composing your search expression. Successful matches will be highlighted in Yellow."
390 msgstr ""
391
392 #: ../../../home/kovid/work/calibre/manual/conversion.rst:396
393 msgid "The search works by using a Python regular expression. All matched text is simply removed from the document or replaced using the replacement pattern. The replacement pattern is optional, if left blank then text matching the search pattern will be deleted from the document. You can learn more about regular expressions and their syntax at :ref:`regexptutorial`."
394 msgstr ""
395
396 #: ../../../home/kovid/work/calibre/manual/conversion.rst:404
397 msgid "Structure detection"
398 msgstr ""
399
400 #: ../../../home/kovid/work/calibre/manual/conversion.rst:406
401 msgid "Structure detection involves calibre trying its best to detect structural elements in the input document, when they are not properly specified. For example, chapters, page breaks, headers, footers, etc. As you can imagine, this process varies widely from book to book. Fortunately, calibre has very powerful options to control this. With power comes complexity, but if once you take the time to learn the complexity, you will find it well worth the effort."
402 msgstr ""
403
404 #: ../../../home/kovid/work/calibre/manual/conversion.rst:412
405 msgid "Chapters and page breaks"
406 msgstr ""
407
408 #: ../../../home/kovid/work/calibre/manual/conversion.rst:414
409 msgid "calibre has two sets of options for :guilabel:`chapter detection` and :guilabel:`inserting page breaks`. This can sometimes be slightly confusing, as by default, calibre will insert page breaks before detected chapters as well as the locations detected by the page breaks option. The reason for this is that there are often locations where page breaks should be inserted that are not chapter boundaries. Also, detected chapters can be optionally inserted into the auto generated Table of Contents."
410 msgstr ""
411
412 #: ../../../home/kovid/work/calibre/manual/conversion.rst:419
413 msgid "calibre uses *XPath*, a powerful language to allow the user to specify chapter boundaries/page breaks. XPath can seem a little daunting to use at first, fortunately, there is a :ref:`XPath tutorial <xpath-tutorial>` in the User Manual. Remember that Structure detection operates on the intermediate XHTML produced by the conversion pipeline. Use the debug option described in the :ref:`conversion-introduction` to figure out the appropriate settings for your book. There is also a button for a XPath wizard to help with the generation of simple XPath expressions."
414 msgstr ""
415
416 #: ../../../home/kovid/work/calibre/manual/conversion.rst:425
417 msgid "By default, calibre uses the following expression for detecting chapters::"
418 msgstr ""
419
420 #: ../../../home/kovid/work/calibre/manual/conversion.rst:429
421 msgid "This expression is rather complex, because it tries to handle a number of common cases simultaneously. What it means is that calibre will assume chapters start at either `<h1>` or `<h2>` tags that have any of the words `(chapter, book, section or part)` in them or that have the `class=\"chapter\"` attribute."
422 msgstr ""
423
424 #: ../../../home/kovid/work/calibre/manual/conversion.rst:433
425 msgid "A related option is :guilabel:`Chapter mark`, which allows you to control what calibre does when it detects a chapter. By default, it will insert a page break before the chapter. You can have it insert a ruled line instead of, or in addition to the page break. You can also have it do nothing."
426 msgstr ""
427
428 #: ../../../home/kovid/work/calibre/manual/conversion.rst:437
429 msgid "The default setting for detecting page breaks is::"
430 msgstr ""
431
432 #: ../../../home/kovid/work/calibre/manual/conversion.rst:441
433 msgid "which means that calibre will insert page breaks before every `<h1>` and `<h2>` tag by default."
434 msgstr ""
435
436 #: ../../../home/kovid/work/calibre/manual/conversion.rst:445
437 msgid "The default expressions may change depending on the input format you are converting."
438 msgstr ""
439
440 #: ../../../home/kovid/work/calibre/manual/conversion.rst:448
441 msgid "Miscellaneous"
442 msgstr ""
443
444 #: ../../../home/kovid/work/calibre/manual/conversion.rst:450
445 msgid "There are a few more options in this section."
446 msgstr ""
447
448 #: ../../../home/kovid/work/calibre/manual/conversion.rst:452
449 msgid ":guilabel:`Insert metadata as page at start of book`"
450 msgstr ""
451
452 #: ../../../home/kovid/work/calibre/manual/conversion.rst:453
453 msgid "One of the great things about calibre is that it allows you to maintain very complete metadata about all of your books, for example, a rating, tags, comments, etc. This option will create a single page with all this metadata and insert it into the converted e-book, typically just after the cover. Think of it as a way to create your own customised book jacket."
454 msgstr ""
455
456 #: ../../../home/kovid/work/calibre/manual/conversion.rst:458
457 msgid ":guilabel:`Remove first image`"
458 msgstr ""
459
460 #: ../../../home/kovid/work/calibre/manual/conversion.rst:459
461 msgid "Sometimes, the source document you are converting includes the cover as part of the book, instead of as a separate cover. If you also specify a cover in calibre, then the converted book will have two covers. This option will simply remove the first image from the source document, thereby ensuring that the converted book has only one cover, the one specified in calibre."
462 msgstr ""
463
464 #: ../../../home/kovid/work/calibre/manual/conversion.rst:466
465 msgid "Table of Contents"
466 msgstr ""
467
468 #: ../../../home/kovid/work/calibre/manual/conversion.rst:468
469 msgid "When the input document has a Table of Contents in its metadata, calibre will just use that. However, a number of older formats either do not support a metadata based Table of Contents, or individual documents do not have one. In these cases, the options in this section can help you automatically generate a Table of Contents in the converted e-book, based on the actual content in the input document."
470 msgstr ""
471
472 #: ../../../home/kovid/work/calibre/manual/conversion.rst:473
473 msgid "Using these options can be a little challenging to get exactly right. If you prefer creating/editing the Table of Contents by hand, convert to the EPUB or AZW3 formats and select the checkbox at the bottom of the Table of Contents section of the conversion dialog that says :guilabel:`Manually fine-tune the Table of Contents after conversion`. This will launch the ToC Editor tool after the conversion. It allows you to create entries in the Table of Contents by simply clicking the place in the book where you want the entry to point. You can also use the ToC Editor by itself, without doing a conversion. Go to :guilabel:`Preferences->Interface->Toolbars` and add the :guilabel:`ToC Editor` to the main toolbar. Then just select the book you want to edit and click the :guilabel:`ToC Editor` button."
474 msgstr ""
475
476 #: ../../../home/kovid/work/calibre/manual/conversion.rst:485
477 msgid "The first option is :guilabel:`Force use of auto-generated Table of Contents`. By checking this option you can have calibre override any Table of Contents found in the metadata of the input document with the auto generated one."
478 msgstr ""
479
480 #: ../../../home/kovid/work/calibre/manual/conversion.rst:489
481 msgid "The default way that the creation of the auto generated Table of Contents works is that, calibre will first try to add any detected chapters to the generated table of contents. You can learn how to customize the detection of chapters in the :ref:`structure-detection` section above. If you do not want to include detected chapters in the generated table of contents, check the :guilabel:`Do not add detected chapters` option."
482 msgstr ""
483
484 #: ../../../home/kovid/work/calibre/manual/conversion.rst:494
485 msgid "If less than the :guilabel:`Chapter threshold` number of chapters were detected, calibre will then add any hyperlinks it finds in the input document to the Table of Contents. This often works well: many input documents include a hyperlinked Table of Contents right at the start. The :guilabel:`Number of links` option can be used to control this behavior. If set to zero, no links are added. If set to a number greater than zero, at most that number of links is added."
486 msgstr ""
487
488 #: ../../../home/kovid/work/calibre/manual/conversion.rst:500
489 msgid "calibre will automatically filter duplicates from the generated Table of Contents. However, if there are some additional undesirable entries, you can filter them using the :guilabel:`TOC Filter` option. This is a regular expression that will match the title of entries in the generated table of contents. Whenever a match is found, it will be removed. For example, to remove all entries titles \"Next\" or \"Previous\" use::"
490 msgstr ""
491
492 #: ../../../home/kovid/work/calibre/manual/conversion.rst:507
493 msgid "The :guilabel:`Level 1,2,3 TOC` options allow you to create a sophisticated multi-level Table of Contents. They are XPath expressions that match tags in the intermediate XHTML produced by the conversion pipeline. See the :ref:`conversion-introduction` for how to get access to this XHTML. Also read the :ref:`xpath-tutorial`, to learn how to construct XPath expressions. Next to each option is a button that launches a wizard to help with the creation of basic XPath expressions. The following simple example illustrates how to use these options."
494 msgstr ""
495
496 #: ../../../home/kovid/work/calibre/manual/conversion.rst:513
497 msgid "Suppose you have an input document that results in XHTML that looks like this:"
498 msgstr ""
499
500 #: ../../../home/kovid/work/calibre/manual/conversion.rst:535
501 msgid "Then, we set the options as::"
502 msgstr ""
503
504 #: ../../../home/kovid/work/calibre/manual/conversion.rst:540
505 msgid "This will result in an automatically generated two level Table of Contents that looks like::"
506 msgstr ""
507
508 #: ../../../home/kovid/work/calibre/manual/conversion.rst:551
509 msgid "Not all output formats support a multi level Table of Contents. You should first try with EPUB output. If that works, then try your format of choice."
510 msgstr ""
511
512 #: ../../../home/kovid/work/calibre/manual/conversion.rst:555
513 msgid "Using images as chapter titles when converting HTML input documents"
514 msgstr ""
515
516 #: ../../../home/kovid/work/calibre/manual/conversion.rst:557
517 msgid "Suppose you want to use an image as your chapter title, but still want calibre to be able to automatically generate a Table of Contents for you from the chapter titles. Use the following HTML markup to achieve this:"
518 msgstr ""
519
520 #: ../../../home/kovid/work/calibre/manual/conversion.rst:571
521 msgid "Set the :guilabel:`Level 1 TOC` setting to ``//h:h2``. Then, for chapter two, calibre will take the title from the value of the ``title`` attribute on the ``<h2>`` tag, since the tag has no text."
522 msgstr ""
523
524 #: ../../../home/kovid/work/calibre/manual/conversion.rst:574
525 msgid "Using tag attributes to supply the text for entries in the Table of Contents"
526 msgstr ""
527
528 #: ../../../home/kovid/work/calibre/manual/conversion.rst:576
529 msgid "If you have particularly long chapter titles and want shortened versions in the Table of Contents, you can use the title attribute to achieve this, for example:"
530 msgstr ""
531
532 #: ../../../home/kovid/work/calibre/manual/conversion.rst:591
533 msgid "Set the :guilabel:`Level 1 TOC` setting to ``//h:h2/@title``. Then calibre will take the title from the value of the ``title`` attribute on the ``<h2>`` tags, instead of using the text inside the tag. Note the trailing ``/@title`` on the XPath expression, you can use this form to tell calibre to get the text from any attribute you like."
534 msgstr ""
535
536 #: ../../../home/kovid/work/calibre/manual/conversion.rst:598
537 msgid "How options are set/saved for conversion"
538 msgstr ""
539
540 #: ../../../home/kovid/work/calibre/manual/conversion.rst:600
541 msgid "There are two places where conversion options can be set in calibre. The first is in Preferences->Conversion. These settings are the defaults for the conversion options. Whenever you try to convert a new book, the settings set here will be used by default."
542 msgstr ""
543
544 #: ../../../home/kovid/work/calibre/manual/conversion.rst:605
545 msgid "You can also change settings in the conversion dialog for each book conversion. When you convert a book, calibre remembers the settings you used for that book, so that if you convert it again, the saved settings for the individual book will take precedence over the defaults set in :guilabel:`Preferences`. You can restore the individual settings to defaults by using the :guilabel:`Restore defaults` button in the individual book conversion dialog. You can remove the saved settings for a group of books by selecting all the books and then clicking the :guilabel:`Edit metadata` button to bring up the bulk metadata edit dialog, near the bottom of the dialog is an option to remove stored conversion settings."
546 msgstr ""
547
548 #: ../../../home/kovid/work/calibre/manual/conversion.rst:616
549 msgid "When you bulk convert a set of books, settings are taken in the following order (last one wins):"
550 msgstr ""
551
552 #: ../../../home/kovid/work/calibre/manual/conversion.rst:618
553 msgid "From the defaults set in Preferences->Conversion"
554 msgstr ""
555
556 #: ../../../home/kovid/work/calibre/manual/conversion.rst:620
557 msgid "From the saved conversion settings for each book being converted (if any). This can be turned off by the option in the top left corner of the Bulk conversion dialog."
558 msgstr ""
559
560 #: ../../../home/kovid/work/calibre/manual/conversion.rst:624
561 msgid "From the settings set in the Bulk conversion dialog"
562 msgstr ""
563
564 #: ../../../home/kovid/work/calibre/manual/conversion.rst:626
565 msgid "Note that the final settings for each book in a Bulk conversion will be saved and re-used if the book is converted again. Since the highest priority in Bulk Conversion is given to the settings in the Bulk conversion dialog, these will override any book specific settings. So you should only bulk convert books together that need similar settings. The exceptions are metadata and input format specific settings. Since the Bulk conversion dialog does not have settings for these two categories, they will be taken from book specific settings (if any) or the defaults."
566 msgstr ""
567
568 #: ../../../home/kovid/work/calibre/manual/conversion.rst:637
569 msgid "You can see the actual settings used during any conversion by clicking the rotating icon in the lower right corner and then double clicking the individual conversion job. This will bring up a conversion log that will contain the actual settings used, near the top."
570 msgstr ""
571
572 #: ../../../home/kovid/work/calibre/manual/conversion.rst:642
573 msgid "Format specific tips"
574 msgstr ""
575
576 #: ../../../home/kovid/work/calibre/manual/conversion.rst:644
577 msgid "Here you will find tips specific to the conversion of particular formats. Options specific to particular format, whether input or output are available in the conversion dialog under their own section, for example `TXT input` or `EPUB output`."
578 msgstr ""
579
580 #: ../../../home/kovid/work/calibre/manual/conversion.rst:649
581 msgid "Convert Microsoft Word documents"
582 msgstr ""
583
584 #: ../../../home/kovid/work/calibre/manual/conversion.rst:651
585 msgid "calibre can automatically convert ``.docx`` files created by Microsoft Word 2007 and newer. Just add the file to calibre and click convert."
586 msgstr ""
587
588 #: ../../../home/kovid/work/calibre/manual/conversion.rst:655
589 msgid "There is a :download_file:`demo .docx file <demos/demo.docx>` that demonstrates the capabilities of the calibre conversion engine. Just download it and convert it to EPUB or AZW3 to see what calibre can do."
590 msgstr ""
591
592 #: ../../../home/kovid/work/calibre/manual/conversion.rst:659
593 msgid "calibre will automatically generate a Table of Contents based on headings if you mark your headings with the ``Heading 1``, ``Heading 2``, etc. styles in Microsoft Word. Open the output e-book in the calibre E-book viewer and click the :guilabel:`Table of Contents` button to view the generated Table of Contents."
594 msgstr ""
595
596 #: ../../../home/kovid/work/calibre/manual/conversion.rst:665
597 msgid "Older .doc files"
598 msgstr ""
599
600 #: ../../../home/kovid/work/calibre/manual/conversion.rst:667
601 msgid "For older .doc files, you can save the document as HTML with Microsoft Word and then convert the resulting HTML file with calibre. When saving as HTML, be sure to use the \"Save as Web Page, Filtered\" option as this will produce clean HTML that will convert well. Note that Word produces really messy HTML, converting it can take a long time, so be patient. If you have a newer version of Word available, you can directly save it as .docx as well."
602 msgstr ""
603
604 #: ../../../home/kovid/work/calibre/manual/conversion.rst:674
605 msgid "Another alternative is to use the free LibreOffice. Open your .doc file in LibreOffice and save it as .docx, which can be directly converted in calibre."
606 msgstr ""
607
608 #: ../../../home/kovid/work/calibre/manual/conversion.rst:678
609 msgid "Convert TXT documents"
610 msgstr ""
611
612 #: ../../../home/kovid/work/calibre/manual/conversion.rst:680
613 msgid "TXT documents have no well defined way to specify formatting like bold, italics, etc, or document structure like paragraphs, headings, sections and so on, but there are a variety of conventions commonly used. By default calibre attempts automatic detection of the correct formatting and markup based on those conventions."
614 msgstr ""
615
616 #: ../../../home/kovid/work/calibre/manual/conversion.rst:685
617 msgid "TXT input supports a number of options to differentiate how paragraphs are detected."
618 msgstr ""
619
620 #: ../../../home/kovid/work/calibre/manual/conversion.rst:687
621 msgid ":guilabel:`Paragraph style: Auto`"
622 msgstr ""
623
624 #: ../../../home/kovid/work/calibre/manual/conversion.rst:688
625 msgid "Analyzes the text file and attempts to automatically determine how paragraphs are defined. This option will generally work fine, if you achieve undesirable results try one of the manual options."
626 msgstr ""
627
628 #: ../../../home/kovid/work/calibre/manual/conversion.rst:691
629 msgid ":guilabel:`Paragraph style: Block`"
630 msgstr ""
631
632 #: ../../../home/kovid/work/calibre/manual/conversion.rst:692
633 msgid "Assumes one or more blank lines are a paragraph boundary::"
634 msgstr ""
635
636 #: ../../../home/kovid/work/calibre/manual/conversion.rst:699
637 msgid ":guilabel:`Paragraph style: Single`"
638 msgstr ""
639
640 #: ../../../home/kovid/work/calibre/manual/conversion.rst:700
641 msgid "Assumes that every line is a paragraph::"
642 msgstr ""
643
644 #: ../../../home/kovid/work/calibre/manual/conversion.rst:706
645 msgid ":guilabel:`Paragraph style: Print`"
646 msgstr ""
647
648 #: ../../../home/kovid/work/calibre/manual/conversion.rst:707
649 msgid "Assumes that every paragraph starts with an indent (either a tab or 2+ spaces). Paragraphs end when the next line that starts with an indent is reached::"
650 msgstr ""
651
652 #: ../../../home/kovid/work/calibre/manual/conversion.rst:717
653 msgid ":guilabel:`Paragraph style: Unformatted`"
654 msgstr ""
655
656 #: ../../../home/kovid/work/calibre/manual/conversion.rst:718
657 msgid "Assumes that the document has no formatting, but does use hard line breaks. Punctuation and median line length are used to attempt to re-create paragraphs."
658 msgstr ""
659
660 #: ../../../home/kovid/work/calibre/manual/conversion.rst:721
661 msgid ":guilabel:`Formatting style: Auto`"
662 msgstr ""
663
664 #: ../../../home/kovid/work/calibre/manual/conversion.rst:722
665 msgid "Attempts to detect the type of formatting markup being used. If no markup is used then heuristic formatting will be applied."
666 msgstr ""
667
668 #: ../../../home/kovid/work/calibre/manual/conversion.rst:725
669 msgid ":guilabel:`Formatting style: Heuristic`"
670 msgstr ""
671
672 #: ../../../home/kovid/work/calibre/manual/conversion.rst:726
673 msgid "Analyzes the document for common chapter headings, scene breaks, and italicized words and applies the appropriate HTML markup during conversion."
674 msgstr ""
675
676 #: ../../../home/kovid/work/calibre/manual/conversion.rst:729
677 msgid ":guilabel:`Formatting style: Markdown`"
678 msgstr ""
679
680 #: ../../../home/kovid/work/calibre/manual/conversion.rst:730
681 msgid "calibre also supports running TXT input though a transformation preprocessor known as Markdown. Markdown allows for basic formatting to be added to TXT documents, such as bold, italics, section headings, tables, lists, a Table of Contents, etc. Marking chapter headings with a leading # and setting the chapter XPath detection expression to \"//h:h1\" is the easiest way to have a proper table of contents generated from a TXT document. You can learn more about the Markdown syntax at `daringfireball <https://daringfireball.net/projects/markdown/syntax>`_."
682 msgstr ""
683
684 #: ../../../home/kovid/work/calibre/manual/conversion.rst:736
685 msgid ":guilabel:`Formatting style: None`"
686 msgstr ""
687
688 #: ../../../home/kovid/work/calibre/manual/conversion.rst:737
689 msgid "Applies no special formatting to the text, the document is converted to HTML with no other changes."
690 msgstr ""
691
692 #: ../../../home/kovid/work/calibre/manual/conversion.rst:742
693 msgid "Convert PDF documents"
694 msgstr ""
695
696 #: ../../../home/kovid/work/calibre/manual/conversion.rst:744
697 msgid "PDF documents are one of the worst formats to convert from. They are a fixed page size and text placement format. Meaning, it is very difficult to determine where one paragraph ends and another begins. calibre will try to unwrap paragraphs using a configurable, :guilabel:`Line un-wrapping factor`. This is a scale used to determine the length at which a line should be unwrapped. Valid values are a decimal between 0 and 1. The default is 0.45, just under the median line length. Lower this value to include more text in the unwrapping. Increase to include less. You can adjust this value in the conversion settings under :guilabel:`PDF Input`."
698 msgstr ""
699
700 #: ../../../home/kovid/work/calibre/manual/conversion.rst:751
701 msgid "Also, they often have headers and footers as part of the document that will become included with the text. Use the :guilabel:`Search and replace` panel to remove headers and footers to mitigate this issue. If the headers and footers are not removed from the text it can throw off the paragraph unwrapping. To learn how to use the header and footer removal options, read :ref:`regexptutorial`."
702 msgstr ""
703
704 #: ../../../home/kovid/work/calibre/manual/conversion.rst:756
705 msgid "Some limitations of PDF input are:"
706 msgstr ""
707
708 #: ../../../home/kovid/work/calibre/manual/conversion.rst:758
709 msgid "Complex, multi-column, and image based documents are not supported."
710 msgstr ""
711
712 #: ../../../home/kovid/work/calibre/manual/conversion.rst:759
713 msgid "Extraction of vector images and tables from within the document is also not supported."
714 msgstr ""
715
716 #: ../../../home/kovid/work/calibre/manual/conversion.rst:760
717 msgid "Some PDFs use special glyphs to represent ll or ff or fi, etc. Conversion of these may or may not work depending on just how they are represented internally in the PDF."
718 msgstr ""
719
720 #: ../../../home/kovid/work/calibre/manual/conversion.rst:761
721 msgid "Links and Tables of Contents are not supported"
722 msgstr ""
723
724 #: ../../../home/kovid/work/calibre/manual/conversion.rst:762
725 msgid "PDFs that use embedded non-Unicode fonts to represent non-English characters will result in garbled output for those characters"
726 msgstr ""
727
728 #: ../../../home/kovid/work/calibre/manual/conversion.rst:763
729 msgid "Some PDFs are made up of photographs of the page with OCRed text behind them. In such cases calibre uses the OCRed text, which can be very different from what you see when you view the PDF file"
730 msgstr ""
731
732 #: ../../../home/kovid/work/calibre/manual/conversion.rst:764
733 msgid "PDFs that are used to display complex text, like right to left languages and math typesetting will not convert correctly"
734 msgstr ""
735
736 #: ../../../home/kovid/work/calibre/manual/conversion.rst:766
737 msgid "To re-iterate **PDF is a really, really bad** format to use as input. If you absolutely must use PDF, then be prepared for an output ranging anywhere from decent to unusable, depending on the input PDF."
738 msgstr ""
739
740 #: ../../../home/kovid/work/calibre/manual/conversion.rst:770
741 msgid "Comic book collections"
742 msgstr ""
743
744 #: ../../../home/kovid/work/calibre/manual/conversion.rst:772
745 msgid "A comic book collection is a .cbc file. A .cbc file is a ZIP file that contains other CBZ/CBR files. In addition the .cbc file must contain a simple text file called comics.txt, encoded in UTF-8. The comics.txt file must contain a list of the comics files inside the .cbc file, in the form filename:title, as shown below::"
746 msgstr ""
747
748 #: ../../../home/kovid/work/calibre/manual/conversion.rst:780
749 msgid "The .cbc file will then contain::"
750 msgstr ""
751
752 #: ../../../home/kovid/work/calibre/manual/conversion.rst:787
753 msgid "calibre will automatically convert this .cbc file into an e-book with a Table of Contents pointing to each entry in comics.txt."
754 msgstr ""
755
756 #: ../../../home/kovid/work/calibre/manual/conversion.rst:791
757 msgid "EPUB advanced formatting demo"
758 msgstr ""
759
760 #: ../../../home/kovid/work/calibre/manual/conversion.rst:793
761 msgid "Various advanced formatting for EPUB files is demonstrated in this :download_file:`demo file <demos/demo.epub>`. The file was created from hand coded HTML using calibre and is meant to be used as a template for your own EPUB creation efforts."
762 msgstr ""
763
764 #: ../../../home/kovid/work/calibre/manual/conversion.rst:796
765 msgid "The source HTML it was created from is available :download_file:`demo.zip <demos/demo.zip>`. The settings used to create the EPUB from the ZIP file are::"
766 msgstr ""
767
768 #: ../../../home/kovid/work/calibre/manual/conversion.rst:801
769 msgid "Note that because this file explores the potential of EPUB, most of the advanced formatting is not going to work on readers less capable than calibre's built-in EPUB viewer."
770 msgstr ""
771
772 #: ../../../home/kovid/work/calibre/manual/conversion.rst:805
773 msgid "Convert ODT documents"
774 msgstr ""
775
776 #: ../../../home/kovid/work/calibre/manual/conversion.rst:807
777 msgid "calibre can directly convert ODT (OpenDocument Text) files. You should use styles to format your document and minimize the use of direct formatting. When inserting images into your document you need to anchor them to the paragraph, images anchored to a page will all end up in the front of the conversion."
778 msgstr ""
779
780 #: ../../../home/kovid/work/calibre/manual/conversion.rst:810
781 msgid "To enable automatic detection of chapters, you need to mark them with the built-in styles called :guilabel:`Heading 1`, :guilabel:`Heading 2`, ..., :guilabel:`Heading 6` (:guilabel:`Heading 1` equates to the HTML tag ``<h1>``, :guilabel:`Heading 2` to ``<h2>``, etc). When you convert in calibre you can enter which style you used into the :guilabel:`Detect chapters at` box. Example:"
782 msgstr ""
783
784 #: ../../../home/kovid/work/calibre/manual/conversion.rst:816
785 msgid "If you mark Chapters with style :guilabel:`Heading 2`, you have to set the 'Detect chapters at' box to ``//h:h2``"
786 msgstr ""
787
788 #: ../../../home/kovid/work/calibre/manual/conversion.rst:817
789 msgid "For a nested TOC with Sections marked with :guilabel:`Heading 2` and the Chapters marked with :guilabel:`Heading 3` you need to enter ``//h:h2|//h:h3``. On the Convert - TOC page set the :guilabel:`Level 1 TOC` box to ``//h:h2`` and the :guilabel:`Level 2 TOC` box to ``//h:h3``."
790 msgstr ""
791
792 #: ../../../home/kovid/work/calibre/manual/conversion.rst:819
793 msgid "Well-known document properties (Title, Keywords, Description, Creator) are recognized and calibre will use the first image (not too small, and with good aspect-ratio) as the cover image."
794 msgstr ""
795
796 #: ../../../home/kovid/work/calibre/manual/conversion.rst:821
797 msgid "There is also an advanced property conversion mode, which is activated by setting the custom property ``opf.metadata`` ('Yes or No' type) to Yes in your ODT document (File->Properties->Custom Properties). If this property is detected by calibre, the following custom properties are recognized (``opf.authors`` overrides document creator)::"
798 msgstr ""
799
800 #: ../../../home/kovid/work/calibre/manual/conversion.rst:834
801 msgid "In addition to this, you can specify the picture to use as the cover by naming it ``opf.cover`` (right click, Picture->Options->Name) in the ODT. If no picture with this name is found, the 'smart' method is used. As the cover detection might result in double covers in certain output formats, the process will remove the paragraph (only if the only content is the cover!) from the document. But this works only with the named picture!"
802 msgstr ""
803
804 #: ../../../home/kovid/work/calibre/manual/conversion.rst:841
805 msgid "To disable cover detection you can set the custom property ``opf.nocover`` ('Yes or No' type) to Yes in advanced mode."
806 msgstr ""
807
808 #: ../../../home/kovid/work/calibre/manual/conversion.rst:844
809 msgid "Converting to PDF"
810 msgstr ""
811
812 #: ../../../home/kovid/work/calibre/manual/conversion.rst:846
813 msgid "The first, most important, setting to decide on when converting to PDF is the page size. By default, calibre uses a page size of \"U.S. Letter\". You can change this to another standard page size or a completely custom size in the :guilabel:`PDF Output` section of the conversion dialog. If you are generating a PDF to be used on a specific device, you can turn on the option to use the page size from the :guilabel:`output profile` instead. So if your output profile is set to Kindle, calibre will create a PDF with page size suitable for viewing on the small Kindle screen."
814 msgstr ""
815
816 #: ../../../home/kovid/work/calibre/manual/conversion.rst:856
817 msgid "Headers and Footers"
818 msgstr ""
819
820 #: ../../../home/kovid/work/calibre/manual/conversion.rst:857
821 msgid "You can insert arbitrary headers and footers on each page of the PDF by specifying header and footer templates. Templates are just snippets of HTML code that get rendered in the header and footer locations. For example, to display page numbers centered at the bottom of every page, in green, use the following footer template::"
822 msgstr ""
823
824 #: ../../../home/kovid/work/calibre/manual/conversion.rst:865
825 msgid "calibre will automatically replace :code:`_PAGENUM_` with the current page number. You can even put different content on even and odd pages, for example the following header template will show the title on odd pages and the author on even pages::"
826 msgstr ""
827
828 #: ../../../home/kovid/work/calibre/manual/conversion.rst:874
829 msgid "calibre will automatically replace :code:`_TITLE_` and :code:`_AUTHOR_` with the title and author of the document being converted. Setting :code:`justify-content` to :code:`flex-end` will cause the text to be right aligned."
830 msgstr ""
831
832 #: ../../../home/kovid/work/calibre/manual/conversion.rst:879
833 msgid "You can also display text at the left and right edges and change the font size, as demonstrated with this header template::"
834 msgstr ""
835
836 #: ../../../home/kovid/work/calibre/manual/conversion.rst:887
837 msgid "This will display the title at the left and the author at the right, in a font size smaller than the main text."
838 msgstr ""
839
840 #: ../../../home/kovid/work/calibre/manual/conversion.rst:890
841 msgid "You can also use the current section in templates, as shown below::"
842 msgstr ""
843
844 #: ../../../home/kovid/work/calibre/manual/conversion.rst:894
845 msgid ":code:`_SECTION_` is replaced by whatever the name of the current section is. These names are taken from the metadata Table of Contents in the document (the PDF Outline). If the document has no table of contents then it will be replaced by empty text. If a single PDF page has multiple sections, the first section on the page will be used. Similarly, there is a variable named :code:`_TOP_LEVEL_SECTION_` that can be used to get the name of the current top-level section."
846 msgstr ""
847
848 #: ../../../home/kovid/work/calibre/manual/conversion.rst:901
849 msgid "You can even use JavaScript inside the header and footer templates, for example, the following template will cause page numbers to start at 4 instead of 1::"
850 msgstr ""
851
852 #: ../../../home/kovid/work/calibre/manual/conversion.rst:911
853 msgid "In addition there are some more variables you can use in the headers and footers, documented below:"
854 msgstr ""
855
856 #: ../../../home/kovid/work/calibre/manual/conversion.rst:914
857 msgid "``_TOTAL_PAGES_`` - total number of pages in the PDF file, useful for implementing a progress counter, for example."
858 msgstr ""
859
860 #: ../../../home/kovid/work/calibre/manual/conversion.rst:916
861 msgid "``_TOP_LEVEL_SECTION_PAGES_`` - total number of pages in the current top level section"
862 msgstr ""
863
864 #: ../../../home/kovid/work/calibre/manual/conversion.rst:918
865 msgid "``_TOP_LEVEL_SECTION_PAGENUM_`` - the page number of the current page within the current top level section"
866 msgstr ""
867
868 #: ../../../home/kovid/work/calibre/manual/conversion.rst:920
869 msgid "``_WIDTH_PIXELS_`` - the width of the header/footer area in pixels"
870 msgstr ""
871
872 #: ../../../home/kovid/work/calibre/manual/conversion.rst:921
873 msgid "``_HEIGHT_PIXELS_`` - the height of the header/footer area in pixels"
874 msgstr ""
875
876 #: ../../../home/kovid/work/calibre/manual/conversion.rst:923
877 msgid "When adding headers and footers make sure you set the page top and bottom margins to large enough values, under the :guilabel:`PDF Output` section of the conversion dialog."
878 msgstr ""
879
880 #: ../../../home/kovid/work/calibre/manual/conversion.rst:928
881 msgid "Printable Table of Contents"
882 msgstr ""
883
884 #: ../../../home/kovid/work/calibre/manual/conversion.rst:930
885 msgid "You can also insert a printable Table of Contents at the end of the PDF that lists the page numbers for every section. This is very useful if you intend to print out the PDF to paper. If you wish to use the PDF on an electronic device, then the PDF Outline provides this functionality and is generated by default."
886 msgstr ""
887
888 #: ../../../home/kovid/work/calibre/manual/conversion.rst:935
889 msgid "You can customize the look of the generated Table of contents by using the Extra CSS conversion setting under the Look & feel part of the conversion dialog. The default CSS used is listed below, simply copy it and make whatever changes you like."
890 msgstr ""
891
892 #: ../../../home/kovid/work/calibre/manual/conversion.rst:955
893 msgid "Custom page margins for individual HTML files"
894 msgstr ""
895
896 #: ../../../home/kovid/work/calibre/manual/conversion.rst:957
897 msgid "If you are converting an EPUB or AZW3 file with multiple individual HTML files inside it and you want to change the page margins for a particular HTML file you can add the following style block to the HTML file using the calibre E-book editor:"
898 msgstr ""
899
900 #: ../../../home/kovid/work/calibre/manual/conversion.rst:974
901 msgid "Then, in the PDF output section of the conversion dialog, turn on the option to :guilabel:`Use page margins from the document being converted`. Now all pages generated from this HTML file will have ``10pt`` margins."
902 msgstr ""