Zevencijferige telefoonnummers in Rotterdam, Den Haag, Amsterdam

▼ Ik kwam laatst een oude kaart van Den Haag tegen en ik vroeg me af van wanneer die was. Er stond geen jaartal op. Wel viel me op dat de telefoonnummers die erop stonden maar zes cijfers hadden, dus van voor dat alle Haagse telefoonnummers er een 3 bij kregen. Maar wanneer was dat? Het lukte mij niet deze info terug te vinden via Wikipedia of Google.

Ik herinner me dat in Amsterdam er een tijd zowel zes- als zevencijferige telefoonnummers gebruikt werden. En iemand schreef zelfs dat dit vanaf rond 1972 was. Via de Fidonet nodelist kon ik achterhalen dat de overschakeling van zes- naar zevencijferig tussen oktober 1990 en januari 1991 gebeurd is.

Voor zover ik me kan herinneren had Rotterdam al een hele tijd zevencijferige nummers die met een 4 begonnen voor wij in Den Haag de 3 kregen. Uit de nodelist blijkt dat in januari 1990 Rotterdam de 4 al had.

En voor Den Haag zien we de overgang van zes naar zeven cijfers tussen augustus 1989 en januari 1990.

Op 10 oktober 1995 volgde met Operatie Decibel de rest van Nederland, met ofwel een driecijferig netnummer en zeven cijfers voor het abonneenummer, ofwel een viercijferig netnummer en een zescijferig abonneenummer.

Sindsdien is er in Nederland voor zover ik weet niks meer veranderd aan de telefoonnummers, maar uit onderzoek voor twee los van elkaar staande zaken viel me wel op hoe veel en vaak telefoonnummers in verschillende delen van de wereld veranderen.

Permalink - posted 2021-05-13

Getting the "Music" miniplayer back to actual mini

▼ I just had a moderate-size scare: I typed something into iTunes Music, and the miniplayer now showed playback controls:

That's not what I want. I want it to show the album artwork. That's how I've used iTunes and now Music for many years. If I need to interact with the controls, those will then come up when I place my mouse pointer over the miniplayer window. In the view menu, there is no option to get back to my usual setup.

But it's pretty easy to do this if you know how: just drag the bottom corner of the miniplayer window up until the window is roughly rectangular, and after releasing the mouse button:

This is actually quite a good way to change the layout of the miniplayer. (You can also make the window even smaller or even larger to get different results.) However, it's also extremely un-discoverable.

A free tip, from me to you.

Permalink - posted 2021-04-13

I did it again... I made another keyboard tester

▼ The other day I noticed how dirty my VT420 terminal's keyboard was, so I decided to take off the keycaps to clean them.

Then of course it's always good to put the keycaps back where they belong. That's a task made a lot easier with a keyboard tester app such as the online one I made a while ago. However, I don't think the VT420 supports the latest Javascript features...

So I whipped up a command line keyboard tester: kbdtest.php. Save the page, rename to kbdtest.php, then run with "php kbdtest.php". Works on the Mac, haven't tested other systems.

The script draws an image of the main part of a keyboard, with the keys that should work displayed in red. Then as you type them, they're made the default color and bright or bold. Typing the same key multiple times adds and removes an underline. The first number is a count of how many different keys you've typed, the second one only counts printable characters and tab, backspace and enter. (Upper vs lower case is ignored.) When you've typed all 71 of those, the program ends. You can of course also use control C. When there's 8 characters left, the remaining ones start to blink.

Note the box drawing characters. These are actually produced by issuing an ANSI escape code to switch to the DEC special graphics character set. In that mode, the lower case characters become line/box drawing characters. Turns out: this also works in the Terminal on the Mac!

I couldn't find a workable way to get the actual keyboard scan codes or something similar on the command line, so I can't do anything with keymaps, like the web keyboard tester does. However, turns out you can still read special keys such as the function keys and arrow keys. These produce ANSI escape codes. And again, that works in the Terminal exactly like it does on the VT420 terminal.

Permalink - posted 2021-03-16

A new life for the 2003 Apple Wireless Keyboard

▼ Back in 2003, Apple released the Apple Wireless Keyboard:

(Not to be confused with later keyboards of the same name that look like laptop keyboards.)

The keyboard still works with an ancient MacBook Pro, but it won't pair with anything from the 2010s. That's too bad, because I think it looks pretty nice. So I decided to see if I could bring its essence into the 2020s by transplanting the keycaps to my Drop CTRL keyboard.

Here on the left is a regular MX style keycap, and to the right one from the AWK2003. Not so different.

Until we turn them over:

However, the AWK2003 keycap will fit on a Cherry MX style switch, especially a Kailh box switch:

But the fit is too loose. However, we can fix that with some teflon tape.

Three layers seems to work well:

And there it is: the Drop CTRL keyboard with 2003 Apple Wireless Keyboard keycaps:

The keycap profile is a bit different, especially on the bottom row, as you can see with the alt key:

It's not possible to replace the entire bottom row with keys from the AWK2003, as only the alt key has a standard size.

So I used the regular keycaps for the bottom row and the cursor keys:

With three layers of teflon tape, the keys mostly stay put, but this is what can happen after a good long typing session...

Permalink - posted 2021-03-05