Easyling release notes January, 2026

January was a particularly productive for us. The key focus was on ensuring only the right content is ingested. In addition to that, we added new options for specifying the source of the translation even if it is imported through an XLIFF file. Read the full article for the details

Crest ingest filters

Our JavaScript-based translation engine, Crest, allows for highly efficient translation directly in the web browser. One of its main advantages is that it can translate everything that’s visible in the browser, even if it is dynamic content without the additional configuration that the proxy solution would require.
This advantage, however, can be a drawback too when it comes to ingesting new content. When configured to do so, Easyling can gather content that it has no translations for and add it to the Workbench. This can result in a situation where content that’s not intended to be part of the website, like the output of AI extensions, can be ingested as source content.
When this happens on the translated websites, these can be filtered out with our new development. For example, if the source site is in English, and it is translated to Japanese, the alphabet is different. This way, we can ensure that the Japanese content is not ingested. This has two key benefits:

1. Lower cognitive load on reviewers: When human reviewers edit content, they will not see translated content as source, so what they see is what they truly need to review.
2. Lower total word count: For subscriptions based on the word count of the site, this can avoid wasting words as they aren’t ingested.

Import XLIFFs as MT

While Easyling supports many machine translator engines and large language models, we found that in some workflows, working with machine translation is beneficial in external tools. This could always be accommodated through XLIFF exports that can be processed in the preferred tools. However, up until now, when content was translated through XLIFFs, those would be marked as human translations. Based on feedback from our power users, we added an option to import content from XLIFF files as MT. So, if you use machine translators to process your XLIFFs, you can still mark the segments as MT, ensuring that they are in the correct workflow.

Note that we’re always excited to hear about your feedback and new feature requests. If you have any ideas, please email us at support@easyling.com.

Don’t externalise resources

We have options for custom behaviour when URLs, both HTML pages and resources, are externalised. You can specify redirects to the original site, for example. We found that in some cases, this can cause issues, especially in conjunction with the Handle unknown pages as externalised option. The following scenario can happen:

1. A given JavaScript file is not in the Resources list, so it is unknown,
2. The project is set to redirect externalised pages to the source website,
3. Handle unknown pages as externalised is turned on.

In this case, we have an “unknown” JS, which is treated as externalsied, so it is redirected. However, the original site may be on a different domain, resulting in a cross-origin request, leading to errors.

To avoid this scenario, we now only apply these actions, like redirection to HTML pages. Resources are unaffected. This ensures that your translated sites continue to function even with this combination of settings enabled.

Miscellaneous

As usual, we have a few smaller, but nonetheless very cool improvements:

• We improved the caching for JavaScript translation to ensure even faster loading times and also increasing the efficiency on our side.
• As we’re working on modernising the Workbench, we updated the icons throughout the interface.
• We fixed a bug in JavaScript translation relating to slot element. They should now work as expected.