View Single Post
Old 06-21-2021, 11:43 PM   #3
pickyaxe
Addict
pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.pickyaxe ought to be getting tired of karma fortunes by now.
 
Posts: 289
Karma: 3762916
Join Date: Nov 2011
Device: none
Quote:
Originally Posted by NiLuJe View Post
Err, when, where?

(I'm mainly objecting to the wording here, I *know* we use a monospace font for stuff that ought to be monospace [e.g., pre blocks] ^^).
I... don't actually know. That's just the behavior I'm observing when I replace DroidSansMono or add another monospaced font to the same directory DroidSansMono.ttf is located at.

It's not difficult to set a new monospace font (by adding a new file into that directory and hoping KOReader selects it as "the" monospace font). However, matching the size to your currently-used non-monospaced font is a hassle. Also, once KOReader has loaded, the monospaced font is not user-changeable.
pickyaxe is offline   Reply With Quote