View Single Post
Old 03-28-2010, 06:46 PM   #13
DVC
Junior Member
DVC began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2010
Device: iPhone 3Gs
Lot's of answers, but they all make my point.

First, .doc is not supported so that route is closed.

Second, converting to HTML will destroy a book's format. The result will be as bad as a web-page. I know, I've used Word to make HTMLs.

LIT? What the hell is that? I don't know where you live, but there is only one universal document standard and that is PDF. Since the rules of decoding PDF are decades old, why would anyone design a conversion program that accepted PDF as the "last" choice? In reality, PDF is the only input format needed for making eBooks.

Why list RTF if it can't convert an RTF with pictures. Telling me there may be pix format that is not supported only means RTF is not really fully supported. RTF means RTF as it comes from any software that produces it. Since almost every RTF document includes pix -- a conversion program has be able to deal with all pix. What's so radical about JPEGs?

And, the suggestions that one convert to X and then convert to Y to get to Z are just plain silly. At each step, more formating will be screwed-up. When one uses a graphics conversion program -- it just does the job.

And, since EPUB is designed for BOOKS -- the comments that one cannot expect to convert BOOKS kind of defeats the purpose of a CONVERTER TO EPUB. Now, were there a way to interactively edit the EPUB output so one could fix conversion problems -- it would be acceptable given the likelihood of conversion errors. But, there isn't. The Debug feature is a joke -- a folder full of .jpegs.)

Sorry, to be so negative, but Caliber simply doesn't make eBooks than can be sold. So, I'm not sure why it was written. Converting LIT to EPUB. Why?

Last edited by DVC; 03-28-2010 at 06:52 PM.
DVC is offline   Reply With Quote