126

ViktorVoronin Google Translation API requires a token that you use in your application. All usage beyond the free tier would be charged to the owner of the token, which would be us.

https://cloud.google.com/translate/

What does make sense is to simply use a translation extension. We will be happy to include a native translation feature, once it is available in macOS.

    Vlad I'm not sure if you don't read my posts or I'm a terrible communicator. 😬

    There are endpoints that don't require an API token. Here is a demo for you:

    const googleTranslate = (text, langTo, langFrom = "auto") => {
      return fetch(
          `https://translate.googleapis.com/translate_a/single?` +
          `client=gtx&dt=t&sl=${langFrom}&tl=${langTo}&q=${encodeURIComponent(text)}`
        )
        .then(res => res.json())
        .then(data => data[0][0][0])
    }
    
    const input = window.prompt("Enter text to translate to Russian:")
    
    googleTranslate(input, langTo = "ru").then(translated =>
      alert(`"${input}"\nin Russian would be:\n"${translated}".`)
    )
    • Vlad replied to this.
      6 days later

      ViktorVoronin Hm.. can you point out this API in the Google translate official API doc? We wouldn't want to implement an official API theat can be shut down ant any moment.

        21 days later

        optuma Thanks for this. I tried Vivaldi translation and it is not native nor private. You can easily test this by disabling your wifi and trying to translate a page - it will not work. It requires to send data to Vivaldi servers for translation (where is then processed by hosted Lingvanex software). So when Vivaldi says that it is "private by design", take it with a grain of salt.

        We will include translation when one is available on macOS (so that it is truly native and private). Until then translation can be achieved using one of the many web extensions.

        10 days later

        Safari has a built in translation of webpages feature. It works well but it can not remember you were there and will not translate automatically. I would like to see Orion browser have one and be better than Safari. Otherwise your browser is awesome.

        Thanks,

        CucumberJam

        It seems that Monterey added a native translation feature, we can definitely use that.

        Merged 17 posts from Native web page translation.
          10 days later
          7 months later

          In the meantime does anyone have a suggestion for a translation extension that actually works for translating full webpages?

            Google translate should work

              a month later

              +1 for translation. Looking forward to this feature. Would probably be more useful on mobile for me, though.

                Can you add built-in translate such as safari when you highlight text and press right click will find translate option as per the attachment + It's better to add built in translate for web pages like google chrome.


                • Vlad replied to this.

                  Bander Use one post per issue. Removed the second part.

                    Vlad changed the title to Built in translate .
                      2 months later
                      Merged 3 posts from Built in translate.
                        a month later

                        Hi guys, just want to bump this one up rather than create a new one. I'm still an MS Edge user because of the automatic translation (and not having nested tabs). After reading the comments here, and doing a bit of research, I'm pretty sure there's a way to make this happen in a way that won't be costing you (or us) too much, both in terms of money and privacy.

                        Auto-translation is a very important feature, especially as it opens up access to a huge amount of information that would otherwise require extra steps.

                        Having auto translation is an extremely important solution to provide, whether it's through the browser, in messages, in glasses, or a babelfish inserted into the ear. It removes the barriers in communication and enables humanity to communicate and understand each other much better

                        • Vlad replied to this.

                          John macOS has a translation API that we can use once it is publicly avaialbly. Until then all translation solutions would be external meaning data would need to be sent somewhere (like Edge is doing). We want to avoid this and recommend people use a translation extension instead if they are comfortable with their data being sent elsewhere.

                            Automatic translation is a very important feature in this globally connected world, especially as it opens up access to a huge amount of information that would otherwise require quite a few extra steps, or to just ignore it because you can't read it.

                            Having auto translation is an extremely important feature, whether it's through the browser, in messages, in glasses, or a babelfish inserted into the ear. It further removes our barriers by enabling humanity to communicate and understand each other far better.

                            I'm still an MS Edge user because of the way they implement automatic translation (and not having nested tabs). After reading the comments here, and doing a bit of research, I'm quite sure there's a way to make this happen in a way that won't be costing you (or us) too much, in terms of both money and privacy.

                            And, again, thank you for a great browser with a 'lot' of potential. I really want this to be the best Mac browser

                              John changed the title to Automatic Translation of websites .