Adjusting word spacing for justified text – kepub

[rtiangha]

Originally Posted by JSWolf

But that's not what I want. I don't want a larger space between lines. I want a way to fix the bug.

Rather than using the slider to adjust line height to work around the bug, you might be able to alter the font metrics using this methodology to ensure that all Ascender/Ascent values be set to be equal, Descender/Descent value be set to be equal, and LineGap be set to zero. It fixed the problem I had with Kurinto Text, so I decided to do the same with all my fonts and I haven't noticed the problem since.

It's easy to do in FontForge:

1. Go to the Font Information window, go to the General section, take the Ascent value and then go to the Metrics tab of the OS/2 section and input it into the Win Ascent, Typo Ascent, and HHead Ascent fields.
2. Do the same with the General section's Decent value with the Metrics tab's Win, Typo, and HHead Descent fields.
3. Finally, set the Metrics tab's Typo Line Gap and HHead Line Gap fields to 0.

Or if you have Python, you can install gftools and do the same with this command:

gftools fix-vertical-metrics -a ASCENT -d -DESCENT -l 0 FontName-Regular.ttf

Substituting the appropriate values for ASCENT, DESCENT, and Font Name.

For font families, use the Ascent and Descent values from the Regular font face with the bold, italic, and bolditalic versions to make sure everything stays consistent.

[MGlitch]

Originally Posted by rtiangha

Rather than using the slider to adjust line height to work around the bug, you might be able to alter the font metrics using this methodology to ensure that all Ascender/Ascent values be set to be equal, Descender/Descent value be set to be equal, and LineGap be set to zero. It fixed the problem I had with Kurinto Text, so I decided to do the same with all my fonts and I haven't noticed the problem since.

Honestly this I’ve tweaked Literata among others and at this point I have to have the font size and line spacing somewhat ridiculously small to trigger this issue. And honestly the settings get in the way of comfortably reading before the point that the issue pops up.

[JSWolf]

Originally Posted by rtiangha

Rather than using the slider to adjust line height to work around the bug, you might be able to alter the font metrics using this methodology to ensure that all Ascender/Ascent values be set to be equal, Descender/Descent value be set to be equal, and LineGap be set to zero. It fixed the problem I had with Kurinto Text, so I decided to do the same with all my fonts and I haven't noticed the problem since.

It's easy to do in FontForge:

1. Go to the Font Information window, go to the General section, take the Ascent value and then go to the Metrics tab of the OS/2 section and input it into the Win Ascent, Typo Ascent, and HHead Ascent fields.
2. Do the same with the General section's Decent value with the Metrics tab's Win, Typo, and HHead Descent fields.
3. Finally, set the Metrics tab's Typo Line Gap and HHead Line Gap fields to 0.

Or if you have Python, you can install gftools and do the same with this command:

gftools fix-vertical-metrics -a ASCENT -d -DESCENT -l 0 FontName-Regular.ttf

Substituting the appropriate values for ASCENT, DESCENT, and Font Name.

For font families, use the Ascent and Descent values from the Regular font face with the bold, italic, and bolditalic versions to make sure everything stays consistent.

I just tried this and it still had the problem. It's when you have the line-height small enough. I even tried some Kobo fonts and other fonts I have installed and they all showed the same thing.

[JSWolf]

Originally Posted by MGlitch

Honestly this I’ve tweaked Literata among others and at this point I have to have the font size and line spacing somewhat ridiculously small to trigger this issue. And honestly the settings get in the way of comfortably reading before the point that the issue pops up.

I like a small line height. And at my preferred line height for ChareInk, I do see this issue. I've even tried the proposed fix and still the same.

[MGlitch]

Originally Posted by JSWolf

I like a small line height. And at my preferred line height for ChareInk, I do see this issue. I've even tried the proposed fix and still the same.

Have you tried the my line 24 patch. It allows more refined small spacing.

[JSWolf]

Originally Posted by MGlitch

Have you tried the my line 24 patch. It allows more refined small spacing.

Yes, that is what I am using.

[Deobulakenyo]

Originally Posted by JSWolf

Here is what the code will look like. The ID will have different numbers. And obviously there will be closing spans.

<span class="koboSpan" id="kobo.44.1">

Find the paragraph with the problem. Then delete all kobospans in that paragraph except the first one and then copy the eBook back over the existing copy on your Kobo. It will be imported again and you can go to the same page and see if the problem still exists.

Not sure if I am doing it right but here is what happens when i use the editor and look at the concerned paragraph.

I uploaded again the screenshot for reference

[Deobulakenyo]

Originally Posted by Sirtel

I'm guessing that's the reason. Try without enabling it and see if the spaced-out letters are still there.

Disabling optimizelegibility (i enabled optimizespeed) removed the gap/space between some of the two-letter words.

[JSWolf]

Originally Posted by Deobulakenyo

Not sure if I am doing it right but here is what happens when i use the editor and look at the concerned paragraph.

I uploaded again the screenshot for reference

You have to edit the kepub.epub version. To get access to that, you have to plug in your Kobo and either copy it to your computer, edit it and copy it back or edit it direct on the Kobo. You are looking at the ePub.

And you have to re-enable legibility. to be able to test the change(s).

[Deobulakenyo]

Originally Posted by JSWolf

That's not an ellipse. That's just three periods. The other is definitely a problem.

Have you had a look at the code? If the paragraph in the first photo has multiple koboSpan in the paragraph, try removing all but the first one and try it again. It would be interesting to see if the problem gets fixed.

I did as you say. After deleting all kobo spans except the first one, "h e" is now fixed to "he" but after that paragraph, the rest of the chapter was gone (did not delete it). The next chapter immediately begins after the concerned paragraph.

[npr]

Just started testing: webkitTextRendering=geometricPrecision
in the reading section of the config file.

So far I haven't seen any obviously bad word spacing in kepub, so hoping this is a genuine improvement. Also ligatures are enabled with this setting.

[JSWolf]

Originally Posted by Deobulakenyo

I did as you say. After deleting all kobo spans except the first one, "h e" is now fixed to "he" but after that paragraph, the rest of the chapter was gone (did not delete it). The next chapter immediately begins after the concerned paragraph.

Try deleting the koboSpan on more time. In the Calibre editor do the following...

1. search for <div class="tx"><span class="koboSpan"
2. replace it with <div class="tx"><spam class="koboSpan"
3. Using Diap's Toolbag, delete all span with class koboSpan
4. search for <div class="tx"><spam class="koboSpan"
5. replace it with <div class="tx"><span class="koboSpan"

That is how I did it in my test. Except <div class="tx"> was <p>.

Also, could you post the paragraph with the rendering error as it is before you change the code? Thanks.

[Deobulakenyo]

Originally Posted by JSWolf

Try deleting the koboSpan on more time. In the Calibre editor do the following...

1. search for <div class="tx"><span class="koboSpan"
2. replace it with <div class="tx"><spam class="koboSpan"
3. Using Diap's Toolbag, delete all span with class koboSpan
4. search for <div class="tx"><spam class="koboSpan"
5. replace it with <div class="tx"><span class="koboSpan"

That is how I did it in my test. Except <div class="tx"> was <p>.

Also, could you post the paragraph with the rendering error as it is before you change the code? Thanks.

Okay. I will have a go at it again tomorrow during my lunch break. Although i do not know what Diap's Toolbag is, i am assuming it is part of Calibre's editor, and i will look for it there and play with it.

[JSWolf]

Originally Posted by Deobulakenyo

Okay. I will have a go at it again tomorrow during my lunch break. Although i do not know what Diap's Toolbag is, i am assuming it is part of Calibre's editor, and i will look for it there and play with it.

It's a plugin for Calibre that works with the editor. Here is the link to the plugin thread so you can read about it.

https://www.mobileread.com/forums/sh...d.php?t=251365

[Deobulakenyo]

Originally Posted by JSWolf

Try deleting the koboSpan on more time. In the Calibre editor do the following...

1. search for <div class="tx"><span class="koboSpan"
2. replace it with <div class="tx"><spam class="koboSpan"
3. Using Diap's Toolbag, delete all span with class koboSpan
4. search for <div class="tx"><spam class="koboSpan"
5. replace it with <div class="tx"><span class="koboSpan"

That is how I did it in my test. Except <div class="tx"> was <p>.

Also, could you post the paragraph with the rendering error as it is before you change the code? Thanks.

I followed your instruction and it solved the gap problem between some two-letter words that precede italics.

BTW, here is the "as is" part that is problematic. I encircled the "he" that is displayed as "h e" as posted screenshot shows previously.

Does this mean i have to fix a book by doing the same thing you taught me to do in "all and every chapter"?

and thanks for all your assistance.