Check back here for regular updates, new features, and bug fixes that may affect the translation experience in Lilt!

Last updated: 30 Sept 2020

30 Sept 2020

New Features

• Working Time Tracker

As linguists translate or review on the platform, it's useful for them to know how long they've been working on a given project. Starting today, information about the number of hours worked will appear in the info section of the project, on the right sidebar.

The time format will be shown in decimal form. For example, if a translator spends 2 hours and 27 minutes, it will be shown as 2.45 hours. The information is only viewable while the project is in a non-archived state. Please note that once the project is archived, the information will be inaccessible.

It should be noted that the time spent working will not update live as work progresses. Rather, hours worked will be updated approximately every 3 to 4 hours. The time tracker will indicate when the last update of time spent working was made.

25 Sept 2020

New Features

• Right -to- left and Left-to- right direction control

We implemented Right-to-left and Left-to-right direction marks in the CAT editor. These controls are used to set the way adjacent characters are grouped with the respect to text direction. For translating from English to the Arabic language without an LRM control character, the browser would render the phrase like "The language C++ is a programming language used..." in to the target like this:

                                                                                                                        لغة ++C هي لغة برمجة تستخدم...

With an LRM entered in the editor after the ++, appears like this, as the writer intends:

                                                                                                                               لغة C++‎ هي لغة برمجة تستخدم...

Simply enter one of the markers directly after the word to change its direction. Check out this video demo showing how the markers work.

*Known Issue: After the marker is inserted into the segment, you will get an extra marker character when pressing the spacebar. The extra character will disappear once you confirm the segment.

1 Sept 2020

New Features

• Whitespace character support

There are some changes to the CAT editor to support the representation of whitespace characters in documentation. The editor now supports the entry of the following whitespace characters:

 ° for non-breaking space, entered using Command + Shift + Space keys

→ for tab using the Tab key

As a result of these changes, the mapping of the Tab key will be used to enter the Tab whitespace character. MT suggestions in the editor will only autocomplete using the “Enter/Return” key.

• Navigating between tags

Before, the Tab key was also used to navigate between tags on segments. Now, you can navigate between tags for segments (unconfirmed and confirmed states) by using the following keyboard shortcuts:

Ctrl + ] to navigate to the next tag

Ctrl + [ to navigate to the previous tag

21 Aug 2020 

New Features

• Batch QA 
  • When linguists ran the  “QA Check” option from the Tools menu, they would need to go through a document segment by segment to find and fix errors. Now, linguists have the option to run a Linguistic Batch QA option showing a consolidated view of all linguistic errors for all segments (unconfirmed, confirmed, accepted) grouped by error type in a new modal. The new interface allows translators and reviewers to view, ignore, and accept linguistic QA errors all at once, right in the new modal. The option to run a QA check on individual segments remains.

Batch QA Modal

• Tag QA

  • QA checks against tags are now available, reducing the amount of time SMs spend looking for tag errors.

    When the Run QA option is selected from the Tools menu, QA checks are run against a set of tag rules and linguistic QA rules. Users can switch between linguistic QA checks and tag QA checks by toggling the error view on the segment.

    There is also an option to Run Tag QA at the document level. To find errors, focus on each segment to view errors on the target.

    

*If there are no tags in your document, you will not see any messaging back if you run the Tag QA check.

27 Jul 2020

New Features

• Simultaneous text + tag editor
  • You can now edit tags and text simultaneously. After a segment with tags is confirmed and tags are projected, you will be able to move tags (with drag-and-drop or keyboard shortcuts) and type text in the same mode.
• Tag validation override
  • We have automatic checks to determine whether tags are positioned and nested correctly. When a tag is invalid, it shows as red and does not save automatically. Now, we’ve added the ability to override the validation rule if you are sure that tag placement is correct in a particular case, by confirming or accepting the segment. When a segment is confirmed / accepted, all tags will be saved.

24 Jul 2020

New Features

• Batch accept and reject assignment
  • You can now accept or reject a translation or review assignment for multiple documents at once by clicking "Select All" (or selecting them one-by-one) from the document details view.
• New error categories
  • We've updated the error categories according to our new error taxonomy. Ask your SM for more information about Lilt's new Review Guidelines.

23 June 2020

New Features

• Filter for segments with tags
  • You can now filter for segments with tags (from "View > Segments with Tags") so you can double-check tag placement easily. This filters for all segments with tags in the source. Make sure you’ve turned on "Tools > Show tags in confirmed" to see the tags in the target!
• Clearer translation and review deadlines
  • The project card will now show you the most urgent translation and review deadline in that project for you.
    • 
  • This information will also be shown on the Project Details sidebar (when you click (i) on the project card), as well as in the documents view.
    • 

28 May 2020

Bug Fixes / Improvements

• Fixed a bug where 100% matches were getting degraded to 99% matches in the sidebar and editor
• Fixed nbsp shortcut: now accessible with `cmd+shift+space`.

22 May 2020

New Features

• Tag auto-propagation and leverage:
  • Tags will now be auto-propagated with 100% TM matches! If you change tag positions in a segment and another segment has the same source tags, the target tags will be propagated to match. Note that you must have forward and/or backward auto-propagation turned on in "Settings."
  • When a 100% or 101% TM match with matching source tags is leveraged, the target tags will be leveraged as well.
  • 100% or 101% TM matches with the same source text but different source tags will be degraded to 99% matches.

Bug Fixes / Improvements

• Fix bug where projects detail search bar ("Search Documents") didn't work

7 May 2020

New Features

• Added spell check in QA

Bug Fixes / Improvements

• Fix bug where comments disappear on refresh
• Fix false positive trailing punctuation mismatch in Arabic QA
• Fix termbase crash when the query string contains nbsp
• Fix bug where "Reviewed Target" in revision report didn't match target in the editor
• Fix bug where typing in one segment moves tags in another segment

22 Apr 2020

New Features

• New keyboard shortcut for toggling between tags and text mode (ctrl-option-n, also see the (?) sidebar panel)
• Note a new change to the tag editor: we are rolling out the simultaneous text + tag editor, but in the meantime we needed to make some changes to improve the performance in the editor: you can now no longer edit tags in an unfocused segment. To edit tags, you must click on the segment (without unconfirming or unaccepting it).

Bug Fixes / Improvements

• Performance improvements for the editor
• URLs in Segment Metadata now open in a new tab