![]() ![]() ![]() The two JavaScript files are obfuscated and minified. 2 JS files: main_de.js, element_main.js. ![]() Obviously it is a string dependent token, whose structure is not easy to see, but when you start the web page translation, the following files are loaded: We now retranslate this modified one within Google Chrome using the web page translation function and find that the parameter tk has changed as well as the parameter q (all other parameters have remained the same): ![]() Now that we have all the information we need to use this API outside of Google Chrome, if we change the string to be translated (data field q of the POST request) from, for example, "Hello World" to "Hello World ", we get an error message: If you reactivate the user agent (which generally doesn't do any harm), the API delivers UTF-8 encoded characters: After manually deselecting all headers, including those from the user agent, an encoding problem is discovered when entering special characters (here when translating " Hello World "): Some request headers are also set - but these can mostly be ignored. String format (important for translating HTML tags) The meaning of the URL parameters are also largely obvious:Īnnotation mode (affects the return format)Ĭlient information (varies, via the web interface of Google-Translate the value is "webapp" affects the return format and the rate limiting) If you do a translation, then catch the decisive POST request via "Copy > Copy as cURL (bash)" and execute it in a tool like Postman, for example, you can resend the request without any problems: but Chrome even delivers the requests it sends during page translation free of charge: they can be easily viewed via the Chrome DevTools: but what API does Google Chrome use internally to translate the content and can this API be accessed directly - even on the server side? to analyze network traffic, tools like Wireshark or Telerik Fiddler are recommended, which can also analyze encrypted traffic. When using the website translation function of Google Chrome, it is noticeable that pages can be translated here in very good quality without any noticeable limitation.Īpparently, the advanced nmt model is already used here. In addition, there is an undocumented API that can be used without a key, but which denies service after only a few requests. Please consult with a translator for accuracy if you are relying on the translation or are using this site for official business.As part of its Google Cloud, Google offers the Google Translation API with a usage-based cost structure. Google Translate™ is best viewed in Internet Explorer 9 or higher or in Google Chrome. Some files, forms, and other items cannot be translated including but not limited to forms, publications, graphical buttons, drop-down navigation, graphics, photos, and the search feature results. Governor will not accept liability for any loss or incurred as a result of the use of Google Translate™. Governor does not warrant or guarantee the accuracy, reliability, or timeliness of any translation provided by Google Translate™. The Office of the Lt. The web pages currently in English are the official source for information on the Office of Lt. Google Translate™ automatic translations cannot be guaranteed as exact or without the inclusion of incorrect or inappropriate language. The translations should not be considered exact and should only be used as a rough guide. The Google Translate™ feature is provided for informational purposes only. Google Translate™ is a free, automated service that relies on data and technology to provide its translations. The Office of Lieutenant Governor uses Google™ Translate to provide translation on most of the web pages on this website. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |