Quote:
Originally Posted by Valloric
We've also hit the classic converter vs editor debate. As a perfectionist, I want the text I edit in whatever editor I use to end up exactly that way in the format I want. Converters can't guarantee you that. They could change some minor things, and they usually do. If I go to hours upon hours of trouble to proofread a book I've scanned (for personal use), I do not want to have to go through it all again. The editor should be the last line of defense: when you get the text right there, it should end up that way in the resulting file. IMO, at least.
I do plan on using a wide variety of open source code to create all the other parts of the application. Like for instance wxWidgets for that native look-and-feel on all platforms.
|
oh, i do understand that, although i fear there you may run into some frustrating limitations depending on which format you are creating, regardless of the method. for instance, i gave up on creating a mobipocket version of my illustrated "three men in a boat" by Jerome K. Jerome when i discovered that mobipocket cannot support floated images
instead it inserts them in between blocks of text, which in this particular case completely broke the flow of the book, as most of the illustrations were designed to have text wrapped around them, particularly the illuminated lettrines of each chapter.
in that case there is not much you can do, sadly.
however, no converter should modify the *text* of the book even if they might modify the format because of unsupported features.
but, it is your tool, so you can do whatever you prefer.
i was just trying to be helpful.
