View Single Post
Old 01-15-2013, 09:52 PM   #7
sysKin
Connoisseur
sysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the endsysKin knows the complete value of PI to the end
 
sysKin's Avatar
 
Posts: 56
Karma: 31830
Join Date: Oct 2012
Location: Australia
Device: Aura HD, after a train ate my Glo
Quote:
Originally Posted by meeera View Post
Your issue with the Coben book was not a "flaw" in the reader, and it wasn't splitting the words "wrong". When you feed a reader a completely broken book, it's anyone's guess as to how it's going to render.
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...
sysKin is offline   Reply With Quote