Since my previous post asking for help with this issue was flooded with downvotes, I’d like to explain more clearly what I mean when I talk about spacing problems and also share the solutions I’ve found.
I’ve attached screenshots showing the different justification settings. Each image indicates which type of justification I used and highlights where the problems occur. I’ve always used the same words as a reference, so it’s easier to see the differences in how they are rendered on screen.
- Justification OFF: This is the issue I was talking about. As you can see in the corresponding image, on the SAME line, the words have DIFFERENT spacing between them. When there is a punctuation mark, the words tend to be closer together;
- Justification Left: This one hardly even needs commenting on. In my opinion, this kind of alignment is simply unsuitable for a book;
- Justification FULL: Words are hyphenated and wrapped onto the next line, but the spacing issue is still there. Just look at the image.
Honestly, I find it absurd that proprietary software behaves like this and is unable to produce properly spaced text.
So how do you fix it? Apparently, it took people outside the project, working for free, to improve the software of a company that sells these devices.
Here are the two solutions I found:
- First solution: NickelTypeFix
After installing NickelTypeFix, the spacing is immediately rendered correctly, as you can see in the image. It also brings several other improvements, including faster chapter changes.
- Second solution: KOReader
This is honestly a game changer. KOReader is incredible in terms of what it can do. With all its plugins and customization options, you can really make the reader behave and look exactly the way you want. The learning curve is steeper, but once you understand how it works, there’s simply no comparison.
At this point, I have to wonder why developers who are actually paid to work on a project can’t achieve what other people are doing for free.
What surprised me even more was the reaction when I first mentioned this here. A whole crowd of fanboys jumped in to defend what is clearly a flaw in Nickel, Kobo’s stock reader, claiming that this behaviour is perfectly normal.
I hope these solutions can be useful to someone.