Slashdot Mirror
An iOS 11.1 Glitch Is Replacing Vowels (mashable.com)
An anonymous reader quotes Mashable:
We became privy to a new iPhone keyboard glitch after a few Mashable staffers recently started having issues with their iPhone keyboards, specifically with vowels. The issue started when iOS 11's predictive text feature began to display an odd character in the place of the letter "I," offering up "A[?] instead and autocorrecting within the message field...The bug was also covered by MacRumors, but it appears that my colleagues have even more issues than just the letter "I." One reported that they were also seeing the glitch with the letters "U" and "O" as well, making the problem strictly restricted to vowels. They also said the letters showed up oddly in iMessage on Mac devices, and shared some more screenshots of what the glitch looks like when they went through with sending a message. The glitch wasn't just limited to iMessage, however. My colleagues shared screenshots of their increasingly futile attempts to type out messages on Facebook Messenger...and Twitter.
Apple seems to be acknowledging that the iOS 11.1 glitch may affect iPhones, iPads, and iPod Touches. "Here's what you can do to work around the issue until it's fixed by a future software update," Apple posted on a support page, advising readers to "Try setting up Text Replacement for the letter 'i'."
Apple seems to be acknowledging that the iOS 11.1 glitch may affect iPhones, iPads, and iPod Touches. "Here's what you can do to work around the issue until it's fixed by a future software update," Apple posted on a support page, advising readers to "Try setting up Text Replacement for the letter 'i'."
Noticed this not I have. But then Welsh I am, Boyo.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Like the Headphone jack, vowels are obsolete. It makes sense for Apple to phase them out for us in their latest phones, hopefully leading the rest of the industry to remove them from Android phones, keyboards in general, and so on, within the next couple of years.
Now, sure, some might say "Hey, I still use vowels, they're really useful when you're trying to distinguish between two words that have the same consonants, but a different sound joining them, like "cat" and "cut"", but that's old thinking, as leaving a gap is perfectly fine and should be good enough for everyone. Who cares if you were using lots of cheap old consonants? They're inefficient and completely unnecessary. So cat at out.
You are not alone. This is not normal. None of this is normal.
Does this explain the outbreak of &@(TM)$ that seems to be afflicting our beloved site?
At the bottom of the
Hundreds of new emoji are coming with iOS 11.1 !! Youhou !!!
Ceci n'est pas une Signature !
Just because you have new hardware or OS, why rewrite the code for an application that already works? Of course, maybe they didn't rewrite the keyboard code and something in the OS is interacting with the keyboard code that's screwed up. In either case, there's a quality control testing problem with code development .
In a time of universal deceit, telling the truth is a revolutionary act. George Orwell
Yr Hldng T Wrng
Write English!
Damn Czechs.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Irritable Vowel Syndrome.
Don't worry, vowels have not been completely depreciated, you can buy them as a dongle now.
The problematic sequence that gets generated is the capital I followed by the hex sequence ef b8 8f, which is known as Variation Selector 16. That's “An invisible codepoint which specifies that the preceding character should be displayed with emoji presentation. Only required if the preceding character defaults to text presentation.” So in a sense it's technically correct, it's trying to say to display an eye or eyes when you've typed an "I". The problem is twofold: a) people aren't trying to type emoji, and 2) it doesn't actually work.
Michael J.
Root, God, what is difference?