Kindle Line Spacing

[DNSB]

Originally Posted by Flaviocc

Tks guys, the problem was bad book formatting.

I applied the option in Calibre to fix the tables and everything is ok now.

Another book the problem was I forgot to erase the space between paragraphs.

@DNSB where it's possible to configure Widows and orphans?

Tks.

In the CSS, you would need to remove any existing widows/orphans settings and add widows; 1; and orphans: 1; to the body style.

[JSWolf]

Originally Posted by jhowell

I can’t tell whether you you are mentioning this as a good thing or a bad thing but I agree that one of the goals of Amazon’s Enhanced Typesetting as implemented in KFX format is to normalize things like line spacing to take it out of the hands of the publisher and give more control to the reader.

The reader has no control. The margins are too large and the line height is too large and this is at the smallest settings.

[jhowell]

Originally Posted by JSWolf

The reader has no control. The margins are too large and the line height is too large and this is at the smallest settings.

Too large for you. For me they are just about perfect. Space between lines and margins around the screen make the reading experience more enjoyable for me even if it means more page turns. Others prefer every mm of the screen to be loaded with text. That doesn’t work for me.

[JSWolf]

Originally Posted by jhowell

Too large for you. For me they are just about perfect. Space between lines and margins around the screen make the reading experience more enjoyable for me even if it means more page turns. Others prefer every mm of the screen to be loaded with text. That doesn’t work for me.

But as I say, there is no control. On a Kobo, you can have it how you like it and I can have it how I like it. But with a Kindle, it is as it is like it or not.

[nabsltd]

Originally Posted by JSWolf

The margins are too large and the line height is too large and this is at the smallest settings.

Minimum line height on a Kindle is 1.2. At 1.1, the tail of the uppercase Q in the font I use is almost touching the top of uppercase characters on the line below. That is much too tight. It's barely acceptable at a line height of 1.15. If you use one of the ugly "better for reading" fonts that has high x-height and short descenders, a line height of 1.1 might be OK.

Top and bottom margins on the Kindle are fine, as they are just space for things like page number, clock, etc, and every other eReader is similar. Left and right are a bit larger than I like, but are still far smaller than in printed books. You can also touch up the CSS with negative margins.

[Sirtel]

Originally Posted by nabsltd

Minimum line height on a Kindle is 1.2. At 1.1, the tail of the uppercase Q in the font I use is almost touching the top of uppercase characters on the line below. That is much too tight. It's barely acceptable at a line height of 1.15. If you use one of the ugly "better for reading" fonts that has high x-height and short descenders, a line height of 1.1 might be OK.

It's all subjective, of course. I prefer tight line-spacing to high descenders any time; you, vice versa. For that reason (and others, like custom font sizes) I could never use KFX on my Kindles. I have 33 lines per page on my 7'' Libra 2 and that's what feels optimal to me. I don't want any headers, footers, clock etc taking up space either; the progress bar is enough. On a Kobo, you can adjust the height of top and bottom margins with patching.

It's not totally impossible I'll buy a Kindle again in the future, but reading KFX is out of the question for me.

[JSWolf]

Originally Posted by Sirtel

It's all subjective, of course. I prefer tight line-spacing to high descenders any time; you, vice versa. For that reason (and others, like custom font sizes) I could never use KFX on my Kindles. I have 33 lines per page on my 7'' Libra 2 and that's what feels optimal to me. I don't want any headers, footers, clock etc taking up space either; the progress bar is enough. On a Kobo, you can adjust the height of top and bottom margins with patching.

It's not totally impossible I'll buy a Kindle again in the future, but reading KFX is out of the question for me.

I don't like fonts with that large a descender. I read with ChareInk6SP. On a Kindle reading in KF8, you get get a smaller line height. Also, because the font is not as wide as Bookerly, I also get more characters per line then i would using Bookerly.

One my Libra 2, I get 41 lines per page.

[nabsltd]

Originally Posted by JSWolf

I read with ChareInk6SP.

As I said: If you use one of the ugly "better for reading" fonts that has high x-height and short descenders, a line height of 1.1 might be OK.

Charis SIL is one of those fonts.

Also, because the font is not as wide as Bookerly

My preferred reading font is Adobe Garamond Premier Medium, and it takes about 87% of the width that ChareInk6SP does at the same font size.

EB Garamond and Cormorant Garamond from Google Fonts are both decent free alternatives. EB Garamond is a little bit darker than Adobe's at the same weight, while Cormorant is a little bit lighter. If you are used to reading with something as dense and thickly stroked as ChareInk6SP, both will seem quite light, because of the delicacy of the Garamond style font. Both are about 2-3% wider than Adobe's, so still quite narrow.

[Sirtel]

Originally Posted by nabsltd

As I said: If you use one of the ugly "better for reading" fonts that has high x-height and short descenders, a line height of 1.1 might be OK.

Charis SIL is one of those fonts.


My preferred reading font is Adobe Garamond Premier Medium, and it takes about 87% of the width that ChareInk6SP does at the same font size.

EB Garamond and Cormorant Garamond from Google Fonts are both decent free alternatives. EB Garamond is a little bit darker than Adobe's at the same weight, while Cormorant is a little bit lighter. If you are used to reading with something as dense and thickly stroked as ChareInk6SP, both will seem quite light, because of the delicacy of the Garamond style font. Both are about 2-3% wider than Adobe's, so still quite narrow.

I've tried Garamond, but it doesn't suit me. Too thin and the line spacing is too large. I prefer thicker fonts with tighter line spacing. To each their own.

[JSWolf]

Originally Posted by nabsltd

As I said: If you use one of the ugly "better for reading" fonts that has high x-height and short descenders, a line height of 1.1 might be OK.

Charis SIL is one of those fonts.


My preferred reading font is Adobe Garamond Premier Medium, and it takes about 87% of the width that ChareInk6SP does at the same font size.

EB Garamond and Cormorant Garamond from Google Fonts are both decent free alternatives. EB Garamond is a little bit darker than Adobe's at the same weight, while Cormorant is a little bit lighter. If you are used to reading with something as dense and thickly stroked as ChareInk6SP, both will seem quite light, because of the delicacy of the Garamond style font. Both are about 2-3% wider than Adobe's, so still quite narrow.

If you read KFX, you cannot change the line height. It's forced on you. CharInk6SP allows a smaller line height when used with KF8. Also, the space is smaller so you get more characters per line. ChareInk6SP is based on Charis SIL.

I do need to update ChareInk6SP and CharInk6 to the new version of of Charis SIL.

[jospalau]

Originally Posted by JSWolf

If you read KFX, you cannot change the line height. It's forced on you. CharInk6SP allows a smaller line height when used with KF8. Also, the space is smaller so you get more characters per line. ChareInk6SP is based on Charis SIL.



I do need to update ChareInk6SP and CharInk6 to the new version of of Charis SIL.

I made a few tests with real numbers in KOReader and I can say that ChareInk fits more words per page than other fonts.

Same profile, same configuration:
318wpp Bookerly
320wpp Literata
338wpp Capita
340wpp Georgia
344wpp ChareInk

Sent from my 22081212UG using Tapatalk

[Flaviocc]

Originally Posted by DNSB

In the CSS, you would need to remove any existing widows/orphans settings and add widows; 1; and orphans: 1; to the body style.

Thank you.

I can do that in Calibre or I have to edit the book code (calibre editor or other).

Tks.

[DNSB]

Originally Posted by Flaviocc

Thank you.

I can do that in Calibre or I have to edit the book code (calibre editor or other).

Tks.

For me, the easist way to do it is using either the calibre ebook-editor or Sigil.

Most times, there is only one or two widows/orphans references in the stylesheet(s) but there are some where widows/orphans are in almost every bleeping style.

[Flaviocc]

Originally Posted by DNSB

For me, the easist way to do it is using either the calibre ebook-editor or Sigil.

Most times, there is only one or two widows/orphans references in the stylesheet(s) but there are some where widows/orphans are in almost every bleeping style.

Thank you so much !

[JSWolf]

Originally Posted by jospalau

I made a few tests with real numbers in KOReader and I can say that ChareInk fits more words per page than other fonts.

Same profile, same configuration:
318wpp Bookerly
320wpp Literata
338wpp Capita
340wpp Georgia
344wpp ChareInk

Sent from my 22081212UG using Tapatalk

Try ChareInk6SP and you'll get even more words per page then you do now.