Reducing the size of your production bundle can be a significant challenge, particularly when it comes to including unnecessary code. Libraries like React, React Query or Redux include useful developer tools, but they exclude them on production where it would be just an unnecessary bulk. It is not a new problem, but it is hard to do when you don't have a deep knowledge of different build systems. In this article, we'll explore a solution to this problem that involves including developer tools conditionally, based on the environment in which the package is being used.

Software localization is the process of translating software applications and user interfaces to accommodate users in different geographical regions. By doing this, you can expand your market reach and better serve your international customers. Software localization should be part of your overall strategy if you're considering expanding your business into new markets. Yet, it also brings many challenges during the process. In the second part of the article, we'll have a look at how to overcome them successfully and make the software localization process as smooth as possible.

We are proud to share that we have released the new versions of Tolgee Platform v3 and Tolgee JS v5. We have added namespaces support to structure your strings into smaller chunks. The base library of our JS integrations is completely redesigned to be more lightweight end extendable by plugins.

When we did a market analysis in Tolgee, we asked many companies how they solved localization in their project. We asked them what's their i18n tooling. Surprisingly a lot of companies maintain their custom solution. I've also set up f5bot to e-mail me when the i18n keyword appears in posts or comments on Reddit. Again, a lot of people share their custom i18n libraries or solutions. In this article, I want to explain why I recommend against creating your custom solution and show what challenges you will face when you decide to do so.

Our previous article about Machine Translation (MT) discussed the different machine translation providers. We were looking for the answer which one of them is the best. Today, let’s have a look at how machine translations are integrated into Tolgee localization platform and how you can make the best of it.

As a React developer, I have an suspicion to JS classes usage. In React bubble, it feels like a bad practice when I see them somewhere.

However, recently I got a task to rewrite our @tolgee/core, which is VanillaJS, and so far, there have been classes everywhere. I somehow felt it is not right. But then I realized that I don't actually know how to replace classes outside of React. Hmm ...

Machine translation (MT) is the process of using artificial intelligence to automatically translate text from one language to another without human involvement. Over time, from its beginnings in the 1950s, machine translation changed the translation industry. You probably have at least some little experience with machine translations as Google Translate and similar online translator tools have been available around the web for quite some time.

Hacktoberfest is just around the corner and we are happy to participate this year with Tolgee too! Whether you are a coding newbie, programming guru, or not developer at all, there is always a way how to contribute.

Yes, we updated our roadmap again. In the next few months, we are going to work on CLI, enhanced permissions, new Tolgee core, community translations, webhooks, and batch operations.

Localization testing is a software or web application testing procedure designed to ensure the performance of the application and evaluate its different aspects. The behavior of software is tested for specific languages, regions, and cultures. The goal of doing localization testing is to test the linguistic and cultural aspects of specific modules. Localization testing mainly focuses on the content and UI elements of a website.