Quote:
Originally Posted by odedta
Well, that was over a year ago so I can't really be sure, but I remember that once I created the validated ePub with all the Amazon guidelines and iBooks guidelines in 1 file and passed it through Kindle Previewer it seems just like the ePub.
I think it was a Reflowable Fixed Layout ebook so somehow the mobi turned out well, oh well, that's all in the past now, no reason to dwell on things that don't work.
|
Okay, now you're making my head spin. A
REFLOWABLE FXL? You mean, the text on each page reflows to fit the screen, w/o moving to the ensuring "page?" Is that what you mean? No complaints from customers?
Quote:
|
So, how do you go about creating a mobi file? epub -> mobi? book creator?
|
Wow, I feel really...antiquated. We code them by hand. We have various in-house templates, for sizing (single-pg landscape, spreads-landscape, portrait, etc.) and we plug in the sizes, etc., using regex. Then we make the pages one at a time. Naturally, we batch-process the background images, but you'd be surprised how often that cannot be done, and we end up redoing them manually, one at a time. {shrug}. That's the business we're in, though.
Obviously, there's no way to position the dialogue/text boxes for pop-up/RM. And our styling (CSS) changes for each book. Different text box colors, different fonts...but we can use a bunch of the "template" CSS to at least get us a starting place.
I would not use KKBC, et al, for a commercial book. Too many limits on what we can/can't change easily.
Obviously, fairly often we are making both ePUB/MOBI (not to mention ePIB for B&N). When we do that, we grab what we can reuse from the first book--usually the ePUB--and cobble it together with new custom material for the next (usually MOBI).
The ePIB is made using Nook's proprietary software
COUGH,HACK,
so nothing is reusable there.
No secret sauce magic tricks, I'm afraid.
Hitch