Easyling Release Notes October, 2020

This month was mostly business as usual. Well, as close to that as possible during the pandemic. We integrated a new machine translation engine, Systran. Additionally, you can now specify project-level MT credentials as well as prevent the use of credentials associated with your account. Read the full article for the details!

Systran integration

We are happy to report that the newest addition to our list of supported MT engines is Systran. This engine uses AI translation models and covers more than 50 different languages with in-domain specialisation. Their data centres, which were created with their environmental impact in mind, are hosted in each main customer region and are all fully GDPR compliant. These qualities make Systran a great option for a small startup as well as the Department of Defense (DoD) of the United States and anything in between.

To get started, just enter your API key to the Dashboard 2.0 and enable the engine. With that in place, you can use Systran just like any other engine, both for suggestions in the Workbench and translation of pages through pre-translation.

Additional MT improvements

While working on the Systran integration, we also improved the options to control which API keys are used. As you are probably aware, you can enter MT credentials both in your account settings and in your project settings. The place you enter them determines their availability. If you add a Google Translate key to one of your projects, it will only be available on that one while adding a Systran key to your account makes it available on all of your projects.

Until now, if a project-level key was available, it was assumed that that’s the one to use. With this update, both your account-level and project-level credentials are available for use and you can select either. By default, the project-level credential is used. You can also prevent the use of your account-level key(s) on a specific project by selecting Disable fallback to account level credentials.

Smaller improvements

Like usual, we made some smaller changes that are worth mentioning.

• We added a new filter to the Pages list for checking which resources changed recently. This will facilitate change detection on them or your can use it to quickly find the new image that recently changed and replace it.

• JavaScript and CSS injection rules added to Path Prefix Overrides have a limit of 1kb in size. The user interface now lets you know when you entered too much. This way it doesn’t just get cut off at the point where it’s too long.

• A new query parameter, aspxerrorpath, is now added to the Ignore queries list of new projects. This query is passed if an error was caught by the .NET framework. As the query doesn’t change the content of the website, it is safe to ignore in the proxy.

• A new option, Do not recrawl existing resources, was added to the Crawl wizard. Resources rarely change so it’s not necessary to crawl them as often as you crawl pages so you can enable this feature to skip them. Not only will this make your crawls shorter, it will also save you money as it won’t make as many requests.