- Edited
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).