Thread: Kobo Bug thread
View Single Post
Old 11-13-2019, 05:31 AM   #1157
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,203
Karma: 148951761
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 davidfor View Post
If you include a monospace font in the book and correctly identify it, then you will see monospaced text where ever it is used. And I believe it will render correctly. As Kobo does not include a monospace font in the firmware, any other attempt to use a monospace font will result in using the currently defined font. And that will render correctly.

So, exactly how has Kobo botched rendering of monospace fonts with the RMSDK?
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.
JSWolf is offline   Reply With Quote