View Single Post
Old 05-06-2009, 06:38 AM   #5
tibiafry
Enthusiast
tibiafry has learned how to buy an e-book online
 
tibiafry's Avatar
 
Posts: 43
Karma: 78
Join Date: Jan 2009
Device: Iliad
Quote:
Originally Posted by ondabeach View Post
Hi TibiaFry,

You could try exporting from InDesign in a different format and then using another program (calibre) for example to convert that to ePub format. Also since you say you currently produce books in mobipocket format, I beleive mobipocket have a free program for creating ePubs forem mobi format books, I think it's called Mobipocket Creator? Something like that anyway.

Cheers,

Steve (ondabeach)
The problem exporting to another format is even worse, since ePub export function is essentially build to generate ePubs. If I make a standard xml, the format "tagging" is lost, and the work to do is even harder. With PDF, for instance, I would have to re-arrange all the formatting too. So that's not an option. In fact, to create a Mobipocket we plan to use ePub as source, since once I have the correct ePub working, the conversion from this ePub to mobi is fast and reliable.

Quote:
Originally Posted by mtravellerh View Post
1. Forget InDesign
Your approach to edit xhtml files is the right one. Just do that directly without involving InDesign's crappy code.

2.The mobi, as you might know, doesn't support the xhtml stylesheets in its entirety. Don't even try to convert a (more sophisticated ) epub file directly to Mobi. Won't work. You need an xhtml source file to create both book files from. page breaks, however, should work fine with both formats. Better use them directly in the source file, though (no external page break style to a tag)

3 HanLin's support of epub files is crap, too. No CSS supported whatsoever and the book is essentially flatlined.
1. I'm afraid I can't forget InDesign, for the simple fact that the book is only in this format. So I need to start from InDesign either I want it or not .

2. I didn't knew that one. I realize (with point 3 too) that css is more a problem than a solution. I think I could make a script to split the xhtml into several ones, but it would take me some time (maybe that's the best solution for that). So how do I create that xhtml source file avoiding all of the problems of my first post? (HA!). Do you know where I can read more about css integration with the formats and how much of it is supported for every reader? One thing that annoys me is that ADE or Mobipocket reader display a thing and then the eReaders display another thing. WTF. (and I'm not talking about reflowable text, I'm talking about «serious business»)

3. I see...


Thanks for both of your replies.
tibiafry is offline   Reply With Quote