-
Notifications
You must be signed in to change notification settings - Fork 105
[Deleted] New Translate UI #49
Copy link
Copy link
Closed
Labels
blockedAnother issue is blockingAnother issue is blockingfeatureNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededquestionFurther information is requestedFurther information is requestedwontfixThis will not be worked onThis will not be worked on
Description
Metadata
Metadata
Assignees
Labels
blockedAnother issue is blockingAnother issue is blockingfeatureNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededquestionFurther information is requestedFurther information is requestedwontfixThis will not be worked onThis will not be worked on
Terms
Description
The current version of the
Translatecommand 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->Translateand 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
Translatecommand. Suggestions and contributions are very welcome!