It is important to focus on the information you need to work with, that’s why we’re introducing Filter 2.0. You may choose any of the predefined filters we’ve built (untranslated, fuzzy, leading whitespace, placeholder mismatch, by file, by tag, by platform, by context and many other) or create a completely custom one – of any complexity, really.
Combine property parameters by clicking the ⊕ (Plus) icon. Logical AND / OR operators are used to group the parameters. Saved filters are shared among all project contributors. Project admins can now build a filter and mention its name in the project chat so all contributors will see it. Be creative!
Translation memory search and .TMX import
We’ve added concordance search to our translation memory engine. Hit Cmd/Ctrl-G to open the widget in the editor (or click the icon in the top right corner, near the Add Key button). Start typing a word to see how it’s been ever translated to any of the languages (if you are in the multi-language view) or a language you are currently editing (in the single language view). As usually, translation memory is shared between all projects and users in your team.
That’s not all – you can also import translation memory (.TMX files) using the widget. We support multilingual .TMX files as well.
Language auto-fill rules
Easily chain languages using auto-fill rules in project settings. Once a translation in the language you set for monitoring gets updated (either using the editor, import, API or any other source), all the chained language translations are updated as well. You can choose between overriding existing translation or not. Additionally, we recommend setting auto-filled translations as fuzzy, so translators can filter out by Fuzzy and review the strings.
Customize inline suggestions
As your project grows, your translation memory, glossary, and other suggestions base grow. Now you can customize the content of the inline suggestions drop down (the one that shows up in the editor when you click on a translation). Click on your avatar in the upper right corner, choose Personal profile and adjust the inline suggestion settings as you prefer. You can move them up or down too!
Custom admin rights
The long-awaited feature has arrived – set custom rights to project admins at project’s Contributors page. Right now you can customize the access rights only for project admins. Contributors’ access rights, e.g. the rights to upload or download translations in a particular language, are coming in future updates.
Changes to Glossary
There are several changes to the Glossary (termbase). First of all, per-language definitions and descriptions are available now. You may describe a term in any language and this description would be shown to a translator editing text in that language. If there is no language-specific description, the system would instead show general term description in the inline suggestions.
You can import and export your glossary using .csv files. Detailed .csv format structure description is available in the docs.
Single language (language pair) view changes
Teams translating from multiple languages will appreciate the change. In the single language view, the system would now use selected reference language for the inline suggestions (machine translation, glossary, translation memory) instead of using the project’s base language. Same applies to populating the translation memory – while you edit in the single language view, the translation memory is populated from the reference language to the language you are editing.
Multilingual screenshot recognition
When you upload screenshots in bulk (using the project’s screenshot page) we run them via the OCR engine to detect any text strings and link them automatically to keys/translations in your project. From now on in addition to English, our OCR engine supports Russian, French, German, Spanish, Italian, Swedish, Finnish, Turkish and Polish languages.
CLI tool update
We’ve updated our command-line tool to return a non-zero exit code in case of error. Grab it here.