View Single Post
Old 03-29-2016, 01:19 PM   #19
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,031
Karma: 147977995
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Ripplinger View Post
Kobo readers would display bold instead of italic when <em> was used in the past. I can't remember now if it was for just specific fonts or even if it still happens or was fixed by now. But that got me in the habit of using <i> and <b> just for the reason DiapDealer said... it works on everything, including the then buggy Kobo firmware. I also figured <i> and <b> are shorter (yes, I'm lazy, less typing is always good ), and as long they both did the same thing and both generally supported, I didn't see a reason to change to <em> and <strong>.
That would have to be sometime before the H2O was released. I've never had a problem with <em> with my H2O. I did have a problem with whatever version RMDSk was used on a 650 when the encoding of the files (not in the files, but the files themselves) was incorrect. I'd end up with mostly bolded text.
JSWolf is offline   Reply With Quote