View Single Post
Old 04-29-2011, 07:49 PM   #4
user_none
Sigil & calibre developer
user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.
 
user_none's Avatar
 
Posts: 2,487
Karma: 1063785
Join Date: Jan 2009
Location: Florida, USA
Device: Nook STR
I knew it was somewhere. In the README.txt in the debug directory:



This debug directory contains snapshots of the e-book as it passes through the
various stages of conversion. The stages are:

1. input - This is the result of running the input plugin on the source
file. Use this directory to debug the input plugin.

2. parsed - This is the result of preprocessing and parsing the output of
the input plugin. Note that for some input plugins this will be identical to
the input sub-directory. Use this directory to debug structure detection,
etc.

3. structure - This corresponds to the stage in the pipeline when structure
detection has run, but before the CSS is flattened. Use this directory to
debug the CSS flattening, font size conversion, etc.

4. processed - This corresponds to the e-book as it is passed to the output
plugin. Use this directory to debug the output plugin.
user_none is offline   Reply With Quote