The first 2 months of 2019 are bringing you quite a number of novelties and improvements. Most of the below was triggered by requests with the most votes on https://vote.lokalise.co. You know what to do.
Document file support (beta)
We are introducing support for paged documents – literally the ones that are not key-value based. As a result, you can now upload, translate and download DOCX and HTML files without the need to create key entries what you might have been doing before. With this feature, you are able to use the same TM, MT suggestions, role management while translating both localization files and paged documents.
Start by creating a new project and choose the Documents project type in order to be able to upload paged documents. Currently the feature is in beta and is available from the Essential plan. Support for PDF, InDesign and other formats is coming soon.
Lokalise translation services
Besides your own in-house and outsourced human translators, you are now welcome to start using our native professional translators covering 92 languages under our lifetime quality guarantee. Thanks to grown volumes of translation orders, and in order to improve the workflow and quality, we have decided to run our own translation show for customers who require us to. You can reach out to translation managers in our in-web support chat with your questions and requirements, and they will guide you through.
If you employ localization managers, we are sure they will find a good use of our translation services from now on. If you do not, you can very well continue without localization managers for some time, with our translation managers serving as a good substitute. Please start the chat discussing any translation and localization jobs you have in mind. We will be constantly expanding the scope of work, and your suggestions will help us in prioritizing.
Translation memory 2.0
We have extended Lokalise TM to support multiple translation memory dictionaries, added the support for .TMX file import/export and the ability to set a different TM prioritization order for different projects. The TM concordance search widget has been updated as well – now you can search for exact matches, search in target and disregard the locale region when searching.
Tasks: new functions
Find/replace with preview
We have completely rebuilt the find/replace dialog. You can now see matching results first and choose what to replace and what not. In addition to good old translation replaces, we support replaces in key names and tags.
Spelling and grammar checker improvements
Besides updating the spellchecker engine, from now on all spelling and grammar errors are shown inline. Other improvements include better placeholder handling and the ability to add exceptions to spell- and grammar-checking rules.
Translation statistics reports
We believe that statistics must be transparent for all parties: managers and translators. That is why we have added two new reports. First of all, every user now can download their personal translation/reviewal report from the Personal profile page. That includes every single word translated/reviewed along with the project name and accounted words amount. Finally, your managers are able to download these reports for any/all users from their Team settings page.
Offline translation: updates
We have made some important changes to the offline XLIFF translation feature. Now you can export the keys which you filter in the Editor. Next, the exported XLIFF file contains much more information, like external links to screenshots, status of the translation and comments. A unique segment identifier is now used instead of a key name, which helps in avoiding filename-specific collisions. As mentioned above, the offline translation feature is now directly available in Tasks.
Enforced 2FA for teams
Your admins can now require all users in your team to set up two-factor auth by enforcing 2FA in Team settings. The users who currently do not have 2FA enabled, would be asked to enable it next time they login before accessing the project data. This feature is available starting from the Pro plan.
Cross-project key references
One of the most requested features according to our vote page is now live. It is cross-key referencing — the ability to link values of the keys across different projects. Now instead of referring the keys using their names, one will use unique key identifiers, which can be found in the key’s Clipboard menu.
Tagging skipped keys on upload/import
When our Filter in the Editor is not enough, or for any other reasons, you can upload/import a file with the keys already present in the project with no changes to the translations, only for the purpose of marking them with certain tags.
SDK key in project settings
There were requests to separate personal API tokens from Lokalise mobile SDK tokens – here you are! SDK tokens are also not tied to any user in your team. These can only be used within SDK.
Node.js and Ruby libraries for Lokalise API
QA issues and statistics in API responses
Project-related endpoints in API will now also return QA issues data with the response. Well, you may want to be sure there is none before releasing your strings to production.
API’s endpoints for User groups
New IP addresses for webhooks
If you are filtering Lokalise IP addresses for incoming webhooks, please add 22.214.171.124 to the list. It is one of the addresses our webhooks may come from.