Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Looks to Streamline Clarification of Awkward Autocorrect Messages in New Patent Application
- Thread starter MacRumors
- Start date
- Sort by reaction score
No one is proposing to change that scenario. Pay attention! If you type out a misspelled word, like your name, from going too fast, autocorrect should still come into play. The point is when you actually spell the word correctly, and autocorrect decides that that word you put in the effort to spell correctly isn't in fact the word you meant. And it changes it to a whole other word, sometimes using letters that aren't even near the ones you typed.
This needs a patent? I guess Macrumours will have to stop using their edit function now ...
I'm being glib, I get that it's specifically per word, highlighted that you changed it and gives you alternatives. It would be a great feature and I'm surprised no one's done it yet (maybe they have and I live so sheltered in my Apple bubble that I've never noticed it).
However, wether they patent it or not, the function of edited messages can (and will) now be implemented in a dozen different ways. Every single IM app will just do it anyway. It won't be a unique selling point for long.
I'm being glib, I get that it's specifically per word, highlighted that you changed it and gives you alternatives. It would be a great feature and I'm surprised no one's done it yet (maybe they have and I live so sheltered in my Apple bubble that I've never noticed it).
However, wether they patent it or not, the function of edited messages can (and will) now be implemented in a dozen different ways. Every single IM app will just do it anyway. It won't be a unique selling point for long.
It would be better if clarification corrected the original message. But there're no real UI and UX designers at Apple now, only managers... Or they are suppressed by managers...
They finally feel they need to do something about the awkward correction. Sometimes I really want to smash the phone because of it.
I have to believe a lot of people much smarter than either one of us have been trying to "fix" autocorrect since the iPhone was launched. It has gotten better.
Quite often, I accidentally tap the shift key instead of "a". Autocorrect usually catches it, and fixes it. It would be very Nnoying if Utocorrect ignored words that include cPitals.
I saw someone else addressed this, but I'll reiterate. I'm sure toy have make this mistake before.
Autocorrect has improved a lot the last seven years, I'm sorry you don't see it. It seems to me, you want autocorrect to read your mind, and know exactly what you intended to type. That's still a few years off, try to hold out.
[doublepost=1461944702][/doublepost]
You might want to see someone about your anger.
I wish autocorrect would never replace anything I type with a proper noun. It does it a lot, and never correctly.
Only 2016 Apple would come up with an over-complicated patentable system instead of simply fixing the autocorrect that is so terrible it's had countless jokes made about it. It's not like they don't have
-Thousands and thousands of employees working for them
- billions of dollars in cash laying around
- a fancy new HQ where everybody can collaborate on actually improving the product
But hey, I got new emojis and an API to make the Music app I stopped using due to its terribad UI even more intrusive.
Glad to see the priorities are still straight.
-Thousands and thousands of employees working for them
- billions of dollars in cash laying around
- a fancy new HQ where everybody can collaborate on actually improving the product
But hey, I got new emojis and an API to make the Music app I stopped using due to its terribad UI even more intrusive.
Glad to see the priorities are still straight.
I did too at one point, until I realized just how many errors I make (autocorrect corrected two words in this sentence)
My single biggest gripe with iOS, auto correct is terrible. Have to switch to google to find spellings.. Miss BB in that regard, had amazing auto correct, and great learning dictionary that was easy to manage. iOS tries to do too much under the hood, locking us out of control.
China is over the sandbox and sales are plummeting.
Apple has the best hardware, but the software is way to dummy downed. We need an expert mode - oh, is that jail breaking?
China is over the sandbox and sales are plummeting.
Apple has the best hardware, but the software is way to dummy downed. We need an expert mode - oh, is that jail breaking?
Nope, never blame anything on malice that can be adequately explained by stupidity. In this case, marketing was able to check the feature box that iMessage has autocorrect. No additional resources would be of any value because the marketing message won't change.
Or, just fix their autocorrect system in the first place. I am getting tired of Apple's autocorrect making errors rather than sending the text that I am typing, I don't need a system that helps the receiver try and understand what Apple's lousy autocorrect actually sent.
I've used both Apple and Android on-screen keyboards and by far Apple is still light-years behind on their autocorrect behavior and performance.
I've used both Apple and Android on-screen keyboards and by far Apple is still light-years behind on their autocorrect behavior and performance.
Just pronounced Canada as written, and laughed quite loudly. That's a keeper right there.
How about just not autocorrecting words that you spelt correctly in the first place? I still don't understand what the point of that is.
Also, words that are correct save for a single character. Instead of looking for the simplest solution (changing one character) autocorrect sometimes goes ahead and changes it into a completely different word. It makes no sense. It should do the least amount of damage first, and then get increasingly invasive if it can't find a correctly spelt word.
For example, if I type "Gardem" instead of "Garden", it should always try to see if changing one letter could fix the spelling, rather than skipping straight to something like "Gardeners" or "Gardening" or whatever. I don't literally mean this exact word, but you get what I mean. It tends to work okay in English but it has serious issues in some other languages, especially with accents.
Also, since iOS does not have accents on its keyboards even if you switch to another language (no, the push-wait-hold-select-release pop up menu is not practical for typing), for languages that use lots of accents, people just end up typing without accents. That's fine, everyone understands what you mean. Except autocorrect. It confuses the hell out of it. For example (again, not literally this word, but you get it), you type "Exposé" in French, but not being able to quickly type "é", you just type "Expose", which autocorrect will change to something ridiculous like "Elephants" or whatever. First try to check if there isn't an accent missing, damn it. I thought it was common sense to try to change as little as possible first.
Also, words that are correct save for a single character. Instead of looking for the simplest solution (changing one character) autocorrect sometimes goes ahead and changes it into a completely different word. It makes no sense. It should do the least amount of damage first, and then get increasingly invasive if it can't find a correctly spelt word.
For example, if I type "Gardem" instead of "Garden", it should always try to see if changing one letter could fix the spelling, rather than skipping straight to something like "Gardeners" or "Gardening" or whatever. I don't literally mean this exact word, but you get what I mean. It tends to work okay in English but it has serious issues in some other languages, especially with accents.
Also, since iOS does not have accents on its keyboards even if you switch to another language (no, the push-wait-hold-select-release pop up menu is not practical for typing), for languages that use lots of accents, people just end up typing without accents. That's fine, everyone understands what you mean. Except autocorrect. It confuses the hell out of it. For example (again, not literally this word, but you get it), you type "Exposé" in French, but not being able to quickly type "é", you just type "Expose", which autocorrect will change to something ridiculous like "Elephants" or whatever. First try to check if there isn't an accent missing, damn it. I thought it was common sense to try to change as little as possible first.
Interesting. Never use autocorrect myself, I'd rather just have the predictive text suggestions so I have the option rather than a correction being forced on me.
[doublepost=1461954019][/doublepost]
Amen, brother.
[doublepost=1461954019][/doublepost]
Amen, brother.
I like the idea, but having a clarification system send a second, canned response seems like a clunky solution. What if (for iMessage conversations at least) you could correct a word after you sent it, and it would actually edit and update the message on all parties' phones? There could even be a little symbol next to the edited text bubble (sort of like when the text fails) to let everyone know that the message was clarified.
For text message users, the system could fall back on the canned response.
For text message users, the system could fall back on the canned response.
'Spotty', you say?
It very often corrects things that I typed perfectly correct to different things. Ie..
"Come over" to "Coke over"
"going to" to "gong to" (I never used the word gong, either)
Sometimes I think it will correct one character and be fine. For example, I typed "shed" hoping it would put an apostrophe for "she'd" -- or leave it. Instead, it changed it to Shevardnadze (which I had to look up out of curiosity).
It very often corrects things that I typed perfectly correct to different things. Ie..
"Come over" to "Coke over"
"going to" to "gong to" (I never used the word gong, either)
Sometimes I think it will correct one character and be fine. For example, I typed "shed" hoping it would put an apostrophe for "she'd" -- or leave it. Instead, it changed it to Shevardnadze (which I had to look up out of curiosity).
What about letting us choose which language to use auto correct?
Now it's either on for all languages or not.
I find it helpful in most cases for English; I do agree it's annoying at times. But for Korean, it's almost always wrong. This is especially so when using abbreviated/slang words, which are used extremely often in Korean.
Now it's either on for all languages or not.
I find it helpful in most cases for English; I do agree it's annoying at times. But for Korean, it's almost always wrong. This is especially so when using abbreviated/slang words, which are used extremely often in Korean.
^ This ^ I'm not fully bilingual, so I do not have another keyboard active on my iDevice (I'm sure emoji and bitmoji don't count), however I live in Southern California and pasty-white as I am, a decent amount of everyone's vocabulary is Spanglish to some extent. I can't stand having to go back and re-type "comida" instead of the auto-corrected "Comedy" every time I ask my co-workers what we are eating for lunch.
I do appreciate how well autocorrect functions on SwiftKey. Combined with its lightning fast input, the stellar Android version has been nearly flawless.
Year after year SwiftKey has saved me loads of time. Combined with the lightning speed of the capacitive home button on my fabulous Nexus 6P, I now know just how far behind Apple's iPhone 6S Plus has fallen.
But no worries. No other company is as well equipped to catch up as Apple. If they'd just set aside their ego and get to work, they could create the best model yet.
Year after year SwiftKey has saved me loads of time. Combined with the lightning speed of the capacitive home button on my fabulous Nexus 6P, I now know just how far behind Apple's iPhone 6S Plus has fallen.
But no worries. No other company is as well equipped to catch up as Apple. If they'd just set aside their ego and get to work, they could create the best model yet.