Tolgee

This is one of the best practical i18n writeups I've seen recently. Oren nails the key insight: i18n is not a feature you ship once. It's a layer that touches everything. A few things that resonated with me: - The AI-first translation workflow (translate with AI, then refine with humans) is exactly the approach we designed Tolgee for - The "do not translate" problem with technical terms is something so many teams discover too late - Japanese word counting breaking toast messages. This is the kind of bug that makes you question all your assumptions Happy to see Tolgee mentioned as the tooling choice here. But honestly, even if you use something else, the lessons in this article will save you weeks of pain. Worth a read if you're planning to go multilingual 👇 Thanks, Oren!

It really happened — one of my dreams came true. I got to organize an event like this 💜 The React Brno meetup was such a joy. I enjoyed every moment and I really hope this becomes a tradition. I’m so grateful to all the speakers! David Chocholatý from Purple Technology, Peter Ševčík from STRV, Jiří K. from Tolgee, and Dan S. from Margelo. For most of them, it was their first talk, and they absolutely nailed it! A big thank you to Purple Technology for hosting. The food was great, the space was lovely, and I truly appreciate the opportunity to organize something like this. And honestly, even though the offices aren’t huge, the cozy vibe made it feel even friendlier and more welcoming. Already excited for the next one ✨

No matter what I do, customer conversations are always the best engine for me. ✨ So speaking with Léa Juskiewenski about the impact Tolgee is having in La Fresque du Climat was very special (spoiler: because that impact is huuuuge). Also, a small personal milestone: this is my first case study published on the Tolgee blog. More to come. 🚀 Topic: How do you manage translations in 40+ languages with a network of volunteers? 🤯 That’s the challenge La Fresque du Climat faced as they scaled their climate education workshops to 2M+ participants worldwide. Their model is community-driven: facilitators run workshops locally and naturally want materials in their own language. But the workflow behind it wasn’t built to scale. Translations lived in Excel files, updates required manual copy-pasting into templates, and rolling out a single change across dozens of languages became nearly impossible. 💥 The turning point came when they moved to a structured, API-first localization workflow with Tolgee. Instead of managing scattered files, they centralized translations, enabled collaboration between translators and reviewers, and connected Tolgee to an internal tool that automatically generates multilingual workshop materials. 🐭 What used to be a bottleneck became an enabler. Faster updates, better visibility, and a system that supports hundreds of contributors. As Léa said, “It really centralized everything for us. We can see that hundreds of translators are working on the same platform.” 💎 📖 I share a link to the full post in the comments.

Translations are one of the most common and trickiest challenges you'll face in day to day projects. Jiří K. from Tolgee will walk us through the traps that catch most devs off guard. Pluralization, parameter order, key reuse, tag interpolation and more. Practical rules you can actually apply.

Tolgee is 5. We grew 2.9x in ARR, shipped 60+ releases and attended 5 developer conferences across Europe. Here is what year five looked like.

People often ask me why we named our company Tolgee and why there is a mouse in the logo. Here’s the explanation. When I was originally working on the localization tool for my master’s thesis, I called it Polygloat. I wanted to play with the word “polyglot” to emphasize that the tool helps your app speak many languages, and “goat” because I wanted some animal in the name. Sadly, Polygoat was already taken by another language software tool. However, people thought Polygloat didn’t sound very nice, so we started looking for another name. We came up with more possibilities, including animal-themed ones like my favorite, “Voca Bull Larry,” or “Langustee,” but none of them were cool enough for us. Then I decided to translate the word “translation” into as many languages as I could. In Estonian, it is “tõlge.” So we just removed the “~,” added another “e,” and that’s how we settled on the product and company name. One of the biggest selling points of Tolgee is its native JS integrations, which let you click a string with a mouse directly in the app and translate it in place. Click with a MOUSE. And that’s how the mouse became the logo and mascot of Tolgee. See the nineties vibe? The original logo, created by Marketa Cizmar, had no tail. Which was later fixed by Zuzana Odstrcilova to the current with-tail form.

Translations Like a Pro with Tolgee As developers, we’ve all dealt with localization (i18n). In the React ecosystem, we usually reach for standard libraries and maintain massive JSON files. But recently, I faced a specific challenge: How can we empower non-technical users to manage translations themselves without needing a developer for every typo or phrasing change? The goal was to create a dedicated panel where users could manage keys and values for different languages independently. While researching various solutions, I came across an impressive open-source tool: Tolgee. Why Tolgee caught my attention:  * Visual In-context Editing: This is a game-changer. By simply holding Alt and clicking on any text in the app, you can edit the translation visually on the spot.  * No More Huge JSON Files: It eliminates the need to keep thousands of lines of translation strings in your frontend source code.  * Self-Hosting & Docker: For teams concerned with data privacy or those facing international access restrictions (like my fellow developers in Iran), Tolgee can be easily deployed via Docker on your own servers with your own database.  * User-Friendly UI: It provides a clean dashboard for translators and product managers to work without touching the code. Of course, no tool is a silver bullet. While Tolgee simplifies the workflow, it’s important to weigh it against other workflows like Transifex or Lokalise depending on the project scale. I’d love to hear from you: Have you used Tolgee before? What’s your current workflow for handling dynamic translations in React or other frameworks? Let’s discuss in the comments! 🔗 Check it out: https://tolgee.io Kurzer Tipp für Entwickler: Ich habe Tolgee entdeckt – ein großartiges Tool für In-Context-Übersetzungen in React-Apps. Besonders hilfreich für die Zusammenarbeit mit Nicht-Entwicklern! #ReactJS #WebDevelopment #i18n #Localization #Tolgee #OpenSource #FrontendEngineering #Docker #SelfHosted #JavaScript #SoftwareArchitecture