Thread: Kobo Bug thread
View Single Post
Old 11-13-2019, 06:57 AM   #1158
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by JSWolf View Post
If you use font-family: monospace with ADE and every other version of RMSDK, you will get a monospace font. But Kobo is the only one using RMSDK where that doesn't work. So yes, it is a bug on Kobo's part.
Wrong. If you use "font-family: monospace" and supply an appropriate font, it will work. As it works, it is NOT a bug.

And for the record, this is like saying Windows has a bug because I specified to use "Some Stupid Font" in a book but did not supply the font so that the application could read the font from.
davidfor is offline   Reply With Quote