Quote:
Originally Posted by llasram
I'm working on an "oeb2mobi" for Calibre which will allow the generation of Mobipocket books from OEB XHTML+CSS content.
|
Where do you envision the input oeb files will come from?
- User created? Those that prepare ebooks from HTML could create/modify their .html as well as create the accompanying .opf file and "pass" it to oeb2mobi; or
- Program created? Mobipocket Creator saves a .opf file that could be used as input for "oeb2mobi" (I know what's the point). Moreover, I can modify a Mobipocket .opf for it to load into the .imp creation software eBook Publisher and use that to create .imp ebook. There is python code in PDFRead's output.py which shows how to use/call the eBook Publisher's OLE/COM .dll (windows only). I've also got Perl scripts doing the same thing, which is easy enough to create a windows executable from (again windows only).
Quote:
|
After that, I want to try to shore up differences among the outputs of Calibre's various target format conversions. The goal would be to allow book creators to use one standards-compliant HTML source and produce books which look "the same as possible" in all the various output formats. No IMP support yet, but perhaps one day...
|
I think Ashish Kulkarni (original author of PDFRead) has already done some work with Kovid in getting the .imp format better supported by Calibre. So I will let them tackle this first and wait on the sidelines until I can be of assistance.
