Throughout this summer, you should have felt the increased speed of both the API and web of Lokalise. We’ve refactored and optimized the backend and some of the functions, but also added new features which we list below. Please click on the links which interest you most. Remember, there’s always vote.lokalise.com for you to request features which you might be missing or vote for existing requests you’d like to prioritize.
Screenshot Editor 2.0
We’ve totally rebuilt the Screenshot Editor. The biggest change you’ll notice is that Lokalise shows the coordinates of a key, i.e. its area. As soon as you upload the screenshots, the system will OCR them as usual and mark the coordinates of the text. The area is visible to all translators, of course. Another good news is that we’ve been saving coordinates of the screenshots which you’ve been uploading during the last 5 months. It means that you’d not need to re-upload the screenshots to see the areas of the text. In case you need to set the coordinates manually, just drag the area on the image to link to a key.
As per your requests at vote.lokalise.com: first, screenshot titles are automatically set to the filenames of the uploaded image files. Second, you can replace a screenshot while keeping all the key links. For more information, take a look at the Screenshots Editor docs.
This new integration pulls files from one or more of your Bitbucket repositories and creates pull requests from Lokalise. You can find it among available integrations in their usual place, project settings > Integrations. Learn more.
Each of your projects has now a QA issues counter. Hovering over the number will show a detailed report from which you can go deeper into particular issues. Currently, the list includes unreviewed strings, placeholder/HTML mismatched strings, items with spelling/grammar errors and leading/trailing whitespaces. It’s in the pipeline to add QA checks for URLs, e-mails, and numbers. Feel free to suggest other types of issues at vote.lokalise.com.
Translation memory leverage
An important update for customers who outsource translations from third parties, e.g. their own translation agencies or freelancers instead, instead of using their own in-house translators or our translation partners. You can now pay them taking into account the use of the translation memory, in other words, the TM leverage. There are several ranges (see the screenshot above) you can use when calculating the cost per word.
The feature comes in two flavors: first, you can access it at the projects’ Statistics page. Second, it’s available when you are creating a Task. The system will calculate the initial TM leverage at the moment of creating a task and save it for later use in the task details.
New landing page for public projects
Self-explanatory — take a look at a good example, public projects now look even sexier. Make a good use of your partner or user community in translating your text elements.
Sometimes case matters, and we heard your voice from the vote page. Now it’s possible – use a simple toggle to switch between case-sensitive and case-insensitive search in the editor.
As had been requested, we added a filter (available under Filter > QA > Target matches source in the Editor) that selects all the keys where the target translation value equals the source value. Usually, that happens when, before using Lokalise and its export switches, you’ve manually filled the target values (say, French) with base values (say, English), and would now like to have them properly translated into, say, French.
Glossaries can now be shared among the projects, again, thanks to your requests and votes at vote.lokalise.com. Available to Pro subscriptions.
Support of tools: attributes
We’ve added support of tools: attributes for Android XML import and export.
The never-ending battle in coding between TAB and SPACE is obviously not over. But we’ve got you covered – set indentation for the exported files using both the web interface at the Downloads page or the API/CLI tool (see –indentation parameter). Those using an older version of the CLI tool, please do upgrade.
Updated blog article on the best deployment practices
With new tools and usage patterns available in Lokalise, your deployment processes may be more flexible and efficient. We’ve updated the old article, and it’s now worth taking a look again for any tech-savvy team.