Feature requests

Add an option to include comments (Code Descriptions) in the exported translations. For example, when working with .xcstrings/xml files, replacing the previous translation file with the export causes Xcode/Android Studio to no longer display comments for the strings. Currently, the workaround is to merge the project's existing file with the updated file using jq or similar tools while preserving the comments field.

We would love to have and additional permission toggle: Mark translations as reviewed (deny / allow) This would give us the flexibility to distinguish our users into translators and reviewers.

Currently, it's hard to track what happens to translation keys once they are renamed or deleted. The goal of this request is to provide users with a clear and simple UI for tracking changes to specific translation keys. We could include information on when a key was imported, last seen, created, renamed, deleted, or deprecated.

Currently project names are restricted to a max of 32 characters. Increase to 64 chars. Background: We have projects that we name according company names. And those names are often longer than 32 characters.

Add an option to grant translators access only to a subset of translations based on tags.

Add extension support for Cursor IDE

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

Add option to replace missing translations with default language translations (like it works in Translation Hosting)

According to the PO Files documentation ( https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html ), keys do not need to be unique. They can be repeated, and contexts in 'msgctxt' are used to differentiate them. The context serves to disambiguate messages with the same untranslated string. It is possible to have several entries with the same untranslated string in a PO file, provided that they each have a different context. This is exactly how the .po file generator in Django behaves; the same translation phrase can appear multiple times in the file under the same ID but with different contexts. We could use namespace to differentiate them or use some other mechanism to do so.

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.