Adjusting word spacing for justified text – kepub

[JSWolf]

Originally Posted by MGlitch

What does the epub renderer do better compared to the kepub renderer with those modifications? Actually asking, as I thought they basically brought everything to the kepub renderer that it was lacking or deficient in.

No funny spaces. Adjusting the spacing so it can be smaller. Line height can be smaller without seeing part of the top line of the next screen.

[JSWolf]

Originally Posted by ZodWallop

How do you easily do that?

The opening tag is easy enough to search and replace. But finding which </span>s are bold or italic vs. something else can be a headache.

I use the Calibre editor with Diap's Editing Toolbag (plugin) to convert the spans. Very useful plugin.

[Leddie]

I'm a little lost, what exactly does geometricPrecision do different from optimizelegibility?

Is it just a better way to do what optimizelegibility does?

[DNSB]

Originally Posted by Leddie

I'm a little lost, what exactly does geometricPrecision do different from optimizelegibility?

Is it just a better way to do what optimizelegibility does?

To quote from the Mozilla developer site:

optimizeSpeed
The browser emphasizes rendering speed over legibility and geometric precision when drawing text. It disables kerning and ligatures.

optimizeLegibility
The browser emphasizes legibility over rendering speed and geometric precision. This enables kerning and optional ligatures.

geometricPrecision
The browser emphasizes geometric precision over rendering speed and legibility. Certain aspects of fonts — such as kerning — don't scale linearly. So this value can make text using those fonts look good.

In SVG, when text is scaled up or down, browsers calculate the final size of the text (which is determined by the specified font size and the applied scale) and request a font of that computed size from the platform's font system. But if you request a font size of, say, 9 with a scale of 140%, the resulting font size of 12.6 doesn't explicitly exist in the font system, so the browser rounds the font size to 12 instead. This results in stair-step scaling of text.

But the geometricPrecision property — when fully supported by the rendering engine — lets you scale your text fluidly. For large scale factors, you might see less-than-beautiful text rendering, but the size is what you would expect—neither rounded up nor down to the nearest font size supported by Windows or Linux.

[jackie_w]

Originally Posted by davidfor

I have said I will look at @jackie_w's code for doing one span per paragraph when I have time. That should solve this and other similar issues. Coding something more specific is a waste of time if that is going to happen.

Just for clarity, my code creates one-span-per-node not one-span-per-paragraph. Although in a typical standard paragraph (no italics or other inline styling) they are the same thing.

[jackie_w]

Originally Posted by JSWolf

After reading your post, I did some quick tests and dictionary lookup works no problem.

Highlighting does not work properly.

Thanks for testing. So, only half as problematic as I remembered

[JSWolf]

Originally Posted by jackie_w

Just for clarity, my code creates one-span-per-node not one-span-per-paragraph. Although in a typical standard paragraph (no italics or other inline styling) they are the same thing.

Do the ID numbers have to be sequential? With my removing the extra koboSpan, I also made the IDs out of order.

[davidfor]

Originally Posted by jackie_w

Just for clarity, my code creates one-span-per-node not one-span-per-paragraph. Although in a typical standard paragraph (no italics or other inline styling) they are the same thing.

I was being lazy. I probably should have said "roughly" one span per paragraph. Per node is better but might have needed explanation.

Originally Posted by JSWolf

Do the ID numbers have to be sequential? With my removing the extra koboSpan, I also made the IDs out of order.

It won't matter. I am fairly sure the actual values of the ids are meaningless except as a way to ensure each span has a unique id. Generating a sequential number is just easier.

[JSWolf]

Originally Posted by davidfor

It won't matter. I am fairly sure the actual values of the ids are meaningless except as a way to ensure each span has a unique id. Generating a sequential number is just easier.

I'll have to test again and see what happens if I remove the IDs. Then test again doing what I did before but without the IDs.

[davidfor]

Originally Posted by JSWolf

I'll have to test again and see what happens if I remove the IDs. Then test again doing what I did before but without the IDs.

Read what I said. I said I did not think it mattered what the id looks like. But, the id is mandatory. It is used by the reader for the location. If you do not have the id, then it cannot get back to the correct location in the book. It will always reopen to the start of a chapter. And bookmarks/annotations will not work for the same reason.

[JSWolf]

Originally Posted by davidfor

Read what I said. I said I did not think it mattered what the id looks like. But, the id is mandatory. It is used by the reader for the location. If you do not have the id, then it cannot get back to the correct location in the book. It will always reopen to the start of a chapter. And bookmarks/annotations will not work for the same reason.

When I removed koboSpans inside of plain paragraphs, with no text formatting other then <p>, highlighting did not fully work. It only showed partial highlights.

[davidfor]

Originally Posted by JSWolf

I'll have to test again and see what happens if I remove the IDs. Then test again doing what I did before but without the IDs.

Originally Posted by JSWolf

When I removed koboSpans inside of plain paragraphs, with no text formatting other then <p>, highlighting did not fully work. It only showed partial highlights.

Firstly, I was responding to a statement that you were going to remove ids. Did you actually mean that you were planning to remove some spans? If that was what you were doing, it would be good to actually say it.

And that highlighting didn't work means that you made a mistake. You do not have a span with the appropriate class and an id that covers all parts of the text you are highlighting.

[JSWolf]

I've modified the patch for the word space in KePub to use a value of of -0.07 instead of -0.05. This gives even better word spacing as the word spacing is even smaller. It looks better to me.

[Deobulakenyo]

Originally Posted by JSWolf

I've modified the patch for the word space in KePub to use a value of of -0.07 instead of -0.05. This gives even better word spacing as the word spacing is even smaller. IT looks better to me.

can you post screenshots of the actual difference?

Edit: Nevermind, I will test for myself to see

[JSWolf]

Originally Posted by Deobulakenyo

can you post screenshots of the actual difference?

Edit: Nevermind, I will test for myself to see

Once you do the testing, please let us know what you think.