Quote:
Originally Posted by DNSB
If you simply rename an ebub to .kepub.epub, it will use the ACCESS renderer and you can highlight, etc. Book progress will be remembered ...
|
The bold bits are not my experience. I don't want to argue, we'll have to agree to differ.
Quote:
Originally Posted by DNSB
That's more a difference between the two renderers. RMSDK seems to be more consistent in it's handling of justification especially when you have ligatures enabled. If you send a kepubified epub as an epub or send an epub simply renamed to .kepub.epub, you will notice the differences. This happens with either a kepubified epub or a non-DRMed kepub downloaded to your computer using the Kobo desktop app or copied from your ereader.
|
Here is probably not the place to discuss it but all I can say is that extensive experiments with the koboSpan-adding algorithm (and a few other bizarre tweaks) tells me that full justified kepubs with ligatures can be made to look much smoother than Kobo's default algorithm allows. Possibly still not quite as good as epubs in Adobe, but perfectly acceptable (to me, that is).