OK, I've got a question about this change:
Quote:
|
- Span adding has been refactored and improved to better match Kobo. This means that the numbering of spans may be different if you reconvert a book.
|
Back in 2016,
jackie_w discovered that the reason why optimizeLegibility when enabled (either by patch or ebook css modification) produces weird spacing in justified text is because of span fragmentation; basically, it appears that the Kobo algorithm is aggressive and sometimes breaks up sentences into multiple spans when one span for the whole thing would probably be enough and posted some screenshots highlighting the difference (the one with less span fragmentation looks better).
If kepubify 3.0 better mimics Kobo's way of doing things, will that make the span fragmentation problem better or worse (I don't know how kepubify 2.0 did it instead)? Is there a way for a future version of kepubify to do a better job in reducing span fragmentation even if it means not following Kobo's conventions in applying spans during conversion (maybe by following
jackie_w's hacked KTE algorithm)?