Feature requests

Add support for Apple 'substitution' type in XC String file format.

Add WYSIGWYG to the text editor to simplify Markdown support for non-technical users.

Add an option to export markdown translations (translation keys set to Markdown type) each to a separate file, for easier text files management. Translations with Markdown type will be exported as separate files.

The auditing feature will enable team administrators to monitor user activities across all projects. It will also include detailed tracking of API access.

Option to duplicate existing translation keys by addind a prefix/sufix with possibililty to set the duplicated keys as depreated or assign them to a specific namespace.

Add an option to easily copy languages configuration to other projects.

Add showing and editing tags VS Code extension

It would be neat if we could add a flag when exporting to pull translations not from the editor stage but "latest" or "production" as this would allow to export e.g. the translations in a production stage as .properties for Java etc.

Currently, there are three options to choose from: "Only default language" "Any language except default" "Any language" The goal of this feature request is to add an option to select one or more specific languages that will trigger the automation.

Currently, reverting many changes in translations or translation keys is a problematic task. The aim of this request is to make it easier, for example, by adding an option in the "Activity" tab to select and revert changes.