Feature requests

Add provider gemini

Currently, we offer an import preview feature in the Web UI; however, we could also add a parameter like --preview to CLI to show what changes would be applied to translations in terminal.

Currently, we don't know that type of translation key is until we open the translation row or click to see key settings. The goal of this feature request is to add a badge with translations key row that will indicate what type it contains. You will be able to enable it via "Mini informations" same as "Tags", "Descriptions", "Creation date" etc.

Currently, you have to manually identify translation keys that contain markdown (or should contain it) and change the translation key type to Markdown. With this feature, this configuration could be done at the file format level by adding custom syntax support, such as 'sl:type:markdown', to apply the type to the translation key. We could also skip importing the syntax part and keep only the meaningful translator description, if any. This means we won't be able to export the syntax again, but it probably won't be needed again.

Although there is an option to publish "Translations for customers" this is only applied to the root "_index" file. Not for namespaces. Since all of our translation keys are assigned to a namespace our root "_index" is empty and so are the generate customer "_index_customer-a" files. For each namespace there is a "/namespace-xyz/_index" file generated which contains the translations. But the customer specific file "/namespace-xyz/_index_customer-a" is missing. Because of this, we have to fetch all translations via the API.

Implement a plugin/library/workflow for the native mobile SDK that would allow users to update translations without having to make a full release of their apps. Implementing this feature would likely require to hire Android/iOS developers. Feel free to contact us if you think you can help us with this task.

We could allow users to add custom properties to translation keys and translations, store them in SimpleLocalize, and return them in the output. This feature might simplify some workflows by providing additional context or metadata, making it easier to manage/filter/sort on the client side.

During import and export from the 'Data' tab, verify user access permissions for languages, customers, tags, editing, and other relevant settings.

It would be great if we could choose to only publish selected translation keys to the individual stages.

Add option to the CLI to extract translations from HTML elements that has “data-i18n-key” attribute directly from the URL, list of URLs, or sitemap.