Thread: Kobo Bug thread
View Single Post
Old 11-14-2019, 06:28 AM   #1175
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
Here's a question I hope someone can answer. RMSDK comes with monospace. Why did Kobo break it?
I need you to define two things:

What does "RMSDK comes with monospace" mean? Does it mean "Includes a monospace font". Or "renders things marked as monospace"? Or something else.

How do you think that Kobo broke this? I mean, apart from not actually including a monospace font in the firmware, how is it actually broken?

When you answer, please be specific and details. Or point to actual examples of the problem (beyond no monospace font being supplied, as we all know that).
davidfor is offline   Reply With Quote