Release Notes 7/18/2018 - Wordbee Translator

New Wordbee Translator features and enhancements released on Wednesday, July 18, 2018:

[NEW] Revision history of translations: We now log text changes from the same user if the type of work is not the same
One and the same user may open the same document starting from two different jobs. For example the same user may be assigned a translation and a revision job and make edits for both. Normally, the system does not log changes if edits are done by the same user. However, when the job changes, edits from the same users are now logged.

[IMPROVE] [New Editor] Improvements regarding batch actions and exports
WBT users are now able to update a specific language, custom field with a batch action, when the translation is empty. At the same time Wordbee performed some improvements so the exported Word or Excel document filename is the name of the original file, or else it is the job name.

[FIX] [Editor] Translation finder various fixes
Wordbee has fixed 2 issues in the translation finder:
1. WBT users can now add correctly a new entry in a resource.
2. WBT users are now able to select correctly a target locale in the languages list.

[FIX] Fixed a rare situation leading to "ghost" word counts in standard projects
Wordbee has fixed a rare situation that could lead to entries in the word count that aren't associated with any document that's marked for online translation.

[FIX] User-interface issue found on the count tab on the standard project page
Wordbee has fixed an issue on the standard project page where the header holds the export button was not stretched correctly and aligned with other section in the projects word count tab.

[FIX] [New Editor] Improved pop-up TM history window
Wordbee has improved the New Editor TM pop-up history by making it open in a new tab. In the past the pop-up window was too small and not re-sizable. On the Old Editor this pop-up remains unchanged.

[FIX] [NewEditor] Dependencies are now updated when changing the job status
Wordbee has fixed a problem where dependencies weren't taken into account when changing the job's status for standard projects.

Browse more releases at:

Have more questions? Submit a request


Please sign in to leave a comment.