It’s on the RGB (picture!) as well, which is completely new silkscreen. Should have caught that?
Is wild to watch
Unless this is somehow intended, but how is this (mismatched font) intended?
Now, don’t get me wrong. I am … fine, with my purchase. Not really any complaints. Nothing is perfect, and I will happily take an “early adopter defect” (or an electronic “birth mark”), since it adds uniqueness. If this is traceable to a certain batch, it will be even cooler.
I was going to ask if it is possible to get a single replacement key. Now given these are scissor switches, it’s probably likely that I end up destroying the plastic scissor mechanism or the keycap; that’s fine. Sending a single scissor mechanism and a keycap should be still far cheaper (and less wasteful) than sending a full key cap.
Or even send 5 of them. Though it’s probably silkscreened after the keyboards are assembled, so I don’t know.
I certainly would entertain that idea. But what do I know.
It is always the way I was taught to write an uppercase “i”, with a top and bottom bar.
I continually have to think about wether the letter is an uppercase i (I) or a lowercase L (l), as seen how this font represents those letters.
In passwords, I continue to have to think, is this that stupid font style that confuses capital/lowercase L/i with l/I (lowercase L/capital i).
I didn’t notice my keyboard i until now, but thankfully the uppercase i has a top and bottom bar, as in Xavier_Jiangs’ pic in post#1.
Cheers
If framework truly wants to be unique, rather than having every key have the same font, it would be more interesting to have every key have a different font. Except two. So it could be inconsistently inconsistent.
