Vlad I respect that. However, nothing prevents you to let the final user chose wether he/she wants to send personal information to a 3rd party.
If you really care about privacy, setting Apple Translation API as a default while proposing other services (e.g.: Bing Translate, Amazon Translate or Google Translate) may be a great idea. Ultimately, you let the advised user make his choice while offering a privacy-respecting solution to neophytes.
crnd99 Apple translation API is not avaialble yet. Orion prides in being a zero telemetry browser and last thing we want is accidentaly send uninformed users' private information to big-tech.
A tech savvy/advised user can already use a bookmarklet for translation with any external service (I currently personally use it). It is very simple to use. Is there any reason why you are against this idea? We could perhaps include some ready-made bookmarklets.
Vlad
Yeah, I got that right.
I share your take on the zero-telemetry policy, that's exactly why I suggested that -when available- the Apple Translation API should be set by default as the browser's translation engine.
But why not implementing (alongside the Apple Translation API) others translation providers such as Google, Amazon or Bing? After all you've already done it for search engines. They just need to be clearly identified as "serverside powered engines".
I am not against the bookmarklet trick but it still remains a workaround rather than a handy and simple solution to translate a webpage. This has nothing to do with a one-click translation tool (such as Edge's one).
crnd99 In my mind server side translation would work same as the bookmarklet. Meaning loading the page in the external service like Google translate?
Did you have in mind perhaps in-page translate? That would mean contacting the API directly, and these APIs are not free. In this case we would need to pass the cost to the user somehow?
I definitely second the need for native translate, but wanted to add the opinion/input of another user here.
As a consumer, I like the fact that Orion takes a hard stance on 0-telemetry. It's unfortunate, but we need products today that will protect the user from themselves. A "regular" user who installs Orion because they like the privacy features could inadvertently circumvent those same measures by making configuration changes without understanding the true implications. At that point, Orion has failed in its goal to make the internet safer for the user. If clicking a single bookmarklet to translate a page (which takes the user to an external page making it obvious you're sending information to Google) is too cumbersome for the user, maybe the user needs to explore a different browser with more relaxed controls and is out of beta.
Just my perspective. Orian can't make the hard claim for user privacy if it makes it too easy to circumvent that privacy. Offering the path for data leak in one area just implies that there will be others. The hard stance on 0 telemetry gives me confidence in the product.
I was thinking after the pdf.js got introduced, that maybe this could help
https://github.com/mozilla/firefox-translations
I have no experience with it, so idk if its any good, or if it can be used. I just read that it translates the web locally without using the cloud
osdiab Since can TWP works on Orion, and I must say that on chrome and Firefox it is the best translation extension in the world
https://github.com/FilipePS/Traduzir-paginas-web/releases
For having tried all other solutions, native or extensions of all browsers. None will do the job as well as this one. Really!
It translates what is displayed on the screen and not the whole page at once, which means that when I'm in the middle of the page and I translate I don't have the page falling off too much and it's incredibly faster than safari's translation because it only translates what is necessary.
Also it is possible to exclude <pre> tags. The page tracking is good. Etc... Incredible!
I don't think we should waste time implementing anything else. Just properly support this extension which is perfect.
Brief Summary
I can't find a built in translate page function that is found in chrome/safari, I use this often, can this be added? Thanks.
<What does your feature entail? What is it for? How will it affect existing workflows or user experience?>
Details:
<What are the exact ways that you see a user using your proposed feature? Please go into as much detail as possible, and provide examples of how other browsers/apps implement this feature, if applicable. If your feature suggestion adds on to an existing feature, how would it work into it to extend its usefulness?>
Image/Video:
<Copy/paste or drag and drop to upload images or videos (up to 20MB)>
There are number of translation extensions you can use that work with Orion like
https://chrome.google.com/webstore/detail/mate-translate-–-translat/ihmgiclibbndffejedjimfjmfoabpcke
https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/
Or you cna have a simple google translate bookmarklet http://7is7.com/software/bookmarklets/translate.html
We are waiting for Apple to make the on-device translation API available to include this in Orion.
We are waiting for Apple to allow us access to the built in Translation API in the macOS. This is the most privacy respecting and the most efficient way to get translations in the browser.
In the meantime there is a new project which does local translations in the browser
They have a firefox extensions and it works great in Orion. No 3rd party services are used for translation and it works even offline.
https://addons.mozilla.org/en-US/firefox/addon/translatelocally-for-firefox/
nevermind, got it to work now on some sites
Vlad Initial testing with this is quite good, thank you. With this, I am going to swap back to Orion full time. The reason I went back to Safari was for native translation. I have noticed that Microsoft Outlook for Mac can use the Apple native translation now, so I am hoping Orion can use this soon? I genuinely have no idea how Apple and their API's work in relation to software development, but in the last of 18 months of Apple updates in iOS and MacOS, the native translation functions have both improved and are available more often when using them.
