Easyling release notes July, 2024

Similarly to recent months, in July we focused on under-the-hood improvements. In the long term, we hope that this will result in even speedier processes, be it serving your websites or background tasks, like crawls, imports, or pre-translate processes. We also found and squished lots of bugs. Naturally, we also improved compatibility of the JavaScript translator engine. Read the full article for the details!

Browser extensions

To ensure that new content can be promptly detected whenever it is added to the site, the JavaScript translator engine can report new segments - anything that shows up on the website. Some browser extensions, however, can throw a wrench in the gears. They may provide additional features to websites, like a pop-up that shows a definition of the word or expression that you highlight. These may get detected as new content because it shows up on the website after all.

This month, we added additional protection against the most common such extensions in the Chrome and Firefox stores. These extensions include Grammarly and Dictionary Anywhere as well as multiple third-party translation extensions, like the ones below:

• Google Translate extension.
• Translate - Translator, Dictionary, TTS
• Translator - Select to Translate
• Simple Translate
• Translate (Yes, this extension is just called “Translate”. I’m serious.)

Database consistency

We added additional automated processes that look for inconsistencies in our systems to “heal” them. These inconsistencies can happen due to transient errors that prevent saving data. These errors are inevitable as Easyling is a highly distributed application. Unless a piece of data, like a new segment discovered, is saved to every server, it can not be considered a success. This would manifest in rare cases, where new content was discovered, but not saved successfully, resulting in potentially inconsistent word counts. The additional systems we added this month, will double-check the data and ensure consistency and fix them if needed. This makes our word counts even more robust than they were before.

Miscellaneous

Naturally, we had a few smaller fixes:

• The integration with XTM was updated following a change in their API.
• We watched as the world went up in flames due to CrowdStrike. We were unaffected.
• To speed up our systems, we updated some underlying components. This broke compatibility with websites that use non-standard cookies. We fixed this promptly.
• After importing multiple XLIFF files in a zip and checking Generate and publish JS export after import, we ensured that only one exported file is created as opposed to one for every XLIFF.