View Single Post
Old 11-26-2018, 08:03 AM   #64
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,735
Karma: 6990705
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by DNSB View Post
Again there is no need for that change. The named entity or the two numeric entities for a non-breaking space are treated the same by the renderer. Given that a kepub is rendered by an epub3 renderer on a Kobo ereader, using the named entity for a non-breaking space is not a good idea.
What you are saying is correct, but does not apply to this situation. The epub in question was invalid, and the spaces weren't correct. Kepubify attempts to fix broken epubs, and that made the spaces appear, so the real goal here is to remove them so the epub renders as it did before it was fixed.

Also, note that in the epub in question, the spaces were not originally encoded at all.
geek1011 is offline   Reply With Quote