![]() When I open this book with the Kobo Desktop it is rendered better. I would not suprise me if this kepub is rendered correctly with the Kobo Android or iPhone apps. And that seems the case with the current kepub renderer on the e-ink devices. Some of the more popular ways of inserting a blank line I've seen follow:ĭavidI also have no problem with choice and I do not care which rendering engine is used except when it looks broken or it does not behave like expected. Some of them work for Adobe's Reader Mobile (epub) but not for ACCESS Netfront (kepub). I've seen multiple ways of doing a blank line and some of them do not work on different devices. The "scene break" will depend on how the ebook publisher (not Kobo in most cases) created that piece of code. Given that my current reading stats show 29 books with 41 hours read since April 27th, the displayed chapter remaining times on a kepub - telling me it is going to take me 4 minutes to read the last 7 pages of a chapter, 14 minutes to read the next chapter and 14.5 hours finish reading the book are not even close to realistic numbers. It will not show you how to long it will take to finish the current chapter which in my opinion is a useless bit of information. The same reading stats screen will show the current book's progress and current chapter progress. So neither choice is good to me.As for the reading stats? You can get the number of books and hours read regardless of the type of book. OTOH, with kepub, I'm stuck with the title taking up space at the top. I'd really like to know how long I've been reading a book, how many books I've read this past years, etc. But what if I like having the reading stats? In fact, it's the one kobo feature I wish my current reader had. If the ebook is not DRMed, I find myself breaking out Sigil and having fun hacking and slashing the styles, corrected the incorrect line breaks that amost every ebook seems to have, etc. Then there are the ebooks where the paragraph before the blank line uses a css style with a larger bottom margin or the paragraph after the blank line used a larger top margin. Sigil uses this when you insert a blank line. ![]() is another which works quite well in most cases. Not something I would depend on across multiple devices but Most of the time it does not work but seems to be popular with many publishers. works quite well unless you are reading on an iDevice which seems to disbelieve in non-breaking spaces. Some of the more popular ways of inserting a blank line I've seen follow: How is this good? Improper scene break is a pet peeve of mine.The "scene break" will depend on how the ebook publisher (not Kobo in most cases) created that piece of code. But, from the first post, kepub looks broken where ePub displays correctly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |