Could we have an option to enable autocorrect on typing an answer? I know that previously we’ve said that typing disables autocorrect to make sure you write the correct answer (see Forum post from 2021, can’t seem to add a link here?), but if I’m doing “reverse cards” (e.g. Japanese → English) then I don’t really need to be tested on spelling in my native language. It would be super helpful to be able to be able to specify something like {{type autocorrect=true:Answer}} to enable autocorrect when desired.
I’d be willing to help code / test this if the build setup isn’t too hard on Mac.
An easier solution would be not using a type-answer field on your “reverse card” template. That’s a quick edit for you to make. But speak up if you have questions about how to do it.
2 Likes
I want to actually write an answer and have it checked, but I don’t need to checked on spelling. Autocorrect would be the right solution.
How do you thing this should work? If I understand correctly you want something like this:
- You type world but the field expects World. It should be shown as green (correct).
- You type dog but the field expects World. It should be shown as red (wrong).
Is that what you’re looking for? In that case some js in the card template could potentially achieve this.
Also see:
1 Like
Type-answer fields are designed for short answers where spelling is important. If you’re using autocorrect to alter your answer, then that defeats the point of having Anki check it character-by-character.
If you just want a field to type an answer into, then there are other ways to do that. But I’m sure you can understand that autocorrect functionality is a massive undertaking, even for one language, let alone many. I think it’s unlikely that it is going to be added to the app for type-answer cards.
Platforms like macOS and iOS have autocorrect built in, but Anki intentionally disables autocorrect in type-the-answer fields. The request is for an option to re-enable it.
1 Like
A lot of you are thinking along the lines of a desktop PC with a keyboard, such that what I intend to type is what I get. That’s not true on mobile. On iOS if I want to type “firetruck” I might get “firetrick” or “firrtruck”. This is why autocorrect exists. It’s not just a convenience for those who can’t spell, but because virtual keyboards suck.
Again, the point is to give an option to enable or disable autocorrect as needed. If your deck is such that you want to test spelling, then leave it turned off. If, in my case, you’re testing words and phrases such that autocorrect helps speed things along, then it can be turned on. It should be very easy to implement, yet gives users the ability to choose what makes sense. Can be turned off by default if you think that’s the right answer.