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

Translate-Now: Ability to use a second translator engine for full page translations #153

Open
SuperPat45 opened this issue Oct 7, 2018 · 1 comment

Comments

@SuperPat45
Copy link

SuperPat45 commented Oct 7, 2018

I use Translate-Now with the DeepL because it offer the best translations.

As it does not currently support translating a full page, when you click on the extension icon, it open the DeppL page with the URL inside the textarea and we don't have the "Translate page" item in the main context menu.

It will bu useful to have ability to select google as a second translator engine for full page translation in this case (and eventually when source language is unsupported by DeepL according to the HTML tag of pages).

@Smile4ever
Copy link
Owner

I've thought about it, and this is something I would like to implement.

Just a list of translation engines, that you can reorder according to your preferences. Would be cool to have for certain.

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

2 participants