Easyling Release Notes June, 2023

Despite June being a pretty productive month for us, I’ll try to make the release notes pretty light so that they fit my carry on luggage. However, we can’t miss the highlights, like how the JavaScript translator engine’s built-in language selector can now be enabled or disabled without changing the embed code and how you can now have better control of which languages are shown. Refer to the complete article for the details.

Language selector

The language selector is an integral part of the localisation workflow. However, imagine a scenario where you successfully push a site live with the default configuration using the language selector we provide. Everything is perfect until the client decides that they want to add their own selector, one that matches their design better. This is getting out of hand. Now there are two of them! Previously, to eliminate one of the Sith lords, the embed script had to be edited: ?disableSelector=true had to be added. Now, you also have the option to toggle this on the Dashboard, so that you can act quicker in this scenario.

The system can now also handle deleted languages better. Previously, if you had a target language selected to be displayed and an export was available, it would show up no matter what. We updated this behaviour to respect deleted languages despite the fact that deleting the language doesn’t delete the export, so there is no technical reason why it shouldn’t be available.

Miscellaneous features and fixes

Keep it short, just a bullet point list:

• Classes ct_* and apbct_* are added to excluded HTML classes by default for new projects.
• We improved how link rel="alternate" tags are handled to avoid duplication. Previously, the source site would be added as well as the source language as an available translation.
• We clarified the wording on the XTM setup screen.
• We improved the Language selector settings on the Dashboard to better handle the differences between proxy and JavaScript publishing.
• Client-Side Translation now obeys page list / translation memory freeze as well.
• When advanced source or target filters are used during Work package generation, an intermediate package is created before the entries are filtered. We fixed a bug that caused the settings of the two packages not to match.