View Single Post
Old 03-15-2021, 06:48 PM   #277
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,084
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by BeckyEbook View Post
in parenthesis (single arrow, double arrow)

E-readers:
Nook Simple Touch (OK, OK)
Kobo Touch (OK, BAD [none, the arrow disappears])
KOReader on Kobo Touch (OK, OK)
Kindle Paperwhite 3 (file converted to mobi/azw3 (OK, OK)

So the double arrow is OK in most cases. It is worth checking on other readers (Pocketbook, other Kobo models, Tolino, Onyx etc.)
On my Forma using Charis SIL, the double arrow showed up okay. Testing the Kobo supplied fonts, only AR UDJingxihei, Kobo Tsukushi Mincho and Kobo UD Kakugo supported the double arrow glyph. If I converted the epub3 to kepub, the double arrow worked on any font since the kepub renderer will look for a missing glyph. Other than Courier Dark, my sideloaded fonts all supported the double arrow glyph.

On a Tolino EPOS, the double arrow worked with the default font.

The "=>" pair would likely be the best for catering to the LCD.
DNSB is offline   Reply With Quote