Prioritizing to 1.2 so it is not forgotten. If we can't implement ANY translator by then, we should assign to a future milestone, but this is a feature which will be missed by a fair percentage of users.
+1 from community for non-Google translator
https://community.brave.com/t/non-google-translator/7435/2
+1 from @briannyeko via https://github.com/brave/browser-laptop/issues/10949
Any news of this? This would really make Brave much more viable for me as my main browser if you were able to implement it.
Sorry if I'm posting in the wrong place!
Any news on this?
Is this going to be fixed by fork? @bbondy @bsclifton
@srirambv Brave Core won't fix this immediately- we'd need to do some additional integration. I think it's safe to say that any development would happen in Brave Core and not browser-laptop
Closing in favor of https://github.com/brave/brave-browser/issues/208
Most helpful comment
Prioritizing to 1.2 so it is not forgotten. If we can't implement ANY translator by then, we should assign to a future milestone, but this is a feature which will be missed by a fair percentage of users.