Quote:
Originally Posted by jdunning
Coming from the web world, it feels simpler to have a single HTML file with clean markup and CSS as the source of truth, and which can then be converted to other formats. It also makes it easier to do global changes, search and replace, etc. I appreciate Calibre's ability to convert the CSS cascade to multiple classes as needed, but editing the processed files means it gets out of sync with the HTML.
I get that Calibre currently assumes books are single files, but it already handles multiple files within zips, so it seems like it would be a small step to read those same files from a folder, rather than an archive. Or maybe a plugin could do it.
|
Look at how the search and replace works in Calibre's editor; there are 6 modes; current file, all text files, all style files, selected files, open files, and marked text. You can hardly ask for more for doing global changes.
Calibre doesn't assume that books are a single file. The final packaging is a single file; that's mandated by the format, epub, azw, etc.
Whenever I convert a web page(s) to an ebook I import the files into the editor and do all my work there. Sometimes it's multiple web pages, some times one. Regardless, I've never felt the need to do anything with the originals unless I screw up and need to start over.