Easyling Release Notes - 2014 September

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. See the full list after the jump!

In the past month, the rollout of the Auditing Log has finished. Available for project owners from under the Dashboard, this log shows every project event that has occurred, such as the addition/removal of target languages, new users being added or removed, XLIFF exports and imports, scans and wordcounts, and many more. Due to the data collection scheme, we only have data available from September 15, even for already-existing projects. In the future, expect further events to be added to the auditing log’s display.

[caption id=“attachment_1402” align=“aligncenter” width=“960”] The Audit log displaying user actions[/caption]

The Workbench also received a round of optimizations, so now performance is better than ever, and scrolling is noticeably smoother, even when many thousands of segments are loaded into memory for display.

Our JavaScript parser also received an upgrade, and it is now capable of extracting HTML content as well. Previously, the parser was limited to plaintext content, stored in variables and function parameters, but now, we are also capable of extracting HTML markup from the JavaScript, should it be contained there, and load it into the database for export and translation. This ability is part of the parser, and relies on content being marked appropriately in the search path by appending the contained type (html or plaintext) to the search path specification line.

[caption id=“attachment_1420” align=“aligncenter” width=“978”] By entering “html” after the search path, discovered JSONs will be treated as html pages, and their content will be extracted for translation, without any interfering JavaScript structures[/caption]

We also created a new feature that enables users to exclude individual segments from translation (not to be confused with the ability to lock segments to prevent changes). Externalized segments do not appear in XLIFF exports, and are not shown by default on the Workbench (even when they are shown, they are not editable). This comes hand-in-hand with a change on the Workbench, renaming the previous “Mass-confirm” button to “Bulk Actions”, as it now houses not only mass confirmation, but exclusion (or inclusion) of entries as well.

[caption id=“attachment_1400” align=“aligncenter” width=“1920”] Externalized entries in the Workbench, for fine-grained control over your translations[/caption]

[caption id=“attachment_1421” align=“aligncenter” width=“969”] The Customer can visit the Management View to decide upon the fate of pending segments[/caption]

[caption id=“attachment_1422” align=“aligncenter” width=“1920”] Pending source segments can either be externalized o approved for translation using the Bulk Actions[/caption]

[caption id=“attachment_1423” align=“aligncenter” width=“1920”] Other users can view the pending and/or externalized segments by setting the appropriate filters[/caption]

We’re also adding the ability to define a default state for new segments to be added in the future (either via scan or viewing a page through the proxy): new entries may be added as “Externalized” (not shown in exports, not shown for translation), “Pending” (to be decided upon later, but otherwise accessible), or “Approved” (the segment has been approved for translation, thus it will be shown in exports and the Workbench, letting the linguists do their thing). This default setting is available in the Advanced Settings menu, defaulting to “Approved”.

[caption id=“attachment_1401” align=“aligncenter” width=“966”] Default state of new entries upon adding[/caption]

Lastly, we have completed our migration to the HTTPS protocol - we have now created a secure channel across the entire interface, with eavesdropping being (almost) impossible even when editing.