11 posts tagged with "tolgee"

We are happy to announce that we released support for Ruby on Rails YAML, Flat YAML, and Structured YAML formats.

We are happy to announce that we finally released tools enabling you to use Tolgee to translate also to iOS, Mac and other Apple platform Apps, Android, Flutter, PHP and C++. Also, you can reliably export to generic formats like Structured JSON with support for arrays or XLIFF.

To provide a convenient way of editing translations for developers, translators, localization managers, project managers and other stakeholders, we made our translation editor visual, so you can conveniently edit plurals and you can edit strings without the need to understand the placeholders or HTML tags syntax.

In June 2023, we released our own Tolgee AI Translator.

It doesn't ignore context like other traditional machine translators, which makes it great for translating especially short texts. Tolgee Translator understands the context of the strings used in your app: that's why it can provide the best results.

Throughout autumn 2023, we refined the translator further, including, for example, the language formality feature. And now, we are taking another step closer to the autonomous software translation, adding a couple of new features, which make the results of Trolgee Translator even more accurate.

We're excited to announce the release of a new feature, AI Translation Customization, so you can improve the translation by providing a description of your project or adding a language-specific note.

Dear Tolgee Users,

In the past year of 2023, Tolgee made a significant step forward, introducing many new features and making the whole project more robust. We must reflect these company and product developments into the pricing to align with the new product state and the company's business targets.

Recently, we've received many requests from our users to simplify the update of translations on production, and now we have an answer. Say Hi to Tolgee Content Delivery, a fast and reliable way to keep your translations independent of your code! Also introducing Webhooks for more automation options.

After a little over 2 years, we decided to freshen up the Tolgee brand, including our logo, website and platform's user interface. We value your suggestions and want to provide the best experience for our users. So, we rolled up our sleeves and gave Tolgee a little refresh to not feel so old-school.

Before I started to work on Tolgee I was used to working with Jira. But I didn't like it much, so I chose YouTrack for project monitoring that time. Now it seems better to move the project management to GitHub, since it's more transparent for developers. Also, there is a kanban board feature on GitHub, so we can move the issues as we were used to in YouTrack, but it's also visible to everyone.

In Q4 of 2021, we planned to finish features like translation memory, automated/machine translating, glossaries or paywall for Tolgee cloud. However, we spent a lot of time on upgrading a website and improving JS integrations. Sadly, we haven't finished any of the features, we wanted to finish before the end of the year. So we have to reflect it in our roadmap. We decided to reschedule everything and target more on the segment of developers than translators. Ladies and gentlemen, we are introducing improved roadmap! 🎉

The i18next library is one of the most popular choices for formatting translations in React applications. We decided, that we want to improve the experience by offering an easy integration with Tolgee. Localization is now uniquely accessible as your translations can be managed through opensource platform, without wasting precious Dev time.

When I started to develop Tolgee for my master thesis about 2 years ago, one of my goals was to provide a localization tool also for developers who would like to use it locally on their machine.

Things were different those days. Tolgee was named Polygloat and the tool was intended to be simplest as possible. So I wanted to keep the tool small, and I didn't want to make users to run separate database server for it. But I also wanted to run the app in cloud, where Postgres is considered "more production ready" choice.