From a visual perspective I miss some of those more esoteric symbols, but the current Apple (US) keyboard gets it right. Symbols with text labels for modifiers and clear pictographs for the function keys (though the F3/Mission Control icon is a bit unclear until you click i and the behavior of F5/mic seems unhelpful). I just remember a few too many family tech support issues trying to help a struggling relative understand that command and 'open apple' are the same thing.
I'm wondering where those Canadian keyboards are used. I live in Canada, have seen plenty of multilingual keyboards, and have seen those symbols perhaps once. Even so I can't be sure it was on a keyboard. I just recognized one of the symbols.
Aaaah, he's got carriage return and enter mixed up. The whole reason for the symbol being an arrow returning to the beginning of the line, is because it's the return key. I love the Canadian enter symbol, an arrow pointing into a box.
No amount of drooling over Apple keyboards will make me forget that Apple's designers didn't add keys for basic functions such as Copy and Paste, Undo and Redo.
(Yes, they could have just replaced the "regular" function keys with copy/paste keys, but I feel like that would have gone over about as well as the various times they've, uh, tried to replace the function keys)
> You turned it sideways. Using a colon, a dash, and a parenthesis character in series, you could make a sideways smile or frown. It looked like this: [happy-face] or [sad-face]
The symbols are from a weird ISO/IEC standard (9995-7 ?) that never really caught on except in a few places. I have seen the lock-key symbols more often on lock light panels than on keycaps.
Many European layouts do have more symbols outside ASCII. For example German has ° (degree) and ß (ess-tset) and § (paragraph).
German PC keyboards also tend to have µ on the M key, but it is available with the right Alt key.
Macintosh keyboard layouts tend to have many symbols on Option-combinations but they are not always printed.
ASCII is a 7-bit code, so there are only so many symbols one can add. Prior to ASCII, you had codes that used as few as 5 bits. Early C had the option to use digraphs to represent various forms of parenthesis, simply because symbols like {} and [] were not universal.
(Strictly speaking, people did continue adding symbols. We used to talk about code pages: when the MSB was 0, the other 7 bits were ASCII. When the MSB was 1, the other 7 bits were a user selected code pade.)
ASCII is 7-bit and fully filled out. Every other extended character system prior to Unicode was sporadically supported. C has digraphs and trigraphs because even the ASCII punctuation wasn't guaranteed to be available on all keyboards. IBM, notably had an APL typeball for their Selectric derived terminals but that was equivalent to switching character sets and not something that could be considered universal prior to Unicode.
ASCII is a 7-bit encoding, so adding more symbols to it would rather defeat the point.
Once you already had that encoding established, in a time of 8-bit computing for which it had a practical purpose, it's historical momentum and inertia from there. Sure, we have Unicode now, but getting the entire industry to settle on including a sparkle emoji and a fire emoji on keyboard layouts is probably not going to happen.
is a particularly humorous instance of https://en.wikipedia.org/wiki/RAS_syndrome
(Yes, they could have just replaced the "regular" function keys with copy/paste keys, but I feel like that would have gone over about as well as the various times they've, uh, tried to replace the function keys)
Not sure if this was ever supported system-wide in any way, though.
Did the editor repace :) with [happy-face]?
Macintosh keyboard layouts tend to have many symbols on Option-combinations but they are not always printed.
(Strictly speaking, people did continue adding symbols. We used to talk about code pages: when the MSB was 0, the other 7 bits were ASCII. When the MSB was 1, the other 7 bits were a user selected code pade.)
Once you already had that encoding established, in a time of 8-bit computing for which it had a practical purpose, it's historical momentum and inertia from there. Sure, we have Unicode now, but getting the entire industry to settle on including a sparkle emoji and a fire emoji on keyboard layouts is probably not going to happen.