MobileRead Forums - View Single Post

ashkulz · 09-02-2008, 05:52 PM

I've added a patch for #1 as ticket #993. I'd appreciate some pointers on what needs to be done for #2 (I think it is taken care of by the patch, but I'm not sure).

Also, for #3: I think it'd be possible to check that impmake exists on the path (e.g. using impmake -v) and if so, doing the html2imp conversion [or else bailing out]. For bundling, impmake depends on eBook Publisher so that'd be required to be bundled. I feel that leaving it out of the bundle (and checking its presence at runtime) would make more sense, as unfortunately there is no native HTML -> IMP conversion (you'll need to build an almost complete HTML renderer which matches their ROM and fonts).

What do you think?

09-02-2008, 05:52 PM	#4
ashkulz Addict Posts: 350 Karma: 705 Join Date: Dec 2006 Location: Mumbai, India Device: Kindle 1/REB 1200	I've added a patch for #1 as ticket #993. I'd appreciate some pointers on what needs to be done for #2 (I think it is taken care of by the patch, but I'm not sure). Also, for #3: I think it'd be possible to check that impmake exists on the path (e.g. using impmake -v) and if so, doing the html2imp conversion [or else bailing out]. For bundling, impmake depends on eBook Publisher so that'd be required to be bundled. I feel that leaving it out of the bundle (and checking its presence at runtime) would make more sense, as unfortunately there is no native HTML -> IMP conversion (you'll need to build an almost complete HTML renderer which matches their ROM and fonts). What do you think? Last edited by ashkulz; 09-02-2008 at 06:02 PM.