⭐ API order creation now supports file attachments, allowing teams to include reference materials directly with automated submissions. This feature enables API-based workflows to fully replicate the manual order submission experience by attaching additional files as part of the order payload.
⭐ Additional validation has been introduced for the POST /v1/api endpoint (used for content upload). Payloads that contain metadata (meta) or description (desc) values for any language other than the project base language (source) will result in an error rather than being silently accepted and ignored. Metadata is stored at the key level and language-specific overwrites are not supported.
⭐ For the use case where the Figma plugin is used as a direct connector to GlobalLink Enterprise Translation Management System (GLE TMS), the languages available for creating a translation order from the plugin is now limited to the set of language pairs configured in the connected GLE TMS project. Previously, users could select any language, even if that language was not yet configured. This sometimes caused orders to enter an “On Hold” state when unsupported languages were submitted.
🛠 The import modal previously allowed users with the translator or reviewer role to assign a tag during import. The tag selection option is now hidden for users with these roles.
🛠 When copying and pasting keys into the Figma plugin key renaming fields, hidden characters (such as carriage returns) could be included without being visible in the editor. This could result in keys being created with unintended names that did not align with how the key is used in other systems (for example in string files).
The plugin trims non-printable characters, whitespaces, and line breaks during the key renaming step to ensure consistent key naming.
Learn about our latest features and improvements
Read the Full Article
Learn about our latest features and improvements
Read the Full Article