View Single Post
Old 08-13-2018, 10:24 PM   #32
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
* Yeah, a scaled down version of the same glyphs would do just fine for the lowercase stuff .

* See the attached snapshot . I get the idea, but (some of) the digits are a bit all over the place (mostly 1, 2 & 3).

I'm considering the lack of padding a feature and not a bug ^^. Might be worth experimenting with a tiny bit of padding for the lowercase stuff, though? But I don't really have a strong opinion on that one .

* Yeah, there's a lot of really tiny BDF/PCF fonts (f.g., creep is 4xsomething, IIRC). Unfortunately, I can only use stuff with a *width* that matches the width of a C data type in bits (i.e., 8/16/32/64). If there's one column of difference one way or the other, than can usually be fudged w/ gbdfed, but even then, turns out that severely limits our possibilities .

(Plus, in our case, 8x8 is already mind-boggingly tiny on a >250dpi screen ;p)
Attached Thumbnails
Click image for larger version

Name:	block.png
Views:	496
Size:	4.9 KB
ID:	165563  

Last edited by NiLuJe; 08-13-2018 at 10:36 PM.
NiLuJe is offline   Reply With Quote