4 ms·

You must have very good reasons for keeping AutoCorrect on. I’d really like to “hear” them as I’m feeling that I did not get the point and am missing out by tur

by nier 4y ago

You must have very good reasons for keeping AutoCorrect on. I’d really like to “hear” them as I’m feeling that I did not get the point and am missing out by turning it off. And with it off, I can still manually select valid corrections pretty quickly by tapping suggestions.

xlii 4y ago
Not OP but my reason is handling of diacritics on iOS. Typing “e” is a baseline but typing “é” feels like it’s 1.5s: hold “e” wait for diacritics to appear, choose one, continue. Not only this breaks flow but is slow as hell. Word with 4 letters with diacritics takes around 5-6 seconds and it feels slow. Autocorrect fixes most of those quite often. If language is widely supported (English/Spanish/French) it’s easy and there are other methods of typing (swipe, text prediction) but leave that area and typing on iPhone is painful. Use more than 1 language and it’s even more painful. It almost requires setting the stage to be able to type in selected language and is still janky. I don’t understand why it is like that. If I’m writing in context of website it should assume that I’m using language of that website and allow me to break out if I really need. There should be API that allows third party apps (chat apps, note apps) to set language by context (like recipient in chat, note in note talking etc.) so that I shouldn’t have need to switch languages at all. As I’m typing this comment autocorrect is “finding” corrections in 3 languages. I feel like I spent more time removing it than typing. And yet “languabes” is perfectly good and I had to fix it manually. There is context, I used this word more than once and it’s in the most supported language on the platform. Come on Apple, this is core user experience. This should be better!
- xattt 4y ago
  Being multilingual is the bane of the Apple input experience. My day-to-day interactions are in English, but I speak with family members in Russian. Whenever a Russian text comes through, English Siri will be sure to mangle it, like Mojibake of the mid-90s and early-200s. There is also no way to ask English Siri to play a song with a non-English title. There actually seems to be a cottage industry of Russian songs on Apple Music with literal translations for this reason. Russian Siri has a pretty good success rate at picking up English speech but I just don’t want Russian Siri for the rest of the day. Don’t get me started if you have a multi-language household and want to have HomeKit and Siri. I think the solution would be to have a UI for picking primary, secondary and tertiary languages for voice interactions. Sadly, I think there won’t be any work done because it’s not perceived as a priority, despite Apple’s messaging at inclusivity and diversity.

by nier 4y ago

xlii 4y ago

Not OP but my reason is handling of diacritics on iOS. Typing “e” is a baseline but typing “é” feels like it’s 1.5s: hold “e” wait for diacritics to appear, choose one, continue. Not only this breaks flow but is slow as hell. Word with 4 letters with diacritics takes around 5-6 seconds and it feels slow. Autocorrect fixes most of those quite often. If language is widely supported (English/Spanish/French) it’s easy and there are other methods of typing (swipe, text prediction) but leave that area and typing on iPhone is painful. Use more than 1 language and it’s even more painful. It almost requires setting the stage to be able to type in selected language and is still janky. I don’t understand why it is like that. If I’m writing in context of website it should assume that I’m using language of that website and allow me to break out if I really need. There should be API that allows third party apps (chat apps, note apps) to set language by context (like recipient in chat, note in note talking etc.) so that I shouldn’t have need to switch languages at all. As I’m typing this comment autocorrect is “finding” corrections in 3 languages. I feel like I spent more time removing it than typing. And yet “languabes” is perfectly good and I had to fix it manually. There is context, I used this word more than once and it’s in the most supported language on the platform. Come on Apple, this is core user experience. This should be better!

xattt 4y ago
Being multilingual is the bane of the Apple input experience. My day-to-day interactions are in English, but I speak with family members in Russian. Whenever a Russian text comes through, English Siri will be sure to mangle it, like Mojibake of the mid-90s and early-200s. There is also no way to ask English Siri to play a song with a non-English title. There actually seems to be a cottage industry of Russian songs on Apple Music with literal translations for this reason. Russian Siri has a pretty good success rate at picking up English speech but I just don’t want Russian Siri for the rest of the day. Don’t get me started if you have a multi-language household and want to have HomeKit and Siri. I think the solution would be to have a UI for picking primary, secondary and tertiary languages for voice interactions. Sadly, I think there won’t be any work done because it’s not perceived as a priority, despite Apple’s messaging at inclusivity and diversity.