New Wordbee Translator features and enhancements released on Wednesday, October 25, 2017:
[NEW] Linguistic resources can be deleted in the new editor
When working on linguistic resources (translation memories, terminologies...), it is now possible to delete individual segments within the interface of the new editor.
[NEW] Custom fields added to services in a price list
You can now add custom fields to service in a price list. Fields are configured by the administrator at "Settings" > "Custom fields" > "Price list services".
[NEW] Orders list: Links added to each line to directly navigate to project, jobs and more.
Orders list: Links added to each line to directly navigate to project details, jobs list, cost and more.
[NEW] [InstantTranslate] New option to submit translation request by pressing the ENTER key
A new user option has been added to the new instant translation app allowing users to submit their translations directly by pressing the ENTER key.
[IMPROVE] Outlook plugins - v1.01.25: Deadline selection improved when submitting post edit request.
New plugin version 1.01.25 available for download. When submitting a post edit request for a machine translation, the deadline selector does not format dates in the PC's local date format. This has been fixed.
[IMPROVE] New languages : Dzonkha, Native Hawaiian, Chamorro and Okinawan
Several new languages have been added to the system :
- Native Hawaiian
[FIX] [NewEditor] XLIFF import does not import tags
Using the new editor, it is not possible to import tags while importing an XLIFF file, they are ignored and not updated.
[FIX] [NewEditor] Impossible to create a new segment in the new editor but it is possible in the old one
In some cases, it is impossible to create a new segment in the new editor but it is possible in the old editor. Creation not authorized for this resource.
[FIX] Line break issue in reconstructed YAML files
An issue with line break in some yaml reconstructed files has been identified and corrected.
Folded style text nodes (starting with char >) were not properly managed. Now these nodes are converted to Literal style nodes (starting with char | ) in the reconstructed document .
Browse more releases at: