Easyling Release Notes August, 2023

Why did the computer go on holiday in August? It needed a byte of summer! So did our developers, so there are a bit fewer notes this time. The two highlights are improvements of our JavaScript-based translation engine and that we added more details to our reports submitted to Google Analytics. Read the full article for the details.

JavaScript-based translation engine

Three key improvements were added this month.

The main one is page exclusions. Up until now, if a page was out of scope, the solution was to simply not add the translator script to those pages. However, depending on the CMS the original website uses, that may not be possible. Some of them only allow you to add a script to every page. With this month’s update, it is possible to exclude pages even if the translator script is added to them.

Note: Unless the SEO add-on is purchased, only prefix-based exclusions are currently supported.

These days, websites are almost always optimised for both mobile and desktop. Sometimes, that means two completely different versions. We updated the language selector to allow it to exist multiple times in the multiple versions of the website that are displayed depending on the screen size. To set it up, enter a CSS selector, such as .lang-selector or .lang-selector, .lang-selector-mobile instead of the class name on the Dashboard.

Finally, we fixed an edge-case where Google Translate was capable of interfering with our translations. This way, it’s now possible to handle some target languages through Easyling while others via Google Translate.

Google Analytics

Proxy traffic can be reported to Google Analytics, so that the tools provided can be used for further analysis. We added the following two new fields to the data we submit.:

• page_location: This field will contain the page where the request was made.
• ip_address: The IP address of the user who made the request.

Workbench

We fixed a problem that caused the pre-translate dialog in the Workbench to fail because the list of segments to be translated wasn’t loaded correctly.