Language Management
Adding, editing, and managing languages in your MovaBase projects
Language Management
This guide covers everything you need to know about managing languages in your MovaBase projects, from adding new languages to organizing and controlling their visibility.
Adding Languages
MovaBase supports both standard languages and custom language definitions, giving you flexibility to match your specific needs.
Adding Standard Languages
Standard languages come from a comprehensive database with pre-configured language codes, names, and native names.
Available Language Database
MovaBase includes an extensive list of supported languages with their properties:
| Property | Description | Example |
|---|---|---|
| Code | ISO language code used for identification | en, es, fr, de, ja, zh-Hans |
| Name | English display name | English, Spanish, French, German, Japanese, Chinese (Simplified) |
| Native Name | Name in the language itself | English, Español, Français, Deutsch, 日本語, 简体中文 |
| Emoji | Visual flag or identifier | 🇺🇸, 🇪🇸, 🇫🇷, 🇩🇪, 🇯🇵, 🇨🇳 |
Language codes follow ISO 639-1 standards or common conventions. This ensures compatibility with most translation tools and platforms.
Steps to Add a Standard Language
- Navigate to your project and open the sidebar if not already visible
- Locate the "Languages" section in the sidebar
- Click "Add Language" button
- Search or browse through the available languages list
- Select the language you want to add
- Click "Add" to confirm
Use the search box to quickly find languages by name, code, or native name. This is especially helpful for languages with similar names or codes.
Adding Custom Languages
If you need a language not in the standard database, MovaBase allows you to create custom language definitions.
When to Use Custom Languages
Consider creating custom languages when:
- Your target language has specific regional variations
- You're working with a constructed language or dialect
- You need to support a specialized technical terminology
- The standard language database doesn't include your target
Custom Language Properties
When creating a custom language, you'll need to provide:
| Field | Description | Example |
|---|---|---|
| Code | Unique identifier for your custom language | es-MX, fr-CA, en-US-custom |
| Name | Display name in English | Mexican Spanish, Canadian French, US Custom English |
| Native Name | Name in the language itself | Español de México, Français canadien, US English |
| Emoji | Visual identifier | Any emoji character or flag emoji |
Custom language codes must be unique within your project. Avoid using codes that might conflict with standard ISO codes to prevent confusion.
Setting Default Language
The default language serves as your source or base language in the project.
Understanding Default Language
The default language:
- Is typically your source language where you create original translations
- Often the first language you add to a new project
- Can be changed at any time
- Affects how translations are imported and displayed
Setting or Changing Default Language
To set or change the default language:
- Navigate to the Languages section in your project sidebar
- Locate the language you want to set as default
- Click the "Set as Default" option (usually a star icon or menu option)
- Confirm the change
Only one language can be marked as default at a time. Changing the default language doesn't affect existing translations.
Language Ordering and Organization
You can organize languages in a logical order that makes sense for your workflow.
Default Ordering
By default, languages are ordered by when they were added to the project.
Reordering Languages
- Navigate to the Languages section in project sidebar
- Look for drag handles or ordering controls
- Drag languages to your preferred order
- Changes are saved automatically
Place your default language at the top or a prominent position for easy reference. Group related languages together (e.g., all Spanish variants).
NEEDS_MEDIA
Managing Languages
Once languages are added, you can manage their properties and visibility through the Languages section.
Editing Language Properties
You can modify language properties at any time to keep them accurate and up to date.
Editable Properties
| Property | Can Be Edited | When to Edit |
|---|---|---|
| Name | Yes | When display name needs correction or you prefer different terminology |
| Native Name | Yes | When native name needs updating or correction |
| Emoji | Yes | When you want to change the visual identifier |
| Code | No | Language code is unique identifier and shouldn't be changed |
| Default Status | Yes | Can set a different language as default |
Steps to Edit a Language
- Navigate to the Languages section in your project sidebar
- Find the language you want to edit
- Click the edit button (pencil icon or similar)
- Modify the desired properties in the edit dialog
- Click "Save" to apply changes
Editing a language's properties doesn't affect the translations themselves. You're only changing the language's metadata, not the translation content.
Removing Languages
You can remove languages that are no longer needed from your project.
Before Removing a Language
Consider the following before removing a language:
| Consideration | Why It Matters |
|---|---|
| Translation Progress | How many translations exist for this language |
| Project Status | Is the language in active use |
| Team Communication | Are translators still working on this language |
| Backup | Do you have a backup of translations |
Removing a language permanently deletes all translations for that language. This action cannot be undone unless you have a backup.
Steps to Remove a Language
- Navigate to the Languages section in your project sidebar
- Locate the language you want to remove
- Click the delete or remove button (trash icon)
- Confirm the deletion when prompted
- The language and all its translations will be removed from your project
Language Visibility Controls
MovaBase allows you to show or hide languages in the translation interface without deleting them entirely.
Understanding Language Visibility
Language visibility controls which languages appear in the translation table and editor:
| Visibility State | Effect |
|---|---|
| Visible | Language appears in translation columns and can be edited |
| Hidden | Language is excluded from view but translations remain in project |
Use Cases for Hiding Languages
Showing and Hiding Languages
To toggle language visibility:
- Navigate to the Languages section in your project sidebar
- Find the language you want to show or hide
- Click the visibility toggle (eye icon)
- The language will be shown or hidden accordingly
You can show all languages at once using the "Show All" option, making it easy to reset your view.
NEEDS_MEDIA
Available Languages
MovaBase provides a comprehensive database of standard languages to choose from.
Supported Language List
The language database includes major world languages and regional variants.
Language Categories
Languages are organized into categories for easier browsing:
| Category | Examples | Typical Uses |
|---|---|---|
| Major Languages | English, Spanish, French, German, Portuguese, Chinese, Japanese | Primary target markets |
| European Languages | Italian, Dutch, Polish, Swedish, Norwegian, Danish | European localization |
| Asian Languages | Korean, Vietnamese, Thai, Indonesian, Malay | Asian market expansion |
| Middle Eastern Languages | Arabic, Hebrew, Persian, Turkish | Middle Eastern markets |
| African Languages | Swahili, Zulu, Amharic, Yoruba | African markets |
| Regional Variants | zh-Hans, zh-Hant, pt-BR, es-MX | Specific regional needs |
Popular Languages
The most commonly used languages in MovaBase:
| Language | Code | Native Name | Region |
|---|---|---|---|
| English | en | English | Global |
| Spanish | es | Español | Spain, Latin America |
| French | fr | Français | France, Canada, Africa |
| German | de | Deutsch | Germany, Austria |
| Portuguese | pt | Português | Portugal, Brazil |
| Chinese (Simplified) | zh-Hans | 简体中文 | China, Singapore |
| Chinese (Traditional) | zh-Hant | 繁體中文 | Taiwan, Hong Kong |
| Japanese | ja | 日本語 | Japan |
| Korean | ko | 한국어 | South Korea |
| Arabic | ar | العربية | Middle East, North Africa |
| Hindi | hi | हिन्दी | India |
The language database is regularly updated to include new languages and language variants based on user feedback and needs.
Custom Language Creation
For languages not available in the standard database, you can create custom definitions.
Custom Language Requirements
| Requirement | Description | Example |
|---|---|---|
| Unique Code | Must be unique within the project | my-custom-lang |
| Display Name | English name for identification | Custom Terminology |
| Native Name | Name in the language itself | Custom script or characters |
| Emoji | Visual identifier for UI | Any emoji character or flag |
Best Practices for Custom Languages
Custom languages are project-specific and won't appear in the standard language database. Consider if the language might benefit other users before creating a custom definition.
Language Codes and Names
Understanding the components of language definitions helps you work more effectively with languages.
Language Code Structure
Language codes in MovaBase typically follow these patterns:
| Pattern | Format | Example | Region |
|---|---|---|---|
| ISO 639-1 | ll or ll-CC | es, es-MX | Two-letter with optional region |
| Common Variants | zh-Hans, zh-Hant, pt-BR | Script or country variant | Specific writing system or country |
| Custom Codes | User-defined | internal-dev, legacy-support | Project-specific codes |
Language Names
MovaBase supports multiple name types:
| Name Type | Purpose | Example |
|---|---|---|
| English Name | Display name for all users | Spanish |
| Native Name | Name in the language's script | Español |
| Code | Technical identifier | es |
The English name is shown to all users, while the native name is primarily for reference and context about the language itself.
Language Emoji Selection
Emojis provide visual identification for languages in the interface.
Emoji Guidelines
| Guideline | Description |
|---|---|
| Use Flag Emojis | When available, use country or region flag emojis |
| Use Character Emojis | For languages without flag representation |
| Be Consistent | Similar languages should use consistent emoji style |
| Avoid Ambiguity | Ensure emoji clearly represents the language |
Emoji Examples
| Language | Flag Emoji | Alternative | When to Use |
|---|---|---|---|
| English | 🇺🇸 | 🇬🇧 | Flag or globe |
| Spanish | 🇪🇸 | 🌴️ | Country flag or sun |
| French | 🇫🇷 | 🗼️ | Country flag or tower |
| German | 🇩🇪 | 🍺️ | Country flag or beer |
| Portuguese | 🇧🇷 | ☕️ | Country flag or coffee |
| Japanese | 🇯🇵 | 🗻️ | Country flag or gate |
| Chinese | 🇨🇳 | 🐉️ | Country flag or dragon |
| Arabic | 🇸🇦 | 🕌️ | Country flag or mosque |
NEEDS_MEDIA
Best Practices for Language Management
Project Organization
Team Collaboration
Document your language strategy and conventions in project documentation or team wiki. This ensures all team members follow consistent practices when adding and managing languages.
Workflow Recommendations
| Task | Frequency | Purpose |
|---|---|---|
| Review Language Usage | Monthly | Identify which languages are actively being translated |
| Audit Custom Languages | Quarterly | Verify custom languages are still needed or could be standardized |
| Check Visibility Settings | Weekly | Ensure language visibility matches current project needs |
| Update Native Names | As needed | Correct or improve native language names based on translator feedback |
Troubleshooting
Common Issues
Part 4 of 14: Language Management Complete
Next: Translation Management