Translation Guide

ℹ️ Note: Allinix supports multiple languages thanks to our community contributors like @Cs4K1Sr4C. We welcome improvements and additions to our translations!

Frontend Translation

We use i18next for managing frontend translations. Our translation files are organized by language in the following structure:

> en
> fr
> hu
...
> zh

Each component's translations are namespaced. For example, the ChatWindow component uses the chat namespace.

Translation Structure

Example

Sample translations from chat.json:

{
  "EMBARKING_ON_NEW_GOAL": {
    "en": "Embarking on a new goal:",
    "es": "Embarcándose en un nuevo objetivo:"
  }
}

File Structure

next/public/locales/
├── en/
│   ├── chat.json
│   ├── common.json
│   └── settings.json
├── fr/
│   ├── chat.json
│   ├── common.json
│   └── settings.json
└── ...

Adding a New Language

1. Update i18n Configuration

   i18n: {
     defaultLocale: "en",
     locales: [
       "en",
       "hu",
       // Add your language code here
     ],
   }

2. Add Language Definition

   export const availableLanguages: Language[] = [
     ENGLISH,
     { code: "fr", name: "Français", flag: "🇫🇷" },
     // Add your language here
   ];

3. Create Translation Files

   mkdir next/public/locales/[language-code]
   # Add translations for all namespaces

⚠️ Warning: Server restart may be required for new languages to take effect.

Backend Translation

Model-Based Translation

Backend translations are handled dynamically by the AI model:

• Translations are generated on-the-fly based on user language selection

• New frontend languages are automatically supported

• Limited ability to modify model-generated translations

README Translation

1. Create Translation File

   # In main/docs directory
   touch README.[language-code].md
   # Example: README.zh-HANS.md

2. Add Language Badge

   <a href="https://github.com/Allinix-Labs/Allinix/blob/master/README.[language-code].md">
     <img src="https://img.shields.io/badge/lang-[Language]-blue.svg" alt="[Language]" />
   </a>

Documentation Translation

ℹ️ Note: Our documentation system is currently in an experimental phase. Translation support for documentation is planned for future releases.

Contributing to Translations

If you notice missing or incorrect translations:

1. Submit a GitHub issue

2. Create a pull request with your changes

We appreciate all contributions to making Allinix more accessible globally!