Easyling release notes August, 2025

Sunny August est venu et est allé si vite que je l'ai à peine remarqué. Cela s'est probablement produit parce que nous avons été très productifs avec des correctifs à Easyling. Nous avons amélioré le sélecteur de langue que nous fournissons et corrigé plusieurs bugs sur notre backend. Lire l'article complet pour les détails ci-dessous le pli

Sélecteur de langue

Over the years, we developed multiple different variations of language selector. These are designed to slot into most websites as seamlessly as possible. We offer a sidebar and multiple dropdowns. Our latest iteration of the dropdown design, v3, allows for more styling configuration than ever before.

Notably, it allows you to select the icons it uses. For example, you can specify what kind of downward pointing arrow (if any) you prefer to signify that the selector is a dropdown, not just the name of the currently selected language. As part of our standard process, when building this, we ensured that it works great on Google Chrome. However, we later noticed that they aren’t visible in Firefox and Safari because those browser engines handle custom characters slightly differently. We adjusted our implementation to account for this, so this variant now works identically across the different browser engines, ensuring a consistent user experience.

Note that we officially only support Google Chrome for the Dashboard and components we provide. Support for other browsers is provided on a best-effort basis. Luckily the best effort usually means that it’ll just work.

JS parser improvement

As the JavaScript language evolves, so do scripts that developers create. With the Translation proxy publishing mode, JavaScript files may need to be separately processed via the JSON path tester tool if they contain translatable content. This month, we improved this system to work better on particularly long lines of code.

This is most beneficial for minified files where the formatting of the JS code (spaces and new lines) is removed and all of it is just one line.

New projects automatically take advantage of our new parser. On older projects, we recommend not changing it because doing so will break existing paths that were specified. However, if you do find a JavaScript file that you need to process that is too long, just let us know at support@easyling.com, and we’ll be happy to activate the new parser for you, allowing you to process it.

Consistent Pattern matching

Pattern matching is one of the most used sections on Advanced settings. In a nutshell, it allows you to group similar segments based on regular expressions. For example, if you have blog posts written by multiple authors on your site, you may have segments, like “Author: Alice”, “Author: Bob” and “Author: Charlie”. By default, that’s six words that count towards your word count limit. However, with Pattern matching, you can specify a regular expression, like Author(.*) to make : Alice, : Bob and : Charlie translation invariants. Names stay the same anyway in the target language. With that, you’ll end up with just one word to translate: Author. The savings can add up to be huge if you have hundreds of posts.

The backend of Easyling is developed in the Java programming language, so with the Translation proxy publishing mode, the regular expression you enter here must be compatible with Java. With the introduction of Crest, our JavaScript-based publishing mode, the system got a bit more complicated. Due to its technology, Crest requires JavaScript regular expressions. While similar, Java and JavaScript regular expressions aren’t exactly the same. This posed issues when changing the publishing mode of a project or when you work with multiple projects, some with Translation proxy, others with Crest. We found ourselves adding Java regular expressions on JS projects and vice versa.

To combat this, we previously introduced a compatibility layer. With Crest, the Java regular expressions are transparently converted to equivalent JavaScript ones. Unfortunately this is not a straightforward task. This month, we refined our algorithm to ensure more regular expressions work appropriately. We’ve tested extensively with common regex patterns. At this time, we’re not aware of edge cases where the results would be unexpected. If you do encounter something strange, please email us at support@easyling.com.

Divers

As usual, we have a couple of smaller improvements.

• We fixed a bug where changing the type of a specific Path prefix override from exact path to prefix would save incorrect values (and wreak havoc as a result).
• We refreshed the XTM API integration based on new WSDL files. This ensures it continues to work in conjunction with the updates the XTM team makes.