Tolgee in-context feature is now available on any production page which is using our integration library! In-context translating brings following advantages:
In this article, I will show you how it works and how to set it up.
In this article, I would like to describe how I optimized our Spring Boot tests to run a bit faster.
Two months ago, I was looking for a solution how to speed up pipeline in our monorepo. As an immediate answer I found basically two alternatives Nx (from Google) and Turborepo as a new cool project from well known opensource author (Jared Palmer). I was immediately drawn towards Turborepo as it was really hyped everywhere. Also, it is quite minimalistic, simple to use and it looked like exact fit for our use-case. So I got into it.
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! 🎉
Most of the information systems using user authentication also work with some kind of avatars - images enabling other users to see who commented, posted or made anything else in the system. When we want to be able to show user avatars, we need to enable users to upload their avatar or generate some default. In this article I am going to show you how to:
jdenticoncropper.js and react-cropper librariesSo you develop an app in React and you want many users to use it, right? To make your app usable for users in foreign countries, you have to translate your App to their languages. 🇬🇧 🇨🇳 🇮🇹 🇪🇸 🇫🇷
In this article, I am going to show you, how to integrate i18next and Tolgee into your project and how easy and fast you can translate a React app using these tools.
Tolgee has also its native integrations. Which are a bit easier to set up, so if you're not used to i18next, maybe it would be easier for you to start with those.
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.
Some time ago I've came across an article about inserting secret text into regular messages using invisible zero-width unicode characters. Now during my work on localization SDKs, I've found quite interesting use case for it.