Batch operations (GitHub link)
Select as many keys as you want and then tag them, mark them as "Reviewed" or "Translated", auto-translate them, or change their state.
Webhooks (GitHub link)
With webhooks, developers would be able to create their custom automation when project data change without periodically calling the REST API. They will be notified by specific events automatically!
CDN (GitHub link)
Tolgee will automatically upload the exported localization data after every change, so your translations will be always up to date. You will be also able to configure your S3-compatible bucket, so the data stay with you.
All format support (GitHub link)
Tolgee currently works fine with ICU message format and you can import data in .po format. However, there are many more formats we want to support. In this task, we would like to create a universal solution for format support, so we will be able to support any format in the future.
Visual editor (GitHub link)
The current editor helps you with ICU syntax but doesn't help you with placeholders or HTML tags. For many, this is not an issue but it's problematic for example in the Arabic language, where it's hard to mix HTML and Arabic characters.
By visual editor, we mean a nice environment, where tags and parameter placeholders are represented visually, so translators don't have to worry about them. The plurals are also visually represented, so users can edit them without understanding the message formatting language.
Tasks (GitHub link)
Tasks will enhance project management, improve collaboration, and enable better time management for translators. You will easily break down your large project into smaller, more manageable sections which helps translators to prioritize and work more efficiently.
Notifications (GitHub link)
When something changes in your project, users will be notified, if enabled. So you can get your strings translated asap.
Community translations (GitHub link)
Tolgee is currently used by many open source projects, but Tolgee doesn't support a safe way of community translating. It can limit translation permissions to specific users, but the user can then modify all the strings in the language. We need to provide a better way, where the community members would be able to only propose changes, which have to be approved and merged by somebody who is permitted to.
In-context support for mobile apps (GitHub link)
The in-context translating works great with web apps, and we would like to provide the same comfort to mobile developers.
QA Checks (GitHub link)
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.
Backups and data export (GitHub link)
For our subscribers, we would like to provide an automated backups feature, which will enable users to restore their project data to a specific state when something goes wrong. Users will be also able to export all project data including metadata and screenshots and import them later.
Git integrations (GitHub link)
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.
Glossaries (GitHub link)
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.
Translation Memory management (GitHub link)
Management of Translation Memories will to share them between different projects. You will be also able to import and export TMX files, so you can back-up them if you want.
Ordering professional translation (GitHub link)
Looking for a way to localize your product into foreign markets Tolgee will help you with that. With Tolgee, you will easily find the ideal professional translator for your needs.
Translation proxy (GitHub link)
Translation proxy will be a service enabling translation of any website without modifying it's sources or content. It will be especially useful for static websites.
Document formats support (GitHub link)
Support for document file formats like DOCX, PPTX, or HTML will enable you to have them translated with ease.
Design tools integrations (GitHub link)
After the Figma plugin, we would also like to provide developers and localization managers plugins for more design tools like Adobe XD or Sketch.
Branching (GitHub link)
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.
What have we done so far...
Tolgee AI Translator
Tolgee's very own AI Translator, which will be able to translate your content automatically. If used with Tolgee SDK, it will translate more accurately thanks to the context provided by the SDK.
Currently, the permissions are level oriented. You can have MANAGE permission, which enables you to do everything in the project, or EDIT which enables you to manage keys, translations, or screenshots. But what if you want to enable a specific user to only add screenshots? With enhanced permissions users will be able to set granular permissions for each scope like uploading screenshots, adding a key, modifying translations, you name it.
Current cloud pricing model is far from ideal. We are going to:
- charge users by translated strings amount, not by translations slots (including untranslated values)
- introduce Pay as you go model, so users won't be charge for what they actually use without the need for buying a package
- lower the free translation limit to 1000. For current users we keep the current pricing. So don't worry.
Command Line Interface will help users with extracting localization data from the Tolgee platform, analyzing code, looking for new keys, and extracting data in specific formats. Everything mentioned is customizable and flexible!
Namespaces in Tolgee JS integrations
Enable localization data export to be split to multiple files not only by the language but also by their namespace.
New Core of Tolgee JS
The new @tolgee/core package will provide refactored core of all js integrations and cleaner API with enhanced customization reduced bundle size and new features.
To see detailed statistics for the project and for each language.
Enable users to see, how translation was edited in the past.
Translation permissions limited by language
Add an option specifying a particular language a user can translate to.
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.
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.
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.