> 2) When an auto-capitalized correction is retyped by the user, don’t preserve capitalization
Seriously, this isn't even a feature for anyone ever, it's a straight-up bug I seem to get hit with several times a day.
But my absolute biggest problem with autocorrect isn't even on this list.
It's when I swipe-type a word and the correct word comes out. Then I swipe-type a second word, and my iPhone decides the first word was wrong, and changes it to be more probable with the second word.
Now, it's super-frustrating but wouldn't be the end of the world if I could just easily tap somewhere to restore the original first word. Occasionally it's listed as one of the options at the top of the keyboard, but not usually. Usually I've got to backspace through both entire words, retype the first word again, hit space twice so the iPhone "forgets" about being in double-word-correction mode, hit delete twice to delete the period-space, hit space again, and finally type my second word!
It drives me nuts. I read what I'm typing as I type it. I don't ever want my phone to fix a word earlier. I wish so badly there were an option to disable this.
Regarding the last point specifically, there is an established texting convention. Say you you (or autocorrect) have made a mistake and typed word A and you have already sent the message, but really you meant word B. Then, if you notice this mistake (granted, if), it is common convention to simply reply “*B”. Then, when the recipient reads to the mistaken word A and wonders why the word A seems out of place, they can look at the subsequent message and substitute B for A, without you even having to explicitly designate which word you made a mistake in (this is still sometimes necessary, but rarely).
Slack has some surprising, hard to discover UI tricks. Another one I learned recently is you can make text into a hyperlink by copying a URL to your clipboard, highlighting the text in Slack, and pasting. https://twitter.com/ftrain/status/1240387882507997186
Ha, cool trick! Reminds me of the Trello trick where if you press the 'copy' keyboard shortcut while hovering over a card, it will copy a link to that specific card.
I see and use "B" as a correction instead of "B". It's very annoying when I'm correcting autocorrect, ie B automatically changed to A, because then in the follow up message it usually changes it again, so I end up with A*.
> This inability seems the IT industry at it's worse. It's like some Frankenstein putting immutability onto human beings.
I don't understand. Communication has historically not been possible to "edit". There's nothing inhuman about that. If I say something, I've said it. Of course I can later make a correction, but the words I said remain said. The same has been true for the thousands of years we've had written communication, until a few years ago (on some platforms).
Personally, I find editing messages a misfeature. There's few things more annoying than replying to a message, and then finding out that the message you're replying to has been replaced by another one. If a platform has this feature, it makes me less likely to use it.
While I do agree, I find that marking a message as 'edited' (like Telegram does) makes it less of a problem for me. Bonus points if I can click to see the original message!
No, we have always been able to edit communication until the internet, because conversations/everything has always been unrecorded or very hard to access the archives of.
Have you never had an argument get to 'you said this', 'no I did not' ? We even edit our own messaging in our heads.
We make mistakes, why can't we correct them?
(We are talking autocomplete of spelling and grammar here at the original level)
And since obviously your end can have a setting/hack/default to keep the original anyway I'm not sure what the fear is.
> No, we have always been able to edit communication until the internet, because conversations/everything has always been unrecorded or very hard to access the archives of.
Spoken, yes. Written, no. But sure, most communication is (and certainly was) spoken, I'll give you that.
> Have you never had an argument get to 'you said this', 'no I did not' ? We even edit our own messaging in our heads.
I'm afraid I have. They suck tremendously. Do you think these arguments are a good thing?
> We make mistakes, why can't we correct them?
We can. We post a correction. "Sorry, I meant to say this."
> (We are talking autocomplete of spelling and grammar here at the original level)
Unless you produce a magic AI that lets people fix only spelling mistakes and nothing else, we're not talking about just that.
> And since obviously your end can have a setting/hack/default to keep the original anyway I'm not sure what the fear is.
Most communication platforms these days are actually not controlled by the users, so no, I can't have a setting for it. And if I have a hack for it (which probably requires a tremendous amount of technical expertise, out of reach for most people), I'm almost certainly in violation of some EOL and may get banned. Heck, in some crazy jurisdictions I could even end up in trouble with the law.
Any SMS conversations that aren't with trusted friends. Like landlords, or bosses, or maybe arranging the visitation with your ex.
As far as an audit trail is concerned, you'd need to have all the cell carriers update their SMS infrastructure to save the associated edit history along with the text of each message. That's definitely non-trivial.
I'm not saying it's a bad idea to have this feature, just that it's much more work than you realize, and the benefit is probably not there to justify the work. Slack has the luxury of controlling their entire platform. They don't rely on Ericsson or Qualcomm or Nokia to implement new features the way SMS would.
I've had this problem quite a lot with both the default keyboard and with GBoard, although seemingly a little less frequently with GBoard. I also find that the speech-to-text often fails to grasp the contextual clues and blatantly uses the wrong "your" or the wrong "their."
GBoard is as bad as all others and only marginally better in some situations.
A couple of minutes ago I tweeted a post that included the word somehow. GBoard changed it to *someone. I went back and highlighted the word, changed it to somehow, verified it was corrected and submitted. In some fraction of Google's wisdom, it recorrected the word back to someone. Argh
I think a lot of this is context and language dependent: I've noticed on an android device I sometimes use instead of my main phone (which is dumb) that sometimes the autocorrect is really smarter than I thought.
In Italian "c'è" means "there is", which is supercommon and also a pain to get right with apostrophe and diacritic, but "ce" is a valid pronoun: if you start typing by typing "ce" it will autocorrect to c'è, but if you go on typing "l'hai" ("ce l'hai" = "do you have it") it will autocorrect the "c'è" back to "ce".
On the other hand, I've recently had the opposite problem in Swedish. The autocorrect on my android treats å, ä, and ö not as proper letters but as a or o with diacritics. For many words with an o or a it seems to prefer words spelled the same but with å, ä, or ö in it. Even when I keep correcting it back again and again.
For some common words it doesn't do it, but for most it does. One common and consistent example is mot (towards, against) which becomes möt (imperative form of meet)
I even don't know somebody who use auto-correct. It's the first thing to turn off in every phone. I'm surprised to hear here from people who say they really use it.
The problem is the cross-over between spell checking and finger location.
if I mistype something because my finger comes down on an adjacent key, with autocorrect turned off, I can figure it out.
Say I want to type QWER and type FDSA by mistake, tomorrow when I read what I typed, figure out where my fingers were and recreate QWER.
But with autocorrect which does spell checking and semantic stuff, there's a good chance that FDSA will be corrected to something like FORD or VISA and I will never be able to recreate what I was thinking of.
I'm sorry I don't have a less contrived example.
The reason I did this was because I had some important things I jotted down quickly, and later - even with an hour of thinking - I could not recreate my original thought.
I had to just turn off most “correction” features because it was more frustrating to manually fix wrong autocompletes than to simply type in a continuous flow.
And plenty of blame should be reserved for the keyboard design itself, causing mistakes. I literally started developing a new keyboard extension as a side project for no reason other than to move keys that constantly tripped me up. (Worst offenders are the stupidly-close backspace and action buttons so that half the time I send wrong text when I meant to delete a letter.)
I think Apple's autocorrect will be seen by historians as a very strange blind spot.
I have a high end iPhone and autocorrect routinely slips in some corrections after I've already scanned the text visually and decided to press send.
The corrections are usually not desired, and often replace valid sentences/words with guesses that are more common words, even at times words or abbreviations that I know I have texted years ago but never since.
I'm not sure what's worse, the bad behavior of AutoCorrect or how laggy it is on my iPhone XS.
Turn Auto-Correct off by default, and you're set. It's really insane how many places auto-correct sneaks itself in and replaces what you type as you type stuff correctly in the first place.
Yep, on iPhone it’s more an hindrance than help especially when mixing languages, so I disable it as soon as I can.
One thing I miss about Windows Phone keyboard was how good the prediction was. On iPhone it can predicts a useful word from time to time after months, but on WP I could type parts of long sentence without having to enter any new letter.
The first thing I do on a new input device is disable autocorrect for good. If you write regularly in three different languages, it's more a hindrance than a help.
Same, albeit just two languages. Also, in Norwegian we use compound words. So for example "garage door" is "garasjedør" ("garage" = "garasje"). The auto-correct on my Android hardly gets any of those right.
I've noticed my friends who use auto-correct usually don't compound words, which can change the meaning of the sentence completely.
I have two issues in Finnish with Android's (Gboard) autocorrect: inflection and language selection.
In Finnish, words can have over a thousand inflected forms. Granted most of them are not used usually but every day I bump into a word that the autocorrect knows but when I add the inflection, it no longer recognises it. It tells me that it doesn't actually parse or "know" Finnish text, it just has a huge word list.
The second issue is that it decides which language's suggestion to show based on the characters I've typed (since I have it set to both English and Finnish). Normally it shows suggestions from both languages but if I type a single ä, ö, or å, it never suggests an English word. This is unfortunate since I sometimes hit such a character by accident and I have to go back and retype the word from that point to get back the English suggestions.
SwiftKey generally does a good job with multiple languages, although it will sometimes replace an English word that I typed correctly with the Spanish word (which is spelled the same but has a stress mark) in an otherwise fully English sentence, with me unaware why it's making the distinción.
Wow, i never even thought to do this, but i just did and i haven't had such a nice time typing in forever! The instant i turned it off it started typing better. Before now, i always had misspellings due to autocorrect, but not anymore. It's amazing i never thought to do this.
The only problem i have now is with the i not becoming capitalized automatically.
right! you would think that maybe someone would have thought about capitalizing a lone letter i. i don't care if everything else is lowercase, but sheesh give us a capital I algorithm.
I wish i had the option of turning off the ML autocorrect since it sucks but leave some basic features. Google is always all or nothing, it's fucking stupid. Like, i have to turn on my location history to give my wife my location in Google maps, no thanks, but it would be nice to share with her without that privacy busting crap.
I use swiping on a Samsung phone and regularly write in three languages (English, Swedish, and Dutch). While there are some annoyances, I find it still speeds it up a lot as long as I change keyboard language (done by swiping left or right on the space bar) to match the language I'm currently using.
Same, it's causing more frustration than it's worth for me. Call me a luddite but I don't like things changing what I wrote. Keyboards should be more accurate.
Because autocorrect is opt-out, not opt-in. The space key is used to confirm an autocorrection, on iPhone at least. To avoid it you need to explicitly tap the “verbatim” autocorrect choice. 9/10 times I don’t even notice autocorrect. It’s jarring when I need to go fix it.
In many cases the default is auto correct will pick the word it thinks you want. Unless you turn it off there is no way to force a different word once it has made a choice.
Depends on the keyboard of course, but there really isn't a good override by default.
Seriously, this isn't even a feature for anyone ever, it's a straight-up bug I seem to get hit with several times a day.
But my absolute biggest problem with autocorrect isn't even on this list.
It's when I swipe-type a word and the correct word comes out. Then I swipe-type a second word, and my iPhone decides the first word was wrong, and changes it to be more probable with the second word.
Now, it's super-frustrating but wouldn't be the end of the world if I could just easily tap somewhere to restore the original first word. Occasionally it's listed as one of the options at the top of the keyboard, but not usually. Usually I've got to backspace through both entire words, retype the first word again, hit space twice so the iPhone "forgets" about being in double-word-correction mode, hit delete twice to delete the period-space, hit space again, and finally type my second word!
It drives me nuts. I read what I'm typing as I type it. I don't ever want my phone to fix a word earlier. I wish so badly there were an option to disable this.