Translation memory will suggest sentences that will have already been translated in your projects before.
Don't translate everything manually. With an automated translations feature, services like DeepL, Google Translate, or AWS translate will help by suggesting or translating your new keys automatically when enabled.
Translating on production
Currently, in-context localization works only when the application is in development mode which is cool, but we would like to enable users to translate directly in the deployed app by providing API key using the Tolgee Tools Chrome plugin.
More export options
More formats (json, xliff) and export options like filtering or structuring will be provided, so exports will be more versatile.
Project Dashboard (In progress)
To see detailed statistics for the project and for each language.
Translation history (In progress)
Enable users to see, how translation was edited in the past.
Translation permissions limited by language (In progress)
Add option specifying a particular language an user can translate to.
To translate the same terms the same way every time, you need to store the terminology to reuse it in the future. Glossaries are the feature that enables you to do that.
Billing on Tolgee Cloud
To generate some profit from providing this great localization tool, we need to enable our users to pay for our services. To do so, we have to implement backend services and UI to bill for our services. If you are self-hosting Tolgee, don't worry. Tolgee stays free for you.
Namespaces/Scoping in Tolgee JS integrations
To support localization data split by namespaces or multi-level scopes.
Design tools integrations
With Tolgee, developers and translators can translate apps very easily. We would also like to provide translators with simplicity by enabling them to translate texts directly in tools like Figma, XD, or Miro.
Support for mobile apps
Tolgee works great with Web apps, and we would like to provide the same comfort to mobile developers.
Even translators make mistakes, but some of these mistakes can be detected, and translators can be notified. No more mistakes like missing tags, missing parameters, or missing punctuation marks.
There are times when it would be great if localization data were synced with your Git repository. Or maybe you would like to create pull requests automatically when translations are changed...
To do this, integrations to GitHub, GitLab, or just support for Git itself will be helpful.
Sometimes you need to maintain multiple versions of your software, so you’ll need to have multiple versions of your localization data stored in Tolgee as well.
Looking for a translator to access foreign markets? Tolgee will help you with this. With the Tolgee Translator Marketplace, there will be nothing easier than finding the ideal translator for your app.
What have we done so far...
After a year and a half of development, we’ve decided to finally release the first official and stable version of Tolgee. Tolgee is now tested and stable, so it's time to celebrate. 🎉🎉🎉
Start to promote Tolgee
Until now, we have been working hard to come up with a product that will satisfy most of the needs of our users. Since Tolgee is now production-ready, and we are going to promote it hard!
Clean and improve UI
Before we released Tolgee V1, we wanted to clean up the UI since we wanted our users to have a great user experience.
Automatic screenshot generation
Context is the most important thing for translators to do their job correctly. We wanted to enable software developers to provide the context to translators without wasting their time. With Tolgee JS SDK and Tolgee Chrome plugin, developers are able to generate screenshots automatically while creating the key in the in-context translation UI.