• Blog
  • Documentation
  • Courses
  • Changelog
  • AI Starters
  • UI Kit
  • FAQ
  • Supamode
    New
  • Pricing

Launch your next SaaS in record time with Makerkit, a React SaaS Boilerplate for Next.js and Supabase.

Makerkit is a product of Makerkit Pte Ltd (registered in the Republic of Singapore)Company Registration No: 202407149CFor support or inquiries, please contact us

About
  • FAQ
  • Contact
  • Verify your Discord
  • Consultation
  • Open Source
  • Become an Affiliate
Product
  • Documentation
  • Blog
  • Changelog
  • UI Blocks
  • Figma UI Kit
  • AI SaaS Starters
License
  • Activate License
  • Upgrade License
  • Invite Member
Legal
  • Terms of License
    • Adding API Routes
    • Change Authentication strategy
    • Fetching the signed in User
    • Reading a Document
    • Creating a Document
    • Configuring Plans
    • Project Configuration
    • Updating the Navigation menu
    • Adding a new translation string
    • Guarding an API Route
    • Adding Pages
    • Updating the Sidebar menu
    • Require Email Verification
    • Fetching the selected Organization
    • Reading a list of Documents
    • Updating a Document
    • Running the Stripe Webhook locally
    • Branding
    • Setting a Default Language
    • Dark Theme
    • Theming
    • Calling API Routes from the client
    • Deleting a Document
    • Updating the Logo
    • Adding a new language in the Next.js Firebase SaaS Kit
    • Checking CSRF Tokens
    • Passing data from server to client
    • Updating the Fonts
    • Adding Pages
    • Guarding Pages
    • Using Lemon Squeezy instead of Stripe
    • Updating the Favicons
    • Using the Language Switcher
    • Environment variables
    • Detect current Locale
    • Setting up Emails

Adding a new translation string

Adding new translations to your application is easy. This guide will show you how to add a new translation string to your application.

The translations of the application are stored at public/locales/<en>.

We have various translations languages JSON files by default (only in English):

  • public/locales/en/common.json - where we store the common translations
  • public/locales/en/auth.json - where we store the auth translations
  • public/locales/en/profile.json - where we store the profile settings translations
  • public/locales/en/organization.json - where we store the organization settings translations
  • public/locales/en/subscription.json - where we store the subscription settings translations

You can keep adding translations to these files if you wish, or create new bundles for your translations.

Adding a new translation string

Let's say we want to add a new translation string to the common.json file.

  1. Open the public/locales/en/common.json file and add the new translation string:
json
{
"new_translation_string": "This is a new translation string"
}

You can then reference this key in your application like this:

  1. Using the Trans component from next-i18next
  2. Using the useTranslation hook from next-i18next

For example, using the Trans component:

tsx
<Trans i18nKey="common:new_translation_string" />

or using the useTranslation hook:

tsx
const { t } = useTranslation();
const newTranslationString = t('common:new_translation_string');
On this page
  1. Adding a new translation string