You can add new keys in the Tolgee Platform using the Native SDKs, CLI, or REST API. For JavaScript frameworks like React, Angular, Vue, etc, we recommend adding keys using in-context editing, which is part of the Native SDKs.

We recommend using the ICU message format for pluralization. It enables you to render the correct plural forms in every known language.

E.g.

{dogsCount, plural,
  one {Je tu jeden pes}
  few {Jsou tu # psi}
  other {Je tu # psů}}

The `few` variant in the example above is not required in English. However, in the Czech language, providing this form is necessary to display a grammatically correct string for any number.

ICU message format handles this for you.

Tolgee Platform visualizes plurals so users, like translators, do not have to face the ICU syntax.

Tolgee Platform can export visualized plurals to various file formats supporting pluralization, like .po, Ruby .yaml or i18next.

Tolgee currently supports

• Tolgee AI translator

• DeepL

• Google Translate

• Amazon Translate

• Microsoft Cognitive

Team members who care about precise wording can reliably edit the strings directly inside the product using Tolgee Native SDKs and its in-context editing feature.

Users can open the in-context edition dialog by alt+clicing the string in the development mode app.

Even live production applications can be turned to development mode using the Tolgee Chrome plugin.

Such an edit is very simple and reliable because the user knows what string is edited and that they're not editing a different string. Also, they don't have to search for the string in the source code, localization files, or huge localization data sets.

No. In a production environment, you should not use Tolgee as a source for localization data or leak your API key this way.

Instead, you should use data exported as static assets or Content Delivery (CDN).

You can export the data

• using the Tolgee Platform UI

• using the CLI

• using the REST API

• or you can publish the data to the CDN

When your app is live in production, there is no need to use the API key. Your app does not fetch data from Tolgee REST API; instead, it fetches data from static assets or Content Delivery (CDN).

You should never leak your API key. That's why developers should store the API keys in environment files (.env) in the .gitignore file.

Tolgee supports all significant formats storing localization data such as JSON, XLIFF, .strings, .arb, .po and many more. Read about all supported formats here.

When running your app in development mode with the Tolgee Native SDKs, localization data are fetched from the Tolgee REST API. You can edit the strings using the in-context tools, generate screenshots or review translations.

On the other hand, in production mode, Tolgee uses static assets or data published to Content Delivery (CDN). In production mode, no one can modify the app's strings unless they provide their API key using the Tolgee Chrome plugin.

Yes. When conversion to Tolgee ICU placeholders is enabled, you can reuse the exact data for any supported platform.

For example, you can use data created for web applications for your iOS or Android mobile app and vice versa.

You can use your favorite CI/CD tool, such as GitHub Actions or GitLab CI/CD, while embracing Tolgee CLI's pull command or Tolgee REST API's export endpoint to automate data exporting.

Absolutely! When you sign up for Tolgee, you will automatically receive our Free plan, which is limited by the number of hosted words, seats and MT credits.