View Single Post
Old 02-16-2014, 02:49 AM   #10
arspr
Dead account. Bye
arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.
 
Posts: 587
Karma: 668244
Join Date: Mar 2011
Device: none
Quote:
Originally Posted by Nick Payne View Post
Well, I switched to the extended driver and reloaded a couple of books where I had had this problem. Loading them as kepubs does fix the orphaned end of chapter problem, but I then see a couple of other bugs which weren't manifested when the books were epubs:

1. Hyphenation at line ends is now breaking words at the wrong place. For example, I'm staring at the word "everywhere" hyphenated as "everyw-here".

2. If the book is formatted to use em dashes between words without a space either side of the em dash, the reader is now sometimes inserting spaces each side of the em dash as part of justifying lines. That didn't happen when they were epubs.
Well, you've just discovered that neither renderer (RMSDK from Adobe for epubs, or Kobo ACCESS for kepubs) is perfect.

The long paragraph bug (and others like this one I reported in my old Sony PRS-650 and which is also present in my Kobo AuraHD) is present across every brand...

But ACCESS isn't error free either. You've gotten a known issue about extra spacing around some punctuation marks and their partner words when justifying I posted in the bug thread. (Some discussion starts here about it).

And there are other issues. I give you some examples:
  • Some CSS properties like widows and orphans are ignored in kepubs. Link here.
  • Fake freezing at kepub opening. Link here.
  • Cross-effects between ACCESS "real" pages per chapter numbering and books with chapters in the same html file. Link here.
  • Strange criteria about cover scaling when this cover is not correctly set in HTML. Link here.

Some of them possibly happen just because kepub specification is not known. So, although it really seems logical expecting it being a step forward from epubs, maybe some things aren't permitted anymore and they raise "bugs".

About the hyphenation, and just to be sure. Hyphenation in ACCESS is disabled by default. You have enabled it through the CSS trick, haven't you? In any case, it really seems the trouble is not in the engine but in the hyphenation dictionary... (Yes dictionaries in Kobo are not really really good, because of that there are some hacks about substituting them in these forums).
arspr is offline   Reply With Quote