[Jellby]

Originally Posted by arspr

First of all. Do not convert epubs into kepubs by simply renaming them. Some other modifications should be made (IIRC a lot of <span>s are inserted in order to make annotations work fine).

OK, I was not really testing kepub vs. epub, but the Kobo renderer vs. the Adobe one. I create most of the epubs I read from scratch, and I want control on the code, I don't want tons of meaningless <span>s, thank you, I will stay with the "pure" epub format.

Secondly. GUI settings are "usually" applied over the book's CSS in both formats. Unless I'm fully wrong there's no difference in the behaviour of both renderers.

This was only a guess. But what I mean is that when the user selects "justify", the reader could apply it (on top of the book's CSS) in different ways. A possible way is adding an implicit "body { text-align: justify }" rule. Another way is a "* { text-align; justify !important }" rule, and yet another is ".normal-text { text-align; justify }". The first would be my preferred one, the second overrides some alignment which is not meant to be overriden, the third requires the class "normal-text" to be used in the code. I don't know which are the chosen ones in the different renderers, but it seems to me they are different, and I'm used to work with ADE's one.

Third. Text alignment should perfectly work in kepubs. I've never found one issue about it.

If/when I test again, I'll give a more detailed report on what I don't like.

If you are interested, could you try this test?