Feature requests

Currently we see Created: dinsdag, 29 april 2025 at 19:49•Web UI Last seen: dinsdag, 29 april 2025 at 19:49•Web UI We are unable to see who added it from all of our users

Add notifications for: Translations added Translations in language changed status to Needs Review

Gemini is an AI that translates languages well

"It would be nice if you add a Filter "same as default" - that would allow me to see which translations have the same text as the default (such as English), to identify those where I was lazy before (or when the auto translate failed and used the default option)."

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.