{"id":35732,"date":"2022-04-29T16:20:44","date_gmt":"2022-04-29T20:20:44","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=35732"},"modified":"2023-03-28T09:49:22","modified_gmt":"2023-03-28T13:49:22","slug":"autocorrect-explained","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/04\/29\/autocorrect-explained\/","title":{"rendered":"Autocorrect Explained: Why Your iPhone Adds Annoying Typos While Fixing Others"},"content":{"rendered":"

Ben Lovejoy<\/a>:<\/p>\n

But yeah, people do complain, and even the guy who created the feature – Ken Kocienda – admits that sometimes it can be more of a hinderance than a help. Indeed, if you think that it’s gotten worse rather than better over the years, that can actually be true … <\/p>

The reason, paradoxically, is that autocorrect has grown more intelligent over the years, and the more we ask it to do, the more potential there is for new types of errors.<\/p>

The WSJ’s<\/a><\/em> Joanna Stern went on a mission to learn more about why autocorrect can sometimes be ducking annoying.<\/p>

[…]<\/p>

The personalized dictionary looks for words not in the static dictionary, which you have typed three times. That’s the point at which it decides you know what you’re doing, and it’s a real word. However, if you make the same typo<\/em> three times, it learns that instead!<\/p><\/blockquote>\n\n

John Gruber<\/a>:<\/p>\n

\n

Don’t miss the video<\/a>, which involves some actual ducking ducks.<\/p>\n<\/blockquote>\n\n

Louie Mantia, Jr.<\/a>:<\/p>\n

\n

You ever get that absolutely horrible bug in macOS messages where you’re typing a long message and at a certain point it starts chopping up everything you’ve written, replacing characters, moving entire passages, and duplicating text?<\/p>\n<\/blockquote>\n\n

Steve Troughton-Smith<\/a>:<\/p>\n

\n

This is the serious autocorrect issue Apple introduced in macOS 12 to Catalyst apps. Twitter also suffers from it. macOS 11, no problem<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n