Alright, with further inspection, I'm pretty sure the Input Plugin is being leveraged is
https://github.com/kovidgoyal/calibr.../html_input.py
I also know the HTML document fed to that plugin is valid.
And I was also able to activate some debugging from ebook-convert!
Quote:
debug: InputFormatPlugin: HTML Input running
on /tmp/tmp-82696wkvncw/SUMMARY.html
debug: Creator not specified
debug: Building file list...
debug: Normalizing filename cases
debug: Rewriting HTML links
debug: 34% Exécution des transformations du livre numérique…
debug: Merging user specified metadata...
debug: Detecting structure...
debug: Detected chapter: Introduction
debug: Detected chapter: Quick-start
debug: Auto generated TOC with 2 entries.
debug: Flattening CSS and remapping font sizes...
debug: Source base font size is 25.92000pt
debug: Removing fake margins...
debug: Cleaning up manifest...
Trimming unused files from manifest...
debug: Creating PDF Output...
debug: 67% Exécution de l'extension PDF Output
debug: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
debug: Bottom margin is too small for footer, increasing it to 18.0pts
debug: 78% Rendered SUMMARY.html
debug: 89% Rendered index.html
debug: 100% Rendered quick-start.html
debug: Rendered PDF in 0.571188 seconds:
debug: PDF output written to /tmp/tmp-82696wkvncw/index.pdf
debug: Sortie sauvegardée vers /tmp/tmp-82696wkvncw/index.pdf
|
Too bad I never get a chance to have a look at /tmp/tmp-82696wkvncw/SUMMARY.html before the conversion process ends, for it gets destroyed: I would then be able to actually see what is being fed to the Input Plugin.
What I was unable to discover as well, from inspecting Calibre's codebase, is how this HTML document is going to be transformed into Calibre's internal XHTML for further processing/conversion.