Read this answer in context □ 2 All Replies (16) I tested in on the bild article and it worked for me (screenshot attached), although I admit I'm blocking a lot of content in that page, so if our blocking strategies are different, the result also could be different. Mozilla recently blocked/removed a number of these extensions due to a new policy that doesn't allow extensions to inject external scripts - all scripts need to be included with the extension to be approved.Ī partial workaround for the block is to user one of the userscript extensions (Tampermonkey or Violentmonkey) and a userscript to inject Google's script. The widget script was released for website authors to add translation to their own pages, but you actually can inject it into any site that doesn't block external Google scripts. (3) Insert the Google Translate Widget to translate the page "in place" But this should work as long as the API key is valid. This may require a paid developer account with Google, so I don't know if it is used in free extensions. (2) Use an official Google Translate API to translate the page "in place" I think that might be what is happening in your first screenshot. Google will attempt to independently retrieve the page and translate it. (1) Send the URL of the page to Google Translate (leave the page or open a new tab) Hi Gad Feldan, I'm not sure about the extensions you've tried, but there are three possible strategies:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |