The Google Translate widget we implemented is deprecated set to be shut down on September 20th.
I chatted with one of the developers at UT Austin and they shared the use the GTranslate module to add this functionality to sites. This module has no added costs for the translation functionality.
His comments:
We have some sites that use the Drupal "GTranslate" module I think we've discussed that particular module here before. It's kind of problematic, in my view.
You can see it in action in the header of this site: https://hr.utexas.edu/
The module is a "freebie" version of a vendor product that uses the Google Translate API. In the past, there have been issues getting the single person who maintains the module to keep it updated and to use Drupal best practices.
The Gtranslate module does some trickery that somehow keeps the URL of the site the same while performing the translation, which is a feature that the stakeholders on the team that chose it preferred. When you use the widget as a standalone, the URL gets transformed to a Google Translate URL.
The Google Translate widget we implemented is deprecated set to be shut down on September 20th.
I chatted with one of the developers at UT Austin and they shared the use the GTranslate module to add this functionality to sites. This module has no added costs for the translation functionality.
His comments: