View Single Post
Old 01-21-2018, 02:59 AM   #7
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 35,393
Karma: 145435140
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by writingboy View Post
The majority of the pings come from one specific section of HTML, which contains several hundred ↺ characters meant to link readers back to the sections from which my endnotes originate. I've tried tweaking that, but no such luck.
One possibility that comes to mind is that epub3 does not support HTML named entities. You might want to try replacing ↺ with ↺ (double check that as it's not a character I make use of). Repeat for any other HTML enties such the the right and left quotes. I've been bitten by this a few times since my favourite   entity is not supported and & #160; (remove the space) just lacks the same human readability.

For epub3, I would suggest using Sigil instead of calibre's editor. At this time, it simply supports epub3 better than calibre's editor does.

Last edited by DNSB; 01-21-2018 at 03:14 AM.
DNSB is offline   Reply With Quote