Product Updates

New: QA checks, translating offline and more

Written by Petr Antropov · 3 min read >

A new set of features, expected or positively-surprising, bam! We are happy to introduce 18 new functionalities in this update. Should you think we are missing any, please be sure to stop by vote.lokalise.co and add your suggestions or vote for suggestions made by others.

Editor: Focus mode

Translators, one more treat for you. We believe that the Focus mode may help you to finish the job sooner. Do not be distracted by all the available bells and whistles when you just need to translate or review. In order to enable the Focus mode, first switch to the bilingual view.

Editor: changes in the source

Another cool feature in the bilingual view. It is now possible to see the differences or the changes that happened to the source text since it had been last translated. These changes are highlighted and/or struck through.

Editor: auto-complete

This one is kind of self-explanatory. Auto-complete feeds from the words in either machine translations or the translation memory.

Editor: reviewers in translation history

Besides seeing in translation history who exactly has updated the translation and what was changed, you can now track who has reviewed the translation.

Editor: hotkeys for TM suggestions

Fulfilling another request from translators, we are adding more keyboard shortcuts for translation suggestions. Now it is easier to navigate. By using the combination of Ctrl+Alt+Number, select the suitable suggestion without using a mouse or a touchpad.

Once offline translations are enabled, every translator, first having entered the bilingual editing mode, will see the offline translation widget.

Translators will be able to download the current target language as an XLIFF file, translate it offline and upload the translated XLIFF file back to Lokalise.

Rest assured that the source language will be safe, as offline translations can only change the target languages. When a translator uploads a file, Lokalise replaces all translations of the target language with those in the file. Filename and platform attributes of keys will not be changed.

Tasks: lock the keys engaged in a task

Limit the access to keys engaged in a task only to task assignees. You do this by ticking the “Lock translations” checkbox when creating a task. Note that you may lock or unlock the currently engaged keys in the properties of an active task.

Tasks: reviewal tasks

When creating a new task, you can now specify its type: translation or reviewal. Items in reviewal tasks are marked completed by clicking the “review” icon in the editor. As you remember, in comparison, items in translation tasks are completed by updating the translation. The other way to mark items as completed in both types of tasks is to click the “mark as done” icon.

Tasks: chained reviewal tasks

Build advanced workflows with chained reviewal tasks.  To create a chained task, choose a parent task from the list. A chained task will be queued until the parent task is completed and then start automatically. You can create an unlimited number of chained tasks. Chained tasks inherit scope from parent tasks, however, you can assign them to different contributors.

Tasks: automatic key tagging

It is now possible to automatically tag keys in a task once it is completed. Tick the “Tag keys as the task is completed” checkbox and enter one or more tags to be added.

QA checks

Quality assurance (QA) checks are run every time a translation is updated, whether it happens in the web UI (the Editor), as a result of an API request, or of a file upload. Currently, we provide 11 different QA checks. Every check can be either turned off, set to either a warning (the warning icon will pop up in the editor) or an error (would prevent translators from saving the translation in the editor). You will find the QA checks in Project settings > QA checks. Again, feel free to add your ideas for additional QA cheks here.

Glossary: extract terms

Keeping translations consistent across the whole project is always important. With this new functionality, it is possible to automatically extract the terms repeated a certain number of times, and add them to the Glossary.

Fuzzy is now Unverified

Due to numerous requests, we re-branded😎 the fuzzy flag and replaced it with unverified. Just to remind you, it is an indicator which you can turn on and off. If its automation is enabled in Project settings, and when the source text has been changed and target text should be re-checked, the indicator sets itself on. Either way, you can always click on the indicator or apply a bulk action in order to turn it on or off.

Dashboard: unverified translations

In the dashboard, for every project, you can now see the number of unverified translations across all the languages.

Statistics now cover more

Statistics, which you can find for every Project, now counts the words in the following strata and their combinations:

  • translated
  • reviewed
  • for a selected period
  • at all times
  • by language

Updated word count, percentage done and other stats

We have re-worked our word-counting mechanism. It now takes into account the translator’s effort. There are four cases of how words we count in Lokalise. Learn more about it in this article here.

LiveJs: disable advanced HTML

For our web in-context editor, we have added a new parameter used in the Live JS snippet: disableAdvancedHtml (boolean, default value – false). Enable it to edit only the content-editable sections. Bold, Italic, Headings, Paragraphs, Links and Lists will still be available in the dynamic toolbar.

Official Lokalise Ruby API interface


We have just released an official Lokalise Ruby interface. Of course, we will continue adding libraries for other programming languages.