Quote:
Originally Posted by Manichean
Personally, I don't see the benefit- if I want to have images in a text, I use a format that supports images, e.g. HTML.
As for the "cover storage", there was talk some time ago about including some storage method for formats that eventually lead to a ticket being created, but I don't know if anyone has put it on any todo list  It wouldn't make sense, in my opinion, to develop a separate storage system for old covers, if we are to get such a system, it should be one system for all the files associated with a book entry. |
I think the point is that having something along these lines would allow for easier ebook creation. Using markdown/textile is far more accessible/easier to format than html, and generally quite well suited to basic ebook authoring requirements. I've done one paper book that I had a copy of along with a completely unformatted text file. Markdown, a very small amount of html, along with Calibre's extra_css, and Calibre spit out a book that had 95% of the formatting of the print book.
The implementation in Calibre is the harder part - handling the images during conversion, storing them, etc. Something along the same lines as zipped html might work...