View Single Post
Old 12-18-2012, 01:55 AM   #14
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,204
Karma: 169936284
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by 0x55 View Post
Have two Glos here, one is 2.1.5, one is 2.3.1. Using Kobo Nickel, the same ePub is rendering italics on 2.1.5 and bold on 2.3.1.

The relevant CSS is "font-style: italic" and renders as expected in other readers.

- - - - -

Interesting update: Checking with Kobo Nickel, the HTML tags "i" and "em" both render bold as well.
When I updated to 2.3.1, I did my usual remove uSD card, factory reset, upgrade, restore font and Adobe activation files, quick testing, insert SD card and practice patience for a Glo and a Touch.

Finally got an attack of the brights and removed a couple of side-loaded fonts which duplicated some of the built-in fonts with changed characteristics. After that, the Touch had the usual issues with Avenir plus issues with Gill Sans. The Glo has issues with italic showing as bold for Avenir, Gill Sans and Kobo Nickel.

Oddly, a check of the MD5 checksums on the Gill Sans and Kobo Nickel files shows that the contents do not seem to have changed since the Glo 2.1.4 release and the file names have not changed.

Regards,
David
DNSB is offline   Reply With Quote