Easyling Release Notes – 2015 March

March passed without much in the way of March Madness, so we had plenty of time to add newer and newer features to Easyling to ease your life and work. One such feature is the ability to create reports on work packages present in Easyling. But that’s just the tip of the iceberg: while we do not replace whitespaces at the end of segments, we do give you a warning if there’s a difference between the source and the target. Further, we can now handle multiple content overrides, our white label partners will be pleased to know they can hide the account details (useful for presentations), we now translate the “onClick” attribute with javascript as its value, and we now have a filter to select entries at a certain confidence levels after a TM-application. See the full briefings after the break!

First off, the simplest new feature: hiding the subscription details. When you’re pushing Easyling under your own brand name, it may not be a good idea to show the subscription details on the Dashboard (depending on your sales pitch). Now, there’s a new checkbox in the Account settings menu, which can be used to hide this box. That way, you can truly present Easyling as your own product.


Check this box on the Account page to hide your subscription details – useful if you’re using our whitelabeling feature to sell Easyling under your own brand.

You can also create Excel reports on a given work package set that shows completion status (after re-importing, of course), as well as word counts. To recap, a “Work package” is a unique export that can be sliced according to word counts, and is exported in an easy-to-track format that can be used to spread the load among multiple translators without further processing. With the click of a button, you can also generate an Excel report that lists the pages included in the Work Package export, and the ratio of translated segments to all, useful for tracking the completion of your projects.

If the warning icon appears in the lower right corner, the leading/trailing whitespaces on the segment do not mach the source. You may have to double-check to prevent nasty layout surprises.

The Page Content Override feature has received an upgrade as well: now it can store multiple overrides for multiple paths, where you were limited to one only. This can be used to override multiple parts of the site. To recap this feature as well, the Page Content Override feature takes a path on the remote server, and overrides its content with the entered code, whether it actually exists or not on the original server. Thus, this can be used to provide completely different content in translation, or even to create completely new pages from scratch. These “virtual” pages are also added as translatable pages, with the text content being parsed as a real page would be, so the virtual page can have translations in multiple target languages. Previously, users were limited to a single path on a project, but this restriction has been sidestepped, and now any number of overrides can be defined.


You are no longer limited to overriding one specific page, you can recreate as many as you want in our proxy tool!

The Advanced Settings received a new tweak as well: the ability to translate the contents of the so-called “onClick” attribute (this attribute defines how the element should behave when clicked) even if it has plain JavaScript code as its value. This can be useful in cases where the JavaScript in the attribute contains translatable text or a URL that needs to be mapped to the proxied domain. If this happens, just run the JS Path Tester tool after checking this box, and Easyling will include the onClick attribute in the analysis, then offer its contents for translation (should you choose to).


Translating the onClick JavaScript attribute on certain elements may come in handy during the setup phase of certain sites.

Finally, the Workbench received an upgrade too: a new filter was introduced allowing users to filter for segments of a given confidence level. As you may remember, after applying an Easyling Translation Memory, each segment translated from memory is assigned a confidence score, from 102% down to the threshold you set when starting the pre-translation. Enabling this filter will let you see only segments of a given confidence level for instance, 98% (chosen as the example because this level of match may or may not require reviewing, as the tags may not be matched properly to the source). You can find this filter along with the others, on the Workbench, but you should take care to disable showing other segments, lest your view be polluted with entries you are not interested in.


You can filter for only segments that have been translated via machine translation (or at a specific confidence level), useful for running post-application sanity checks.

Dedicated demo for You