The summer release brings significant improvements to the translation interface and additional features and fixes. You can also opt-in to try a new integration with Zendesk or implement the brand-new CDN client. Curious to learn more? Let's go.
⭐ Interface updates 🔗
We try to constantly improve the UX for translators and other users involved in the localization process at Localazy. Sure, even if automated MT or AI translation can save a lot of time, someone still needs to see the results, check for errors, and fix potential mishaps. Humans are still irreplaceable, and we are building Localazy (mainly) for humans! 😅
🪗 HTML/XML tag collapsing 🔗
A nifty little button was added to the toolbar to help you collapse markup scattered in your translation strings.
This is especially helpful when translating XLIFF files popular with some third-party solutions such as e-learning platforms (such as iSpring Suite, Rise 360 by Articulate & Adobe Captivate) and other external sources that carry additional styling or metadata with the text. It can get cluttered pretty quickly, and the actual text information is lost in the chaos. Not anymore! 🙂
Before:
After:
📌 Pre-translate is now available when adding language 🔗
You can now save a few clicks and pre-translate languages right after adding them to your project. Lightspeed!
🔎 Search and filtering are now available for key aliases 🔗
Now it's possible to search and filter key aliases and export path aliases.
📠 Improved auto-detection of uploaded file formats 🔗
Improved detection of file format and language, perfect for PO/POT and XLIFF files or multilingual formats.
🖼️ Figma: Support for nested keys 🔗
When using Localazy's Figma Plugin, you now have an additional option in the settings that allows you to create nested keys in Localazy by putting a dot into the text node name. Remember that you must have the option "Use node name as source key" active too.
This improvement should help you exchange keys more seamlessly between design and development with Localazy.
🌐 Localazy CDN Client 🔗
The Localazy CDN Client is a Node.js library that offers functionalities to fetch translation strings from JSON files published on the Localazy CDN.
Content can be fetched from JSON files as objects or plain text for other file types.
When translators add translations to your project, they are automatically published to the Localazy CDN. Every published project has its own metafile that contains information about the project files and their translated versions.
Under the hood, the CDN Client fetches the metafile and uses it to get the URLs of the files and their translations. You simply select the files and languages you want to fetch, and the CDN Client does the rest.
🔗 Duplicity Linking gets a new magic button 🔗
The Duplicity Linking feature, which helps you control duplicate strings, has a new magic button that automatically resolves all duplicate content for you. It prefers to always link strings in the same project and file, if possible.
Go ahead and try it! You can always manually control which strings should be linked and which should not. Soon, you will also be able to resolve duplicates automatically as part of Automated Workflows.
🎮 In development: Zendesk Integration 🔗
We are developing a Zendesk integration to help you translate your help centers and knowledge bases maintained with Zendesk. Similar to our Intercom localization solution, the Zendesk plugin will enable you to transfer the data between Zendesk and Localazy in a few clicks and automate it later.
You have the chance to try out the integration before its release and localize your articles with Localazy now.
🗂️ Fixes & Improvements 🔗
As always, there were also numerous fixes and improvements to make your life with Localazy easier. Check them all out:
- HTML entities in source files are escaped and rendered correctly in the translation interface
- Upload dialog for PO and XLIFF files now contains language selector
- While uploading files, the checkbox "mark missing keys as deprecated" is present only when existing keys are updated
- Fixed memory leak during translation sessions
- Better notifications after uploading files
- Fixed format conversions on the web
- Fixed plurals breaking with source language change in the translation interface
- Improved quality checks behavior
- Fixed regex symbols breaking translation interface when used in Glossary terms
- Fixed generic error appearing after file upload
- Added side-scroll for data tables with pinned left and rightmost columns
- User avatar is now the default image for personal organization
- Improved long-running operations (pre-translate, batch approve) progress accuracy
💬 Join the conversation! 🔗
Follow our LinkedIn page to stay updated on new Localazy features, usage tips, success stories, and behind-the-scenes information. See you there! 💙
✔️ Conclusion 🔗
Please share your thoughts on the latest developments in the comments section. We value your feedback and appreciate active users who contribute with tips and suggestions to help shape the platform's improvements. Don't hesitate to reach out to us.
