Firmware 4.34.20097

[NiLuJe]

@ZodWallop: IIRC, the ePub spec thingy requires you to identify the source of the page numbers (e.g., via ISBN-13).

(I may be entirely dreaming that up, because why the hell would the ePub specs start making sense? ).

EDIT: https://www.w3.org/publishing/epub3/...c-nav-pagelist

So, yup, the ePub specs continue being mind-boggling.

[Aleron Ives]

Originally Posted by Uncle Robin

Which print edition?

Originally Posted by ZodWallop

Then what version is the ebook to correspond to?

A reasonable approach would be to use the most recent print edition available at the time the e-book was released. If the print edition has the same cover art as the e-book, then that's close enough for me. :P

[Sirtel]

Originally Posted by Aleron Ives

A reasonable approach would be to use the most recent print edition available at the time the e-book was released. If the print edition has the same cover art as the e-book, then that's close enough for me. :P

What would be the point of that? I do use the count pages plugin for Calibre to estimate an approximate length of my books. The plugin uses a customized value of a certain number of words per page. So all my ebooks are estimated on exactly the same basis. The page count of a printed book would be of no use to me in this, as the result can vary wildly between different editions.

Of course I cannot transfer this page count to my Kobo (or only as a part of the book details), but it's enough for me to know how long a book is. The page count based on a print edition would be much more arbitrary, as there's no telling whether the corresponding print edition is hardcover or paperback or how large a print it uses. I'd have to look all this up to decide. Nope, not my cup of tea at all.

[JSWolf]

Originally Posted by Sirtel

Well, I personally couldn't care less about kerning or ligatures. Rakuten Serif is a pretty font and I liked it, but not so much that I'd use it regularly instead of LexiaDama. Kerning... ligatures... yawn. In fact, I've disabled them on my Sage altogether, because they mess up word spacing. (On the Libra I usually read epubs).

I get that kerning et al are important to many people. Just not to everyone.

I don't get how anyone can not like kerning. It looks better with kerning. As for ligatures, I figure most would not notice if they didn't happen. I probably would not notice.

Kerning does not mess up word spacing. I've read with kerning in KOReader, RMSDK, and Access (KePub) and none of them has word spacing messed up. What is it you are using to read with that has Kerning mess up word spacing? Can you please show a screen grab of messed up word spacing with kerning?

[Sirtel]

Originally Posted by JSWolf

Kerning does not mess up word spacing. I've read with kerning in KOReader, RMSDK, and Access (KePub) and none of them has word spacing messed up. What is it you are using to read with that has Kerning mess up word spacing? Can you please show a screen grab of messed up word spacing with kerning?

I disable hyphenation, that's why kerning messes up word spacing in the books I read. You, on the other hand, use hyphenation rather heavily, from what I've read here.

[JSWolf]

Originally Posted by Sirtel

No, neither of those are necessary. You edit the configuration file of your Kobo (Kobo eReader.conf), the Reading section. Adding the line webkitTextRendering=optimizelegibility turns them on, webkitTextRendering=optimizespeed turns them off.

That will not turn off kerning for RMSDK (ePub).

[Sirtel]

Originally Posted by JSWolf

That will not turn off kerning for RMSDK (ePub).

No, but it's not necessary there. Only kepubs have problems with word spacing, not RMSDK.

[ZodWallop]

Originally Posted by Aleron Ives

A reasonable approach would be to use the most recent print edition available at the time the e-book was released. If the print edition has the same cover art as the e-book, then that's close enough for me. :P

Well, to quote myself:

Originally Posted by ZodWallop

What happens when the paperback (which long term will be the much more popular physical version) comes out. Do they recalculate the page numbers?

[JSWolf]

Originally Posted by Sirtel

Yes, that's true. But word spacing is not an issue with epubs, only with kepubs.

The patch to adjust word spacing with KePub fixes this so it's not an issue.

[Sirtel]

Originally Posted by JSWolf

The patch to adjust word spacing with KePub fixes this so it's not an issue.

Yes, it can still be. The patch impoves it, it doesn't fix it.

[JSWolf]

Originally Posted by Aleron Ives

Do you have an opinion on the text quality between the two? I was reading the Standard E-Books website, and it claims that the public domain e-books there will look significantly better on Kobo devices if you use KEPUB compared to EPUB, because the ADE renderer is bad.

It's because StandardEbooks code is bad. They use overly complicated CSS code and a lot of their eBooks don't work well with RMSDK because of what RSMSDK perceives are errors. So don't tske what they say as the truth. They spin it because of their poor code. And they lie as well.

Compatible ePub is not compatible enough with RMSDK.
Also, Advanced ePub is worthless as there's no need for it. Have you ever seen a public domain book that needs An advanced format that uses the latest technology not yet fully supported by most ereaders? Of course not, because there are none.

If I ever downloaded any of their eBooks, I would have to mostly redo them because their CSS mostly needs to be scrapped.

I've been reading most of my books as EPUB with one KEPUB I bought from Kobo, and I didn't notice any difference between the two formats, other than the page renumbering and reading statistics options that KEPUB offers. I'm not entirely sure what supposed deficiency exists in the ADE renderer, as it seems fine to me.

There is nothing wrong with reading ePub. It's best to read with KePub if the eBook has images that you might want to zoom, lots of footnotes, or ePub 3 CSS code that does not work with ePub that you want to work,

[JSWolf]

Originally Posted by rashkae

The Epub renderer is just slow... there's a slight hesitance in turning pages. But the biggest difference is in books that that have graphical content. Not only is the Epub renderer much slower with those, but the quality of dithering, (to change colour into B&W gradients,) is *much* worse on epub. Kepub can also benefit from Image zoom. Kepubs also have better support for footnote links, that allows the footnote to be displayed in a pop-up.. (Conversely, in Epub, it can be hard to even press the link to the footnote.)

ePub (RMSDK) on Kobo used to be slower. But that's been sped up so it's not too slow. Dithering is not much worse with ePub. As to the speed of displaying images, I've not compared them. But given how ePub is not slow to display the cover and title page, I'd say it's not too slow to display images.

Kepub also has better support for Epub3 features,, including the Epub3 standard for ToC.. (which the epub renderer ignores,, making it unable to handle epub3 files unless those files are generated with backwards epub2 support.)[/quote]

Yes, KePub has better support for ePub 3 features. But why make an ePub 3 without an NCX unless it's heavily reliant on ePub 3 that it won't work well enough with an ePub 2 only renderer.

[Aleron Ives]

Originally Posted by Sirtel

What would be the point of that?

The only purpose I can think of is to help people who are familiar with reading paper books to estimate how long the chapters are via the number of pages in them. Since the library EPUBs I've read have had page numbers, I (erroneously) assumed this is what the page numbers represented. If the EPUB page numbers are in fact not based on a paper book, then I guess they are based on some arbitary metric of how many words "should" fit on a single page.

[MGlitch]

Originally Posted by Aleron Ives

If the EPUB page numbers are in fact not based on a paper book, then I guess they are based on some arbitary metric of how many words "should" fit on a single page.

Adobe, which is probably what those librariy books were using, is worse than words per page. It’s bytes. And the developer of it, or one of them anyway, has said it was an arbitrary number of bytes that they basically pulled out of thin air.

[Sirtel]

Originally Posted by Aleron Ives

The only purpose I can think of is to help people who are familiar with reading paper books to estimate how long the chapters are via the number of pages in them. Since the library EPUBs I've read have had page numbers, I (erroneously) assumed this is what the page numbers represented. If the EPUB page numbers are in fact not based on a paper book, then I guess they are based on some arbitary metric of how many words "should" fit on a single page.

How is that more arbitrary than the page numbers based on a paper edition? If anything, it's less so, as the page numbers of various paper editions vary wildly. You must know exactly which edition to estimate the length. The difference between a hardcover and a mass market paperback can be a couple of hundred pages, if not more.