Tip
Click Follow on the section level (one up from the article level) to receive notification of when new notes are released.
Earlier release notes can be found in the archive.
Fixed Bugs
-
Backslash symbol was displayed as a Yen or Won character in Japanese or Korean target segments in the editor. This has been fixed.
Fixed Bugs
-
Attempting to download a source or target file from the second and/or higher job part of a split job was generating an error. This has been fixed.
-
QA was incorrectly displaying non-confirmed segment warnings for already confirmed segments. This has been fixed.
-
Linguists were not able to complete a job when all segments had been confirmed from pre-translation. This has been fixed.
Fixed Bugs
-
Jobs imported with the AsciiDoc file type and the option enabled were not possible to open in the editor. This has been fixed.
-
Re-confirming a confirmed segment with Instant QA off was generating zero thinking and editing times. This has been fixed.
New Features and Improvements
-
MTUs are no longer consumed by the editor in the CAT pane when MT is used for pre-translation.
Fixed Bugs
-
When a linguist joined segments in a shared job, the segment was being duplicated. This has been fixed.
-
There was no highlighting of found texts in target segments, navigation to the segment with next/previous occurrences was broken and there was no replacement of found occurrences. This has been fixed.
New Features and Improvements
-
A UI task dialog now displaye the list of currently running/planned operations.
Fixed Bugs
-
Linguists without the rights to edit source content could not save target segments with special characters. This has been fixed.
Fixed Bugs
-
Edited comments required resaving. This has been fixed.
-
Clicking on the comments icon
was randomly redirecting to a wrong segment's comment. This has been fixed.
Fixed Bugs
-
With .JSON files,
max length
was not displayed in the contexts note pane for segments with ICU. This has been fixed. -
It was not possible to select multiple segments by segment number in the QA pane. This has been fixed.
Have you come across any bugs?
Thank you for letting our Support team know.