⭐ A new “Pseudo-Translation” option is now available in the editor’s Actions menu. Users can apply pseudo-translations to simulate how the actual translations will look like, download them into their design files, and easily detect untranslated content and layout inconsistencies. Project managers and designers can also use pseudo-translation to preview how text expansion or character variations affect UI layouts before actual translations are applied.
The feature sets a 30% expansion percentage and automatically uses the base language as the source for generating pseudo content. Users can also configure custom leading and trailing characters (the default formatting adds three exclamation marks: [!!! !!!]) to highlight pseudo-translated text.
A new predefined workflow status, “Pseudo-Translated” is automatically applied to all pseudo-translated keys to clearly distinguish them from regular content.
Additionally, a new order option ensures that pseudo-translated keys are excluded from standard translation requests unless explicitly selected. Together, the workflow status and ordering logic keep projects clean and prevent pseudo-translations from polluting production work unless the user intentionally includes them.
⚙️ The backup import functionality in Project Settings now includes advanced, granular restore options for tags, screens, and translations. Users can choose whether to restore only deleted tag and screen data or to restore all available data. The import process also allows full control over whether non-included elements should be deleted. Translations and statuses are restored automatically by default, ensuring a consistent state after import. The Import button now remains disabled until a valid configuration is selected, preventing accidental or incomplete imports. Additionally, any changes applied to tags or screens during the import operation will now generate corresponding changelog entries for improved transparency.
🛠 Keys made up entirely of one or more periods (e.g., ".", "...") are now preserved correctly during i18next export, both in manual and CLI exports.
🛠 Exports now show branch names instead of internal branch IDs, consistent with the UI view.
🛠 Spaces that contain multiple boards now display correctly. Custom issue types in Jira Spaces are now fully supported and available for selection. Additionally, all dropdowns in both Project Settings and Editor modals are now updated dynamically to reflect the latest configuration changes in real time.
🛠 Sync conflict handling improved when configuration is accessed from multiple tabs. Errors are shown clearly, and data integrity is preserved.
🛠 The GitHub integration now detects unsupported structures such as tag arrays to prevent misconfigurations. Users are shown clear warnings for wildcards, mismatched file counts, and other unsupported patterns. Despite these validation checks, all configuration steps remain accessible so users can review the details and make corrections as needed.
Learn about our latest features and improvements
Read the Full Article
Learn about our latest features and improvements
Read the Full Article