Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to spellcheck and grammarcheck the OCR fields and product name using OS level systems #5398

Closed
teolemon opened this issue Jun 18, 2024 · 2 comments · Fixed by #5409

Comments

@teolemon
Copy link
Member

teolemon commented Jun 18, 2024

Problem

  • We have an ongoing effort for ingredient spellcheck
  • Some other fields (like product name) might benefit from OS-level spellcheck and grammar check.

Proposed solution

  • Add an option to spellcheck and grammar check the OCR fields and product name using the OS-level systems
  • Make it optional (dev mode) so that we can evaluate performance and impact

Part of

@teolemon teolemon changed the title Add an option to spellcheck and grammarcheck the OCR fields and product name Add an option to spellcheck and grammarcheck the OCR fields and product name using OS level systems Jun 18, 2024
@github-actions github-actions bot added the ⭐ top issue Top issue. label Jun 18, 2024
@g123k
Copy link
Collaborator

g123k commented Jun 18, 2024

Could you describe what you mean by spellcheck/grammar check?
Is-it the red lines in text fields? If yes, true, this is already available in Flutter and is just a parameter to add.

If you want a real automatic spellcheck, there are some solutions, but they force storing a dictionary of words per language.

@teolemon
Copy link
Member Author

Your first option, the easy one

@g123k g123k self-assigned this Jun 18, 2024
@g123k g123k linked a pull request Jun 19, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from 💬 To discuss and validate to 🎊 Done in 🤳🥫 The Open Food Facts mobile app (Android & iOS) Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants