[FEATURE] iPhone keyboard: autocorrect in Spanish as well as English
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ios, swift
- Domain
- internationalization, mobile
Research direction
Start in the iPhone app’s keyboard and autocorrect implementation; the issue does not name files or tests, so first locate how the keyboard loads dictionaries and handles held-letter accents. Done means users can select English and Spanish together, correct words in either language are preserved, and the requested accents are available. Test the language pair in the TestFlight keyboard.
Written by the indexing model from the issue text.
Description
Problem
I write in English and Spanish. The FluidVoice keyboard on iPhone doesn't load a Spanish dictionary, so it autocorrects Spanish words I typed correctly into broken English. To avoid that I switch to another keyboard, then switch back to dictate.
It's the same problem as the missing accents, which the stale bot closed. I can't stay on one keyboard without both.
Proposed solution
Let me choose the keyboard's languages, English and Spanish in my case, and load those dictionaries together, so autocorrect leaves a correct word in either language alone. Include the hold-a-letter accents from that earlier issue.
Apple's keyboard works this way for some language pairs: "you can type in two languages without having to switch between keyboards."
Alternatives considered
Switching to Apple's keyboard with the globe key works, but it's extra taps every time, and I have to switch back to FluidVoice to keep dictating.
Setup: FluidVoice iPhone app, TestFlight beta.
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from altic-dev/FluidVoice
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
altic-dev/FluidVoice#1284 ·
Maintainers usually reply within 1 day
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
altic-dev/FluidVoice#1191 · 3 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
altic-dev/FluidVoice#1307 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
altic-dev/FluidVoice#1304 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
altic-dev/FluidVoice#1298 ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nightscout/Trio#1748 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
carp-dk/flutter-plugins#1312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
newrelic/newrelic-flutter-agent#256 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day