-
Notifications
You must be signed in to change notification settings - Fork 70
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
[Deleted] New Translate UI #49
Labels
blocked
Another issue is blocking
feature
New feature or request
help wanted
Extra attention is needed
question
Further information is requested
wontfix
This will not be worked on
Comments
This was referenced Nov 23, 2021
2 tasks
The UI for this feature was created in #222 :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
blocked
Another issue is blocking
feature
New feature or request
help wanted
Extra attention is needed
question
Further information is requested
wontfix
This will not be worked on
Terms
Description
The current version of the
Translate
command is not at all what it has the potential to be. As inConjugate
, the Scribe keyboard UI could be changed to make a very intuitive translation feature that's solely based on open source data. Initially it would be used to translate basic words and phrases in a very accurate way, and later more advanced translations could be added - all this without users being tracked or the necessity for an internet connection.Take the word
book
.In English this is both a verb and a noun, so Scribe could realize that there are multiple options and ask the user what they'd like with simple button presses as options. So
Scribe key
->Translate
and the UI could look something like:Selecting one of the options could then lead to another screen where options would be presented with their synonyms (kind of like how Google translate will show synonyms of words).
How multiple options would be scrolled through effectively would need to be figured out. This feature could also include options to get the masculine or feminine versions of certain nouns.
This issue is for discussing and eventually implementing the UI for this new version of the
Translate
command. Suggestions and contributions are very welcome!The text was updated successfully, but these errors were encountered: