Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
It was over a year ago that I pointed out in the post Keyboards: hardware vs. software how disconnected our team (which owns most of the keyboard layouts) and the hardware team (which owns most of the actual keyboard hardware) were.
And how impressive it was that we managed to be in sync so often, given that disconnect.
But it is possible I may live the rest of my life without being able to understand why almost every keyboard layout has a key which, when typed, will produce | (U+007c, a.k.a. VERTICAL LINE) yet printed upon the face of the key is ¦ (U+00a6, a.k.a. BROKEN BAR).
What's up with that?
It turns out that every single byte code page other 874 of the Windows code pages supports U+00a6, and every single Windows code page bar none (pardon the pun) supports U+007c.
And just about every font that has one has the other.
Even though in most cases (to get back to keyboards) almost every keyboard prints one on theface of a key but the matching layout has the other input.
So why this disconnect?
And more importantly, why does it persist?
And most important of all, why don't people complain? In either direction?
I suspect it is because no one really cares.
Or maybe is just that two guys can walk into a bar. Even if it looks like it is broken. Since it turns out they may still be serving drinks....
This post brought to you by "|" (U+007c, a.k.a. VERTICAL LINE)