Real Control Over Your Structured Files
If your content lives in HTML and DITA, this release was built for you. The HTML filter now filters translatable content by attribute value, not just attribute name, so you decide exactly which parts of a file go out for translation. The full options are in the web page configuration guide.
DITA gets two improvements that work as a pair. A new whitespace compression option collapses runs of whitespace in extracted content into a single space, and DITA sections marked non-translatable are now excluded from extraction along with everything nested inside them. Both are documented in the DITA files guide. For documentation teams shipping large structured sets, that is less manual cleanup and far fewer surprises in the output, the kind of precision enterprise content operations depend on.
Stop Work From a Connected System, Instantly
Here is a favorite for anyone running an integration. A new connector endpoint lets an integrated external system cancel all jobs and tasks tied to a specific document workflow, with no one switching into Wordbee to do it. It covers Standard and Codyt projects across every active and completed status except archived, so when a content system pulls a page, it can stop the translation behind it and stop paying for work that no longer matters. It is exactly the kind of remote control developers want from a platform.
Notifications That Match What People Actually Do
Order notifications now follow each participant's real role, submitter, co-owner, or manager, instead of the company they belong to. The old behavior could misfile people, so a manager missed a co-owner's message, or a submitter never heard from the supplier running the order. Now notifications line up with the two settings you already see, orders you submitted or co-own and orders you manage, so the right person hears about the right thing. On the same note, every email notification, including multi-factor codes, now uses the sender address you configured, which matters for anyone running a custom-branded platform.
Translation Memory Gets a Default It Should Have Had All Along
You can now set Allow Context-Based Duplicates once at the translation memory level instead of configuring it on every consolidation. It applies automatically as the default for future consolidations into that memory, and you can still override it per consolidation when a job needs it. The behavior is covered in the default search settings guide. Small setting, real time saved.
Also in This Release
The rest clears friction across the platform. The QA Issues report now includes source and target text beside each issue, and the editor's report module preselects the target language at your cursor, so you generate the right report faster. Reference material auto-copy, which pulls files from a client's Templates folder into new projects, now works for projects created from orders, not just manual ones. Empty folders left behind after a deletion are removed automatically, recursively up the tree, so the Document Library stays tidy. The Supplier Finder window loads noticeably faster on large vendor networks. Translate Files requests can run in parallel for the same user through an optional parameter, cutting total time on high-volume work, with the previous sequential behavior unchanged by default. And the MT Hive order form gains clearer descriptions of which memories drive pretranslation versus post-editing, handy for anyone configuring the client portal.
The fixes close several real gaps. The Create Segment popup is fully editable again for termbase resources on platforms without Terminology Management enabled. XLIFF files with very large character-length constraints now import cleanly instead of failing. A deep link to a specific document through single sign-on now opens that document, not every document in the job. Codyt projects with versioned target languages produce identical word counts for a target and its v2 when the configuration matches, which keeps costing and invoicing accurate. Non-admin users with the right permission can open settings for older order forms again. Custom field placeholders populate consistently however an order is created. And downloading a translated ZIP from the Translate Files tool no longer fails with a file-not-found error.
A release with something for every kind of content team. The full technical notes for 2026.1.13.0 live on help.wordbee.com. If structured file handling or connector-driven workflows are central to your setup, talk to us and we will walk through the options with you.