OK, WTF has happened to WordPress? Why does it suddenly think my blog is in Turkish? Not of course the contents, but all the template stuff, and – far worse – the settings and preferences that should (I guess, though I never actually tried it) enable me to switch to my choice of language.
Confirmed it’s not my browser playing sillybuggers by accessing it from three different browsers on three different computers. Chrome offers to translate this page, but that’s not going to help with a bunch of clientside-scripted menus!
OK, try another tack. ssh in to a remote machine on another continent and check the blog with lynx. Aha, it’s now in English! Hmm, could that difference be because I’m not logged in? Try to log in, but fail because Lynx rejects WordPress’s SSL certificate and refuses to talk to it.
OK, what happens if I fire up a spare browser that’s never logged in from a local desktop? It’s in English. And when I log in with Safari, it’s still in English. This is getting silly!
Resolution: when I reload this composition page in Chrome, it’s reverted to English. Someone or something was playing sillybuggers but got fixed. Was WordPress hacked? Did some sysop at WordPress screw up?
Or could it even have been some sysop at my ISP running a supposedly-transparent proxy that messed with browser preferences? That’s the most worrisome: I got email from them recently inviting me to “protect” myself, and I suspect they’re implementing some Endarkenment. A glitch in something more sinister? My next test would’ve been to route my (turkish-infected) desktop browser through another network, but the return to English pre-empted that.
I don’t know when whatever caused the Turkish first appeared, only when I first saw it – which was a little before 09:00 UTC. Anyone else see Turkish wordpress in recent hours? Or even – if you’re a Virgin broadband user – other sites unexpectedly in Turkish?
[geek note: I could also have tested for a rogue browser preferences setting by visiting a multilingual site like Apache server docs that display in Turkish if your browser asks for it. But that would’ve left open the possibility of misdiagnosing a glitch associated with an ISP-run database having different routing/rules for different sites].
 Iceweasel, Firefox and Chrome, in that order.