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

FEATURE: Translate full sentences #386

Open
mathiasayivor opened this issue Sep 17, 2023 · 6 comments
Open

FEATURE: Translate full sentences #386

mathiasayivor opened this issue Sep 17, 2023 · 6 comments

Comments

@mathiasayivor
Copy link
Contributor

Description

Currently, we have to manually enter each slang we'd like to translate into the search box, and it becomes tedious when trying to translate a full sentence.

What if, instead of just entering the abbreviations one after the other, the user can enter the full sentence, and get a full translation?

If the user inputs a sentence like this (copied from the homepage):
"idk wtf ur on about... ICYMI IMHO RTFM, KISS, SHIT or GTFO."

It gets translated to:

"I Don't Know What The Fuck You Are on about... In Case You Missed It In My Honest Opinion Read The Fucking Manual Keep It Simple Stupid SHIT or Get The Fuck Out."

Screenshots

No response

@data111a
Copy link

interesting idea, I would work with great pleasure

@Njong392
Copy link
Owner

@mathiasayivor this looks interesting. I'd be interested to know how this would work. We'll have to go through the words in the sentence, check if they exist and then give the meaning? what happens when one word in the sentence does not exist for example

@mathiasayivor
Copy link
Contributor Author

@Njong392 Yes basically.

For words without a database match, we can consider them standard English words. However, I'm working on implementing measures to identify English words and detect non-English ones. If a word is deemed non-English, we assume its abbrev is not in the database and prompt the user for their input, possibly by suggesting they open an issue to add it.

Also, remember the contexts thing I suggested earlier in #42? This is one of the use cases. Translating sentences based on context, especially when an abbrev has multiple meanings

In addition, we would need some sort of backend processing for efficiency.

@mathiasayivor
Copy link
Contributor Author

Just to demonstrate, I created a simple prototype you can check it out here: https://github.com/mathiasayivor/abbreve-server. It's currently just a dummy, cos it's not context-aware, but that would be worked on once we add context to each definition.

@Njong392
Copy link
Owner

@Njong392 Yes basically.

For words without a database match, we can consider them standard English words. However, I'm working on implementing measures to identify English words and detect non-English ones. If a word is deemed non-English, we assume its abbrev is not in the database and prompt the user for their input, possibly by suggesting they open an issue to add it.

Also, remember the contexts thing I suggested earlier in #42? This is one of the use cases. Translating sentences based on context, especially when an abbrev has multiple meanings

In addition, we would need some sort of backend processing for efficiency.

The idea sounds really huge if u come to think of it. Right now, I have plans to create a backend for the application with MongoDB, that way we can really implement things a lot better. I'm still really not sold on the idea of storing entire phrases given the fact that we'll already have stuff like contexts and all the like.

@mathiasayivor
Copy link
Contributor Author

The idea sounds really huge if u come to think of it. Right now, I have plans to create a backend for the application with MongoDB, that way we can really implement things a lot better. I'm still really not sold on the idea of storing entire phrases given the fact that we'll already have stuff like contexts and all the like.

The idea is indeed huge, but depends on how we want to implement it. If we only want to translate the abbrevs in the sentence, then we already have a solution (the prototype I worked on). But, if we want more than that (i.e the translated sentence should make sense), then we need more data (i.e context for each abbrev).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants