Taking a break from the travel blog, to get a long overdue task out of the way. I was clearing out my phone and iPad of old photos, I ran across a bunch of spellchecking errors that I’ve been capturing over the last year or so, vaguely planning to post them somewhere. Might as well do it now, while I’m looking at them, and this seems like a convenient place to do it.
Look, I get that spellchecking programs can’t be perfect. I don’t expect them to recognize arcane terms, all the computer acronyms and slang that I know, geek/scifi phrases, etc. If I call someone a noob, or a skrill, or reference a dyson sphere, or use “legal” but unconventional English, a red highlight in a normal editor doesn’t surprise me. So, it’s not unexpected when things like this happen:
But they are, of course, really annoying, because iOS autocorrects unless you spot it trying and hit that little “X” to abort the process. And, when you don’t, you either get weird errors that puzzle your audience, or you catch them after the correction and have to delete and retype, sometimes several times. Maddening.
And some of this, I have no idea what weirdness of programming would cause it to fail. Like:
Of course, where my iOS devices really break down is at the apostrophe. Apparently, these miracles of modern technology have the same problem with contractions as Commander Data — perhaps Data’s ancestral routines come from Apple. (And, honestly, would you be surprised if that were true?) Once an apostrophe appears, iOS just freaks the fuck out, and starts grabbing for random alternatives, resulting in a long list of these:
On the plus side, at least there’s some consistency in its insanity:
And yet, consistency doesn’t help with things like this, does it:
I do think iOS is changing a bit. The recent miscorrections have stopped including the letters in front of the apostrophe, as we see here:
So, maybe the change is a harbinger of a real fix in the future. Though I confess, I would miss the comedy value at least a tiny bit.