Thread: Kobo Bug thread
View Single Post
Old 11-14-2019, 09:29 PM   #1186
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
That's because Kobo botched it. monospace should work in RMDSK on Kobo Readers. It's a part of ADE which is what RMSDK is. So yes, it is a bug that monospace does not render a monospace font when it should.
When are you going to stop repeating this and actually answer my question? You are making claims and not backing them up.

How sure are you that Kobo broke this (which they didn't) and that the other users of the RMSDK didn't spend time fixing a mess that Adobe supplied them?

Please Jon, put up or shut up. You frequently make claims like this as fact. You never back them up.
davidfor is offline   Reply With Quote