Quote:
Originally Posted by gsbe
I see this type of answer a lot to people's ID questions. Can't speak for all ID users but I'm trying to write a book and publish it in the shortest amount of time required.
|
That's not what I was hinting at.
Alot of people who post here
EXPECT just because ID
can output to ePub, reads ID is a drive away no more pay epub creator...and get really upset when they find out they have to do additional work.
Quote:
Originally Posted by gsbe
I have decided to compose the book in ID for two reasons: - ID looks a bit more inspiring to compose text in than a text editor
- ID is supposed to save me time tweaking the output for EPUB
I understand that the output isn't going to be perfect. BUT - I want it to be as perfect as ID is capable of before rolling up my sleeves. |
Yes it does all this to the best of it's ability. the ePub spec which is adheres to is a dumbed down version of an ID document. Featureless.
Quote:
Originally Posted by gsbe
I think this is pretty obvious but I see this response a lot...the knee-jerk response is "oh, ID user...must be a newbie that isn't ready for XHTML/CSS". That's not it, we just want to utilize what we got as well as we can first.
|
It's wasn't knee-jerk at all I thought long and hard on how best to answer you. when in fact you answered your own question.
Quote:
Originally Posted by gsbe
To respond to my OP, I don't think it is possible for ID CS5.5 to export the margin classes for wrapped images...at least I can't get it to do it automagically. Fix this in the generated CSS file, then save that CSS file somewhere else and use it as a CSS template for future EPUB exports.
|
List of things ID won't do on export to epub.
Textwrap
Nested styles
endnote hyperlinking
Floating boxes
Preserve local formatting (It does. But badly IMO)
Keeping in mind, what looks good on one reader may in tern look like a dog's breakfast on another