Quote:
Originally Posted by sysKin
Was that the book with various <font> tags? Because if yes, it *was* kobo splitting words wrong.
As much as html doesn't specify how to split words, <font> is an inline html element and inline html elements are never a valid base on which to split. It *is* valid to have a portion of a word written in different font (imagine an emphasised letter) and boundaries of such font change are not sensible places for a newline.
In other words, while that book was silly, it was not invalid and there exists a perfectly logical way to render it, and what Kobo was doing was not it.
Unless you're referring to a different word split problem in which case I apologise for off-topic...
|
Strictly speaking since most epubs I've seen use a xhtml11 doctype which is not all that different from a XHTML 1.0 Strict declaration, the <font> tag is
not supported. You should use CSS styling to obtain the same effects instead.
HTML5 does not support <font> and in HTML 4.01, it is deprecated -- at least, that's what my HTML validator has to say.
Regards,
David