KePub Output vs KoboTouchExtended

[DevilsTell]

Originally Posted by DNSB

Basically, RMSDK/epub handles typography better than the WebKit based renderer/kepub.

[rant mode]
Accurate page counts in a reflowable ebook?

To me, that is a joke.Even using page maps, you are looking at page counts for a specific physical edition. The only page counts that I've ever found useful was Adobe's synthetic page map algorithm since that gives the same page numbers for the same epub file on any size of device regardless of playing with line spacing, margins, font size, etc.

Page counts that vary with font size, margins, line spacing, line height, etc. are not transferable and so, to me, of no use.
[/rant mode]

Out of a perhaps morbid curiosity, is there a reason that you are modify the font size on your messages?

Can you adjust line spacing with ePub? I had some issues with that, and it's the main reason I switched to KePub.

Sorry if my earlier message was a bit confusing. I'm no expert when it comes to this stuff. To clarify, I'm not really concerned about transferring the exact page count from one medium to another. What I really like is the 'pages left in the chapter' feature, and knowing it corresponds 1:1 with page clicks on my sage, regardless of the font and line spacing. I find it a lot more useful than the 'time left in chapter' stat on Kindle, which I often find inaccurate.

Do you happen to know Amazon's method for determining the Kindle page count? I've noticed that some shorter books in my library can have longer page counts, and vice versa.

Lol the default font size is too small in my opinion. I'm just trying to make my messages more readable

Originally Posted by JSWolf

Also, there is the patch to reduce the space between words for KePub. You may have to play around with it to get it to a value you prefer with your chosen font. It does make a difference and KePub does look better. Not better then ePub with RMSDK but better then KePub would look otherwise.

Another advantage to ePub is that the Count Pages plugin does the page numbering for ePub but it cannot do the page numbering for KePub.

Could someone please help me understand what RMSDK is and how it can be incorporated into ePub to achieve a better appearance?

Thanks!

[jospalau]

Originally Posted by JSWolf

Also, there is the patch to reduce the space between words for KePub. You may have to play around with it to get it to a value you prefer with your chosen font. It does make a difference and KePub does look better. Not better then ePub with RMSDK but better then KePub would look otherwise.

Another advantage to ePub is that the Count Pages plugin does the page numbering for ePub but it cannot do the page numbering for KePub.

KOReader lets you change all these parameters patches hassle free. It also tracks statistics. What's the advantage of using the stock reader?

Sent from my 22081212UG using Tapatalk

[Sirtel]

Originally Posted by jospalau

KOReader lets you change all these parameters patches hassle free. It also tracks statistics. What's the advantage of using the stock reader?

Sent from my 22081212UG using Tapatalk

KOReader is very slow opening large multi-volume omnibuses, and I have many of those. Also I don't like the old-fashioned folder-based library structure it uses. I prefer the library structure based on metadata and tags, like the stock reader uses.

Add to that the fact that I edit the formatting of all my books to make them look consistent on any ereader or app I might wish to use, and KOReader has lost most of its advantages over the (patched) stock reader for me. It just doesn't add any real value for me personally (yes, I have tried it).

[Aleron Ives]

I guess it's also less stable than the stock reader on the Libra 2, for those who have that particular model.

[jospalau]

Originally Posted by Sirtel

KOReader is very slow opening large multi-volume omnibuses, and I have many of those. Also I don't like the old-fashioned folder-based library structure it uses. I prefer the library structure based on metadata and tags, like the stock reader uses.

Add to that the fact that I edit the formatting of all my books to make them look consistent on any ereader or app I might wish to use, and KOReader has lost most of its advantages over the (patched) stock reader for me. It just doesn't add any real value for me personally (yes, I have tried it).

I understand. That's sensible.

How do you use the customized page count you mentioned previously?


Sent from my 22081212UG using Tapatalk

[Sirtel]

Originally Posted by jospalau

I understand. That's sensible.

How do you used the customized page count you mentioned previously?


Sent from my 22081212UG using Tapatalk

There's no way to use it while reading; it's in the book details and gives me an approximate length of the book. As I prefer only the progress bar to be visible when I'm reading and not anything else, this doesn't bother me overmuch.

[JSWolf]

@DevilsTell can you please not make the text you type a larger size? Just use zoom in your web browser to make all the text larger for just yourself. Thanks.

[JSWolf]

While RMSDK/ADE page numbers are not perfect, they do give you an idea of how long the book is. There is no better page numbering for eBooks then that.

[Sirtel]

Originally Posted by JSWolf

While RMSDK/ADE page numbers are not perfect, they do give you an idea of how long the book is.

So does any other way you use. I've found characters per page to be a more consistent method.

[jospalau]

Originally Posted by JSWolf

While RMSDK/ADE page numbers are not perfect, they do give you an idea of how long the book is. There is no better page numbering for eBooks then that.

I agree with this, although page numbers in KOReader are recalculated dynamically depending of the font settings. I take KOReader page number as reference using a consistent configuration between books. All thanks to profiles

Sent from my 22081212UG using Tapatalk

[DNSB]

Originally Posted by DevilsTell

Can you adjust line spacing with ePub? I had some issues with that, and it's the main reason I switched to KePub.

You can adjust the line spacing on a epub but it does require that a fixed line height not be set in the stylesheet.

Originally Posted by DevilsTell

Lol the default font size is too small in my opinion. I'm just trying to make my messages more readable

Most of us have our systems configured to give us a comfortable reading size with the default. Increasing the size as you are doing makes it annoying to read your messages. If you find the font size too small, zoom in in your browser.

Originally Posted by DevilsTell

Could someone please help me understand what RMSDK is and how it can be incorporated into ePub to achieve a better appearance?

RMSDK is the Adobe renderer used by Kobo for .epub files (it also handles Adobe's DRM encrypted epubs). It is not something that is incorporated into a ePub.

[DevilsTell]

Originally Posted by DNSB

You can adjust the line spacing on a epub but it does require that a fixed line height not be set in the stylesheet.

Most of us have our systems configured to give us a comfortable reading size with the default. Increasing the size as you are doing makes it annoying to read your messages. If you find the font size too small, zoom in in your browser.

RMSDK is the Adobe renderer used by Kobo for .epub files (it also handles Adobe's DRM encrypted epubs). It is not something that is incorporated into a ePub.

Thanks! I'll definitely check out adjusting the fixed line height. Hopefully, it won't be too complicated to do.

Duly noted! I'll make sure to keep my text size standard going forward.

[Quoth]

I use Calibre conversion to remove ALL references in CSS with line-height and also white-space. Those are for websites, not reflowable ebooks.

[Sirtel]

Originally Posted by Quoth

I use Calibre conversion to remove ALL references in CSS with line-height and also white-space. Those are for websites, not reflowable ebooks.

Yes. I don't understand why publishers insist on defining line-height for body text in the css. Seems that most of them have never read a single ebook. Same as with an embedded body text font, nonstandard font size, right and/or left margins for body text and many other stupid, stupid things that are regularly inserted in the css even these days, after decades of reflowable ebooks and two decades of dedicated ereaders. Grr.
/rant over

[JSWolf]

Originally Posted by Sirtel

Yes. I don't understand why publishers insist on defining line-height for body text in the css. Seems that most of them have never read a single ebook. Same as with an embedded body text font, nonstandard font size, right and/or left margins for body text and many other stupid, stupid things that are regularly inserted in the css even these days, after decades of reflowable ebooks and two decades of dedicated ereaders. Grr.
/rant over

Because they have no clue what they are doing. They use pre-built templates and really bad software. A good example of really bad software is Velum.