Product Updates

New: Custom translation statuses, Audit logs, Contentful, and more

Written by Nick Ustinov · 2 min read >

Ahhh, sunny July – the month of holidays, festivals, and of course, plenty of new and updated features. 😎

Here’s a quick overview:

We’ve been working hard to bring you the latest batch of updates to the Lokalise platform – take a scroll and let us know which you’ve been waiting for the most!

Custom translation statuses

Implement translation workflows of any complexity using custom translation statuses. Enable this feature in project settings and add as many statuses as needed. A translation may have either single (sequential) or multiple statuses, it’s up to you. Restrict task assignees to toggle certain statuses. Filter by a task status in the editor or when downloading files.

Audit logs

Complete transparency of what’s happening in your team, with your users, and projects. We track over 80 events and keep the log of every action. You can filter by user, event or date range. Exportable as CSV. This feature is targeted at Enterprise customers.

Integration with Contentful

Import data from your Contentful spaces to Lokalise. Translate the content in the editor using our translation tools, apply your translation memories, use tasks and other features in Lokalise. Once ready, sync back to Contentful.

Contributing only in tasks

There are 3 degrees of freedom of translation processes in Lokalise. Translators can either contribute whenever they like, both whenever they like and in translation tasks, and only in translation tasks. The latter is now possible by restricting contributors to work within tasks. Note that admins will still be able to edit translations regardless of the restrictions. Enable the restrictions in project settings, and keys will get locked and be only edited by assignees in tasks.

Project tags in the dashboard

Add tags to projects to organize them into logical groups. Filter by projects tags in the dashboard. Useful for customers with tens or hundreds of projects.

SLAs (Service-level agreements)

Smaller companies may be comfortable with the level of notification and monitoring our Status page that we’ve been able to provide until now.

However, some larger customers may be commercially inclined and/or legally required to demand a certain response time, as well as uptime guarantees through an SLA. If this is something you require, please contact us for further details in the in-web support chat – we’ll be happy to talk about this opportunity.

 

Alternative CAT-standard hotkeys

Some translators prefer CAT-standard hotkeys in the editor. We’ve added a new personal profile setting that allows switching to the Memsource / SDL Trados hotkey set.

i18next support

As i18next is gaining popularity, we’ve added the support of JSON files with i18next, in particular, where plurals are stored as i18next. You need to enable the support for i18next in project settings.

Mark machine translation order results as Unverified

When placing a machine translation order in the Orders menu, it’s now possible to mark all translated items as Unverified for further post-correction.

Spelling exception management

Admins can now manage project-wide spelling exceptions in project settings. If someone has added a word to a spelling exception list by mistake, this is a place to review and remove it.

Translation history for plurals

In addition to restoring regular translations, from now on you can restore plural items. Use the translation history button to the right of the translation item.

New download options

Last reviewed export

An extra option at the downloader – export the previously reviewed version instead of the last, but unreviewed, one. Available using API and CLI as well.

Add a new line at end of file

Some IDE’s show an error in case there is no new line at the end of a file. We’ve taken into account your vote on the feature requests page and have added this option to the downloader. Available using API and CLI as well.

Double colon as YAML separator

You can now use :: (the double colon) as the nested level separator for YAML keys. You’d appreciate it if you’re exporting the same content both to YAML and JSON files since the latter is using :: as a separator.

API updates

New endpoints

We’ve added the endpoints for translation providers, payment cards, translation orders, and custom translation statuses. All client libraries are updated as well.

Set iOS and Android bundle description

You can now set the bundle description when generating a bundle using the API.

 

What’s next?

We love hearing your requirements, and nothing gives us more satisfaction than being able to implement those suggestions that you’ve voted for.

With that in mind, comment down below what you want to see next month! Better yet  – submit a suggestion.