Erick Posted February 3, 2021 Share Posted February 3, 2021 (edited) Hi Pals, I don't know if somebody notice the web-search translate function it doesn't work. Well, in my case on Catalina the url translate function return a error, well, for that, I share with you a way to fix it with a own websearch function. You can add a custom search with the next parameters: Search URL: https://translate.google.com/?sl=en&tl=es&text={query} // this is the new url where translate english to spanish Title: any text Keyword: your keyword to enable the translation And save. Now when enable your search and write you keyword is possible to get the translation. PD: you can add all the web search function you want, in my case I have two for each translation. Search URL: https://translate.google.com/?sl=es&tl=en&text={query} // this is the new url where translate spanish to english Title: any text Keyword: tse Search URL: https://translate.google.com/?sl=en&tl=es&text={query} // this is the new url where translate english to spanish Title: any text Keyword: tes Edited February 3, 2021 by Erick Link to comment Share on other sites More sharing options...
Vero Posted February 4, 2021 Share Posted February 4, 2021 @Erick Out of curiosity, which version of Alfred are you using and what error are you seeing? The translate default web search seems to work fine but I'd be interested to hear if anyone has issues with it. Cheers, Vero Link to comment Share on other sites More sharing options...
marlun Posted February 4, 2021 Share Posted February 4, 2021 I'm seeing the same thing on Alfred 4.3.1 on Big Sur 11.1: Link to comment Share on other sites More sharing options...
pawelgrzybek Posted February 5, 2021 Share Posted February 5, 2021 I experienced the same issue and I know the solution. This is what Alfred currently does: https://www.google.com/translate_t?text=elephant And this is what it should do: https://translate.google.co.uk/?text=elephant Looks like Google changed the URL and query params schema. Should be a quick fix on your end :) Thanks 🐘💨 Link to comment Share on other sites More sharing options...
marlun Posted February 5, 2021 Share Posted February 5, 2021 I agree, except using the UK domain by default Changing to a translate subdomin and removing /translate_t seem to work. pawelgrzybek 1 Link to comment Share on other sites More sharing options...
Andrew Posted February 5, 2021 Share Posted February 5, 2021 I'll get this fixed up for a pre-release build today pawelgrzybek 1 Link to comment Share on other sites More sharing options...
Andrew Posted February 5, 2021 Share Posted February 5, 2021 This fix is now available in the 4.3.2 b1216 pre-release, available from Alfred's update prefs. Link to comment Share on other sites More sharing options...
marlun Posted February 6, 2021 Share Posted February 6, 2021 Works great after updating, thanks Andrew! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now