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

Defining which translator to use from the CLI #53

Closed
yyy33 opened this issue May 5, 2022 · 6 comments
Closed

Defining which translator to use from the CLI #53

yyy33 opened this issue May 5, 2022 · 6 comments

Comments

@yyy33
Copy link

yyy33 commented May 5, 2022

Can you support the command line

@ZhymabekRoman
Copy link
Contributor

@yyy33, What do you mean exactly?

@Animenosekai
Copy link
Owner

@yyy33
Copy link
Author

yyy33 commented May 6, 2022

@yyy33 It already supports command line access :

Animenosekai/translate - README - In other applications/from the terminal

Animenosekai/translate - README - Interactive Shell (REPL)

Sorry my text was swallowed Can you support to specify what translation service to use on the command line instead of the default Google

@Animenosekai
Copy link
Owner

Sorry my text was swallowed Can you support to specify what translation service to use on the command line instead of the default Google

Oh yea my bad.

So basically it doesn't use Google by default but the Translator class, which uses different translators at once.

I planned on doing something to be able to specify the translation service but forgot about it.

@Animenosekai Animenosekai reopened this May 6, 2022
@Animenosekai Animenosekai changed the title about shell command Defining which translator to use from the CLI May 6, 2022
@Animenosekai
Copy link
Owner

Animenosekai commented May 28, 2022

I'm currently coding a way of getting a translator from a string (its name or module location).

Currently at the step of translating the different aliases for the translators (~ 4500 translations), we are soon going to see if this works 👍

@Animenosekai
Copy link
Owner

440e0cb should fix your issue ✨

@Animenosekai Animenosekai mentioned this issue Feb 23, 2023
27 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants