Quote:
Originally Posted by stumped
in this context "good quality" simply means " well written".
|
No it doesn't. Well written refers to the book. Good quality refers to the formatting. The only way to have good quality is with styles.
Quote:
|
The OP has had enough contradictions and headaches inflicted by posters here already and does not also need god quality [sic] "advice" on how to use Word
|
Your the one who said to start over with a good quality Word document. I was just defining what that means.
Quote:
|
I am saying < to All > stop telling the OP to acquire new skills and tools.
|
You did start this with suggesting going back to a good quality Word document.
Quote:
|
Do the writing, and editing in word. When you are happy with the final product, us calibre to convert word ( docx) into epub, automatically. Calibre will not introduce epub errors.
|
This is, given that you don't want the OP to have to learn new skills, If styles are not used in Word, then you can end up with a document that's a real mess and it's more difficult to clean the code in the ePub then it is to use styles.
Quote:
|
if you intend to sell the epub, then hire a professional, to work on it for you. For your own use or to give away, a calibre conversion is fine. No one needs to look under the boonet or admire the elegance of the code, it jsut needs to work.
|
You do need to look under the hood if it's not just for yourself. Messy code can cause problems. In another thread someone was having problems with recently created ePub from Project Gutenberg. I managed to get the code to validate with Calibre's validater and epubcheck but the ePub caused ADE to crash. It was a 100% unneeded CSS entry that once deleted fixed the crashing. The messier the code the more chance there is that it can cause a problem. You don't know what software will be used with this ePub so you want to to work in as many cases as possible.