Standalone i18n
How to use gt-next as a standalone i18n library
Overview
gt-next has feature parity with many other i18n libraries.
This means that you can use gt-next as a standalone i18n library, without using the General Translation platform.
To do this, simply don't provide any environment variables such as GT_API_KEY or GT_PROJECT_ID.
See our migration guide for more information on how to migrate from another i18n library to gt-next.
Tradeoffs
Using gt-next as a standalone i18n library has some tradeoffs.
Manual translation
You will need to manually translate your app. If you use our platform, we automatically translate your app for you.
If your project only uses dictionaries with the useDict() and getDict() functions,
you'll need to manually translate your dictionaries, as you would with any other i18n library.
Make sure you load your translated dictionaries with the loadDictionary() function.
If your project is using inline translations with the <T> component
or the useGT() & getGT() functions,
you'll also need to manually translate your strings.
Since there are no keys with in-line translations, the CLI tool has a command: gtx-cli generate
which will automatically generate template files for your project. You'll just need to edit the template files with your translations for each language.
Make sure you load your translated strings with the loadTranslations() function.
No development translations
Without an API key, translation hot-reload will not work. Untranslated content will only be rendered in your default language.
How is this guide?