View Single Post
Old 04-01-2022, 11:44 PM   #73
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: 47,213
Karma: 170056770
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by roland1 View Post
Anyone have a problem with this—using a utf8 character in a list?

I guess I'll have to declare a utf8 standard in my html headers, no doubt. I want to replace the image-based checkmark icons I am using in my ul lists and these 2714s will do fine.
While the epub standard does specify UTF-8 (or UTF-16) encoding, the issue I've seen is where the font being used does not support a glyph and the renderer does not substitute the glyph from another font. A tofu character instead of a checkmark might irritate some users.

The standard first line in an epub text file is:

Code:
<?xml version="1.0" encoding="utf-8"?>
I'm assuming that you are using either & # 10004; or & # x2714; for the character (MobileRead has issues with displaying special characters so I placed a couple of spaces inside the entities). Sigil will change those numeric entities to the character entity since epub3 by default only allows 5 numeric entities.

Last edited by DNSB; 04-01-2022 at 11:48 PM.
DNSB is offline   Reply With Quote