Thread: Kobo Bug thread
View Single Post
Old 11-14-2019, 09:44 PM   #1187
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
And for the record:

Exactly how many of you have reported this "major bug" to Kobo? If it is such a problem, I'm sure all of you have reported it and explained why it is important. If enough people report the problem, it will change.

And I have asked the question about monospace support. Basically, "not important", and not something they considered was needed. I also asked about the strange path used in the firmware which the patch @jackie_w fixes. That bit probably is a bug. Or at least it is inconsistent with other font paths.
davidfor is offline   Reply With Quote