Thread: Kobo Bug thread
View Single Post
Old 11-12-2019, 11:54 PM   #1156
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
It is a bug because monospace and the rendering of a monospace font is part of RMSDK. Kobo botched it and hasn't bothered to fix it.
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?
davidfor is offline   Reply With Quote