View Single Post
Old 11-21-2018, 02:10 PM   #8
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,097
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by un_pogaz View Post
I understand that automatically converting all HTML entities to their Unicode character is more readable.
However, if we have written an HTML entity (and more specifically a Unicode Entity ) it is because we want it as it is.
So seeing them disappear automatically is a bad surprise.
This is especially troublesome for alternative space character ("Narrow No-Break Space" for example) and technical characters.

It would be nice to have an option to disable the automatic conversion of entities completely (or partially: only Unicode Entities are kept, the other ones are converted)
For me, having to ask the user to manually enter the exceptions (without any other alternative) is not a good feature.
Blame the DEVICE manufactures that decided to NOT support entities any longer. Calibre and Sigil went with the most bulletproof code for those that don't WANT TO LEARN the alternates.
theducks is offline   Reply With Quote