Easyling Release Notes August, 2020

It’s the end of summer. It was a bit strange with the pandemic going on. This month, we migrated the Import feature to the Dashboard 2.0 and added the menu to configure the MemoQ integration. We also significantly improved the support for JavaScript translation. Read the full article for the details!

Import

This section is fairly self-explanatory. You exported content to XLIFF and processed it. Now you need to import it and with this update, you can finally do that through the Dashboard 2.0!

The new Import menu offers the same functionality as the old one but with our new design language and usability standards.

MemoQ integration

Just like with import, this section was moved to the Dashboard 2.0. Step by step, we are getting closer to our goal of fully modernising Easyling.

As the Dashboard 2.0 is based on new technology that encourages code re-use, creating this section will facilitate the addition of new integrations in the future.

JavaScript translation

The proxy can pick up content from HTML pages automatically due to their mostly fixed and well-defined structure. JavaScript, however, isn’t nearly as structured. Despite that, it may still contain segments that need translation. For this reason, we have the JS/JSON/XML processing section. Here, you can mark the strings that need to be translated in scripts, JSONs and even XMLs (but I don’t think I ever needed to use the latter).

JavaScript, however, is constantly evolving and our algorithms in place for processing them were a bit old. As such, JS had many new features that we didn’t yet support. With the new, Shift AST-based system in place, we now have full support for ECMAScript 6, the second main revision of JavaScript. What this means in layman’s terms is that virtually everything is supported.

Note that to ensure compatibility, we didn’t enable the new algorithm on old projects. If you want to have your project migrated to it, please drop us a line at support@easyling.com.

Proxy loop detection

Sometimes, usually with incorrect reverse proxy settings in place, the proxy is instructed to send requests to itself, creating a loop. As Easyling is running on Google’s AppEngine infrastructure that can scale to extreme sizes, this can be really bad. Such a loop loop can cause hundreds of thousands of requests in very little time which can cost an arm and a leg. To prevent this, the proxy can now detect if the request is coming from itself and will simply reply with 410 GONE instead of processing the request. As such, the request loop is broken almost immediately and no resources are wasted.

Smaller improvements

Naturally, this month, we added some smaller changes as well:

• We improved the formatting of CSV page list exports so that they are easier to process by machine while being just as human-readable as before. Note that if human-readability is paramount and the project is small enough, we recommend XLS exports.

• We fixed a bug in the white-space adjustment algorithm during the Pre-translation from TM process that caused empty text to be written as translation in a rare edge case. Unfortunately, the fix isn’t retroactive. Previously infected segments must be fixed manually.