Re: Dynamic or static translation for Website content?

[Konstantin Savenkov]

Hi Greg,

Since Google put its Website Translator Widget down some time ago (albeit resumed the support for COVID-related projects in May), we solved the task in the following way:

1. JS widget that translates the website content on the fly (see example at https://inten.to, the button in the top-right corner).

2. Temporary caching the results to reduce costs for re-translations (makes sense only for high-volume pages).

Regarding the terminology, please note it does not support infections, meaning when translated to Spanish you may find some inconsistencies. Overall, glossaries are good for proper nouns and acronyms, while domain-specific terminology is better to be learned from past translations.

However, customized AutoML is four times more expensive than stock Google Translate, so it depends on how much better the translation is.

cheers,

Konstantin Savenkov.

On Thursday, September 10, 2020 at 6:21:13 AM UTC-7 Greg Molnar wrote:

Hello

I had a conversation with Texas A&M University Forest Service yesterday and they are looking at the translate API to manage having site content in English in Spanish (initially).  They were wondering what the best practice is to dynamically translate HTML content on the fly or maintain translates versions of the pages.  I was hoping this group had some insights on the trends that could be shared.

They do have a second question on the best approach for forestry specific terms and I assumed the glossary functionality would be best for this but suggested they start testing with some sample content to understand how the base models work for them.

Thanks

Greg

[Greg Molnar]

Hello

What is the source of the JS widget used in the example?

[Konstantin Savenkov]

Hi Greg,

It is not open-source. It's a proprietary software code that works with Google Translate API via our middleware, MT Hub. 

Not directly, because you probably don't want your Google API key posted in browser, so it requires some back-end support with CSRF protection etc.

cheers,

Konstantin.