Cutlery/calibre
1
0
Fork 0
mirror of https://github.com/kovidgoyal/calibre.git synced 2025-07-09 03:04:10 -04:00
Code Issues Packages Projects Releases Wiki Activity

String changes

Browse Source
This commit is contained in:
Kovid Goyal 2018-08-10 08:22:50 +05:30
parent 668e208611
commit 0830a0d9a0
No known key found for this signature in database
GPG Key ID: 06BC317B515ACE7C
1 changed files with 87 additions and 88 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
manual/conversion.rst
View File

@ -46,9 +46,9 @@ Schematically, it looks like this:
:align: center
:alt: The conversion pipeline
The input format is first converted to XHTML by the appropriate *Input Plugin*.
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
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>`.
@ -56,10 +56,10 @@ is available :ref:`here <best-source-formats>`.
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 remeber 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
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
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.
You can see this process in action by using the debug option |dbgi|. Just specify the path to
@ -72,10 +72,10 @@ The four sub-directories are:
========== =============
Directory Description
========== =============
input This contains the HTML output by the Input Plugin. Use this to debug the Input Plugin.
parsed The result of pre-processing and converting to XHTML the output from the Input Plugin. Use to debug structure detection.
input This contains the HTML output by the Input plugin. Use this to debug the Input plugin.
parsed The result of pre-processing and converting to XHTML the output from the Input plugin. Use to debug structure detection.
structure Post structure detection, but before CSS flattening and font size conversion. Use to debug font size conversion and CSS transforms.
processed Just before the e-book is passed to the output plugin. Use to debug the output plugin.
processed Just before the e-book is passed to the Output plugin. Use to debug the Output plugin.
========== =============
If you want to edit the input document a little before having calibre convert it, the best thing to
@ -898,4 +898,3 @@ changes you like.
.calibre-pdf-toc .level-1 td:first-of-type { padding-left: 1.4em }
.calibre-pdf-toc .level-2 td:first-of-type { padding-left: 2.8em }