![]() Lastly, and I'm not sure I read this part right, but if you're getting rid of the original file, you can never reconvert. (Alright, that might be oversimplifying things, but.) Additionally, while hard drive space is inexpensive, their is little need to have multiple variant copies of the same ebook, differing primarily on screen resolution and CSS. The resulting ebook format would then be retained indefinitely - losing the advantage of any newly programmed conversion engine upgrades. What you are asking for, in effect, is that a book be converted either at the time it's added or on demand. You always have and can re-convert as needed because you always have the original ebook file as the publisher released it. This means that ebooks are always as capable and functional as Kovid & Programmers, et al, can manage at the time of conversion. My limited impression is that calibre is meant to take whatever original source ebook format you have and, on demand, to convert the book to a format that your software or hardware ereader can view at time of transfer. I do recall Kovid mentioning it was a low priority project as other aspects of calibre would have to be substantially altered before this could be made to work.Īt least, that is the overall impression I got, I might have misunderstood.ĭespite the above, I'm not sure that what you want fits within the overall workflow method that calibre uses. Kovid did mention altering the database structure to allow one-to-many situations, but I cannot recall if this was for a specific aspect only (multiple covers, editions, formats, reprints, etc), or in general throughout the database. You are looking for a one-to-many database function and it doesn't exist in calibre at this time. I cannot imagine a way to implement something like this under calibre's current file structure without entering them as multiple books. Is this something that can be done already, somehow, or if not, would it be possible to implement, without re-writing half of the program? When sending a specific format to a device, one would be able to choose. Then it would be possible to take the original EPUB, and convert it for any reader, like so:ĭickens, Charles - A Christmas Carol.epub (original file, input file for later operations)ĭickens, Charles - A Christmas Carol.kobo_glo.epubĭickens, Charles - A Christmas Carol.kobo_aura.epubĭickens, Charles - A Christmas Carol.sony_t1.epubĭickens, Charles - A Christmas Carol.bokeen_gen3.epub However, I'd much prefer to give a format a name, when converting. When connecting that specific reader, switch to that library. You could of course create a seperate library for each e-reader, copy a book there, reconvert the file, and throw ORIGINAL_EPUB away. What happens if someone has 3 EPUB readers, and wants different conversions for all of them, for some reason? As far as I can see, you can't have three EPUB's in the library and then choose which to upload to the connected reader. While it works, I personally don't really like it, as there are other functions that use or create that format. If this person converts the EPUB to one with built-in font, the original EPUB will be called ORIGINAL_EPUB. That's nice, because now I can convert all books to AZW3 and embed the font I'd like, if I so choose. My main library is entirely EPUB-based, while the Kindle uses AZW3. ![]() ![]() I was thinking: The Kindle does not (officially) support adding user fonts. Is it somehow possible to have one book, containing multiple versions of the same format? ![]()
0 Comments
Leave a Reply. |