Quote:
Originally Posted by McManly
I suspect the problem is that Word 2003 does some awfully kludgey HTML
|
It most definitely does. You can get rid of some or perhaps even most of it by saving your file as "
simplified HTML" in Word, but some manual fixing will likely still be needed to make the code 100% valid.
Also, there's a difference between 100%
valid and
efficient code. Even 100% valid code may be structurally redundant. It will be tough to avoid that whenever using a WYSIWYG editor, and
especially Word, to produce EPUB files. From among WYSIWYG editors, I'd still prefer Composer, part of SeaMonkey's suite, over Word.
To me,
simplicity rules, and I prefer to hand-code my EPUB files in a plain-text editor. I keep my code as
slim as humanly possible; whatever can be
excluded from the code, is thrown away. Only meaningful, efficient, and minimalistic CSS, corresponding to Word styles, is allowed to remain.
Quote:
Originally Posted by McManly
I have seen nowhere, in any reader, where the user can load fonts.
|
Oh, absolutely, every decent EPUB e-reader gives you that option.
That's the power and beauty of EPUB as opposed to PDF. Many e-readers come preloaded with a handful, or even a couple of dozen of nice fonts (both serif and non-serif). Moon+ Reader Pro also gives the user the extra option to add any
custom font to the software. Your e-books should be formatted so that they display properly
regardless of what font the EPUB software user may prefer -- as long as it's a fully Unicode-enabled font, and your file is properly encoded in UTF-8.