Adjusting word spacing for justified text – kepub

[ZodWallop]

Originally Posted by npr

Just started testing: webkitTextRendering=geometricPrecision
in the reading section of the config file... Also ligatures are enabled with this setting.

Given that ligatures are enabled, I just switched over as well. I don't really know what changes to expect, but I'll report back if I see anything obviously crazy.

[Deobulakenyo]

Originally Posted by ZodWallop

Given that ligatures are enabled, I just switched over as well. I don't really know what changes to expect, but I'll report back if I see anything obviously crazy.

This config also removed my problem a few posts back.

[JSWolf]

Originally Posted by Deobulakenyo

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.

I would hope not. But I suggest reporting this in the KoboTouchExtended plugin thread at...

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

[icallaci]

Does the capitalization matter for webkitTextRendering in .kobo/Kobo/Kobo eReader.conf? Some posts say webkitTextRendering=geometricprecision, while others say webkitTextRendering=geometricPrecision.

[ZodWallop]

Originally Posted by icallaci

Does the capitalization matter for webkitTextRendering in .kobo/Kobo/Kobo eReader.conf? Some posts say webkitTextRendering=geometricprecision, while others say webkitTextRendering=geometricPrecision.

I don't know. I'm using:

webkitTextRendering=geometricPrecision

It works.

Let me say that it could very well be confirmation bias, but word/letter spacing seems to be better with it.

I've only read a single 29 screen chapter last night. But I didn't see a single instance of widely spaced words or weirdly spaced letters within in a single word.

We will of course need a lot more than my 20 minute reading session.

[davidfor]

Originally Posted by JSWolf

I would hope not. But I suggest reporting this in the KoboTouchExtended plugin thread at...

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

Why? It is not a bug in the driver. Unless you can prove that Kobo does this in a different way.

[JSWolf]

Originally Posted by davidfor

Why? It is not a bug in the driver. Unless you can prove that Kobo does this in a different way.

When the code is edited to be just one span in the problematic paragraph, the problem goes away. Just because Kobo does it doesn't mean it's not incorrect.

Obviously it doesn't work as we have proof of it and we also have proof that it works when it's just one koboSpan.

[JSWolf]

I'm now trying webkitTextRendering=geometricPrecision and it seems OK so far.

[davidfor]

Originally Posted by JSWolf

When the code is edited to be just one span in the problematic paragraph, the problem goes away. Just because Kobo does it doesn't mean it's not incorrect.

Obviously it doesn't work as we have proof of it and we also have proof that it works when it's just one koboSpan.

As I said, it isn't a bug in the driver. The driver is supposed to produce code that is the same as what Kobo produces in purchased books. If you can demonstrate that the code produced by the driver is does not match what Kobo produces, that is a different matter.

[JSWolf]

Originally Posted by davidfor

As I said, it isn't a bug in the driver. The driver is supposed to produce code that is the same as what Kobo produces in purchased books. If you can demonstrate that the code produced by the driver is does not match what Kobo produces, that is a different matter.

It's most likely a bug in the renderer. But if it works to render the text correctly with just one koboSpan, why not give it a go?

[MGlitch]

Originally Posted by JSWolf

It's most likely a bug in the renderer. But if it works to render the text correctly with just one koboSpan, why not give it a go?

Because the goal of the plugin was to match what Kobo produced. Which has been mentioned numerous times in this thread and others.

[JSWolf]

Originally Posted by MGlitch

Because the goal of the plugin was to match what Kobo produced. Which has been mentioned numerous times in this thread and others.

But if the way Kobo is doing it doesn't work but doing it differently does work, why not change how it's being done?

We already saw that doing it Kobo's way didn't work but doing it with one koboSpan per paragraph did work. Can anyone deny that's what happened?

[npr]

Originally Posted by JSWolf

I'm now trying webkitTextRendering=geometricPrecision and it seems OK so far.

Yes it's ok'ish, but word spacing is still not as good as epub's

[JSWolf]

Originally Posted by npr

Yes it's ok'ish, but word spacing is still not as good as epub's

The word spacing never will be unless it's changed so the spacing can be smaller. But with the new patch to reduce the space between words, it's much better then it was. I may try making it even smaller and see how it looks.

[Sirtel]

Originally Posted by JSWolf

The word spacing never will be unless it's changed so the spacing can be smaller. But with the new patch to reduce the space between words, it's much better then it was. I may try making it even smaller and see how it looks.

I made it smaller than default on both my Sage and Libra (-0.06em and -0.07em respectively). But then I don't hyphenate and kerning/ligatures are disabled.