Quote:
Originally Posted by crutledge
Since I work mostly with Gutenberg, I'll use it as an example.
I download, if there, the complete book.hrm files. This also downloads any images. I also download the book.txt in US ASCII. Using Gutentext, a book.html is created. Although I have regex expressions to clear BD of the ash and trash from the book.htm e.g. page numbers, etc., this is less work. The book.html is then dropped into BD. I open the book.htm in the browser and vertically tile with browser on the left and BD on the right. From this point on, the procedure is the same for any html file...
|
This is basically what my
GuteBook program tries to do automatically for you, but "manual intervention" will ALWAYS produce a better ebook. A while ago, I looked at some Gutenberg .txt you converted to ebooks to see if GuteBook could do the same but it couldn't match the quality that you produced with BD with (manual) insertion of images/toc. I got close, but not 100%!
Looking at your post, I guess I can now try to automate your steps within my GuteBook.pl Perl script. Thanks, Charlie, for the excellent write-up!!!
So, in your case, getting the source .html to produce a presentable .prc can then lead to a presentable .lrf/.epub using calibre and a presentable .imp using Mobi2IMP!!!
