The new year rolled around in Budapest with champagne and fireworks, and so we returned to work from our end-of-year holidays, refreshed, and ready to bring you a plethora of new features and powers for Easyling. We have rolled out the ability to hold back segments from being published automatically to the live site, enhanced our JavaScript translation abilities, and we rolled out many new settings, tools, and tweaks into our Advanced Settings menu.
Christmas came and went, and with it, brought us many new and exciting features. Easyling can now preserve whitespaces in translations, letting users insert line breaks; Work Package generation can be restricted to certain paths and pages, in addition to the exclusion rules; we can now create Excel exports of the resources and pages lists (if there are so many of them that it would break your browser’s back); and uploaded Translation Memories can be searched, to see if they contain the proper content.
With the cold of November upon us, Easyling’s development slowed down somewhat, but we managed to churn out some interesting new features for our users. One of these is the new “Customer” role, enabling your customer to manage the segments by selecting what needs to be translated, another is the ability to restrict viewing of the proxied site using a username/password combination, and the ability to batch XLIFF uploads. See more after the jump!
October passed without much development on the interface front, the month was spent mostly on preparing the groundwork for a host of new features to materialize in November. However, we still managed to upgrade the Workbench to enable operations en masse, rework our work package generation interface, and we created a tool to query the status of the caches page-by-page. You can find a more detailed explanation after the break.
Yet another month has passed here in Budapest, and autumn has arrived with the cold weather allowing us to overclock our computers to churn out another new set of features, greater than anything before. Easyling now has an auditing log listing all project events in chronological order, the Workbench has received several optimization passes resulting in a noticeable speedup when many segments are involved, we added the ability to extract HTML snippets from JavaScript as well as the power to exclude individual segments, and we migrated to use HTTPS, creating a secure channel even for the editing interface.
August had a bit of a lull in activity, with our staff taking their well-deserved leaves, so this post is going to be a little bit shorter. But still, Easyling has gained some new abilities and some new fortifications against potential errors. Firstly, Easyling now handles the “data-src” attributes used by various CMS-s, resulting in their contents being handled as resources. If your site uses these attributes, a simple scan will now discover these as well, and extract their contents into the Resources tab.
With the heat of July bearing down on us, our office becomes more of a refuge than a workplace - without our new A/C systems, development would quickly grind to a halt due to heat strokes. But since we’re running those A/Cs on full blast, we can afford to keep rolling out new features and abilities for Easyling as fast as we can. Some of these new features include the ability to completely delete source segments via a regular expression, a new, advanced Discovery system, and with this, a new interface that provides more detailed statistics, as well as a more detailed CSV export, useful for tracking changes.
Another month has passed, and Easyling received several new capabilities, as well as an award during the LT-Innovate Summit in Brussels. The most important of these new capabilities is the new Translation Workbench, an upgrade of the existing List View, rewritten from the ground up along with the advanced _Translation Memory (TMX) _handling to support migration from other proxy solutions; but we also added the ability to define custom “ignore classes”, HTML classes which are exempted from being translated.