Use Cases

Why Use Algebras CLI?

Algebras CLI is a wrapper for our AI-powered translation engine that simplifies usage for developers. Instead of manually managing translation files or hiring expensive translation services, you can automate the entire process with a few simple commands.

Translating i18n JavaScript Applications

Next.js and React Applications

Translate JSON-based translation files commonly used with next-i18next, react-i18next, and other JavaScript i18n libraries.

What you do:

1. Initialize: algebras init (auto-detects public/locales/en/*.json files)
2. Add languages: algebras add fr es de ja
3. Translate: algebras translate

Example setup:

source_files:
  "public/locales/en/common.json":
    destination_path: "public/locales/%algebras_locale_code%/common.json"

Why this helps: Your JSON translation files are automatically created and maintained. When you add new keys, run algebras update to translate only what’s new, keeping everything in sync.

Vue.js and Nuxt.js Applications

Translate YAML or JSON files used in Vue i18n configurations.

What you do:

1. Configure source files in .algebras.config
2. Add target languages: algebras add fr es
3. Run translations: algebras translate

Why this helps: Supports both JSON and YAML formats commonly used in Vue ecosystems. The CLI handles the file structure automatically.

Svelte and SvelteKit Applications

Translate TypeScript or JSON translation files used in Svelte projects.

What you do:

1. Set up configuration for your TypeScript translation files
2. Add languages: algebras add de fr
3. Translate: algebras translate

Why this helps: Works with TypeScript translation files, maintaining type safety while automating translations.

Angular Applications

Translate XLIFF files used in Angular’s i18n system.

What you do:

1. Configure XLIFF source files in .algebras.config
2. Add languages: algebras add es pt_BR
3. Translate: algebras translate

Why this helps: Native client-side i18n support for Angular’s standard XLIFF format. No need for separate translation management tools.

HTML Files with Embedded Translations

Translate static HTML files or templates that contain translatable content.

What you do:

1. Configure HTML source files
2. Add languages: algebras add fr es
3. Translate: algebras translate (creates index.fr.html, index.es.html, etc.)

Example setup:

source_files:
  "html_files/index.html":
    destination_path: "html_files/index.%algebras_locale_code%.html"

Why this helps: Useful for static sites, email templates, or documentation that needs multiple language versions.

Translating iOS and Android Applications

iOS Applications

Translate .strings and .stringsdict files used in iOS localization.

What you do:

1. Configure your iOS localization files:

   source_files:
     "ios/App/en.lproj/Localizable.strings":
       destination_path: "ios/App/%algebras_locale_code%.lproj/Localizable.strings"

2. Add languages: algebras add fr_CA es_MX ja
3. Translate: algebras translate

Why this helps: Automatically creates the correct .lproj directory structure for iOS. Handles both regular strings and pluralization strings (.stringsdict files).

Android Applications

Translate XML string resources located in values/ directories.

What you do:

1. Configure Android string resources:

   source_files:
     "app/src/main/res/values/strings.xml":
       destination_path: "app/src/main/res/values-%algebras_locale_code%/strings.xml"

2. Add languages: algebras add fr es-ru ja
3. Translate: algebras translate

Why this helps: Creates the correct values-es/, values-fr/ directory structure automatically. Handles Android’s locale code format (e.g., es-rMX for Mexican Spanish).

Flutter Applications

Translate ARB (Application Resource Bundle) files used in Flutter i18n.

What you do:

1. Configure ARB files:

   source_files:
     "lib/l10n/app_en.arb":
       destination_path: "lib/l10n/app_%algebras_locale_code%.arb"

2. Add languages: algebras add fr es de
3. Translate: algebras translate

Why this helps: Flutter’s standard localization format is fully supported. Works seamlessly with Flutter’s code generation for localization.

Mobile App UI Constraints

Ensure translations fit within mobile UI constraints.

What you do: Use the --ui-safe flag: algebras translate --ui-safe

Why this helps: Mobile buttons, labels, and UI elements have fixed widths. The UI-safe mode ensures translations don’t exceed original text length, preventing layout breaks.

Translating Localization Tables in CSV/XLSX Formats

CSV Translation Files

Manage multi-language translations stored in CSV format, where each row is a key and columns are languages.

What you do:

1. Configure CSV source files in .algebras.config
2. Add target language columns: algebras add es de fr
3. Translate: algebras translate

Why this helps: Perfect for non-developers who work with spreadsheets. Content teams can edit translations in Google Sheets or Excel, then use Algebras CLI to sync and translate.

XLSX Translation Files

Work with Excel files for translation management, ideal for teams using spreadsheet-based workflows.

What you do:

1. Configure XLSX source files
2. Add languages: algebras add ja zh_Hans
3. Translate: algebras translate --ui-safe (optional)

Why this helps: Enterprise teams often prefer Excel for translation management. Algebras CLI reads and writes Excel files directly, maintaining formulas and formatting.

Glossary Management from Spreadsheets

Upload and maintain translation glossaries from CSV or XLSX files for consistent terminology.

What you do:

1. Create a glossary CSV/XLSX with terms and translations
2. Upload: algebras glossary push terms.csv --name "Product Glossary"
3. Use in translations: algebras translate --glossary-id your-glossary-id

Why this helps: Maintain consistency across large projects. Financial, medical, legal, and technical terms need precise translations that glossaries ensure.

Backend and Framework Translations

Django Applications

Translate Gettext PO files used in Django’s localization system.

What you do:

1. Configure PO files:

   source_files:
     "locale/en/LC_MESSAGES/django.po":
       destination_path: "locale/%algebras_locale_code%/LC_MESSAGES/django.po"

2. Add languages: algebras add es fr de
3. Translate: algebras translate

Why this helps: Native support for Django’s standard Gettext format. No need to manually edit PO files or use separate translation tools.

Flask Applications

Translate Gettext PO files in Flask projects, similar to Django workflow.

What you do:

1. Set up PO file configuration
2. Add languages: algebras add pt es
3. Translate: algebras translate

Why this helps: Streamlines Flask localization using the standard Gettext approach.

FastAPI Applications

Translate JSON, YAML, or custom format translation files used in FastAPI projects.

What you do:

1. Configure your translation file format (JSON/YAML typically)
2. Add languages: algebras add es fr
3. Translate: algebras translate

Why this helps: Flexible format support works with any translation file structure your FastAPI application uses.

Java and Spring Applications

Translate Java Properties files used in ResourceBundle configurations.

What you do:

1. Configure properties files:

   source_files:
     "src/main/resources/messages.properties":
       destination_path: "src/main/resources/messages_%algebras_locale_code%.properties"

2. Add languages: algebras add es_ES fr_FR de_DE
3. Translate: algebras translate

Why this helps: Java ResourceBundle standard format is fully supported. Works with Spring Boot and other Java frameworks using properties files.

Ruby on Rails Applications

Translate YAML files used in Rails i18n system.

What you do:

1. Configure Rails locale files:

   source_files:
     "config/locales/en.yml":
       destination_path: "config/locales/%algebras_locale_code%.yml"

2. Add languages: algebras add es fr de
3. Translate: algebras translate

Why this helps: Rails standard YAML locale format is automatically handled. Maintains Rails’ nested structure and formatting.

CI/CD Automations

Automated Translation Checks in CI

Ensure translation files are complete and up-to-date before deployments.

What you do: Add algebras ci to your CI/CD pipeline (GitHub Actions, GitLab CI, Jenkins, etc.)

Example GitHub Actions:

- name: Check translations
  run: algebras ci

Why this helps: Catches missing translations before production. Fails the build if new keys aren’t translated, preventing incomplete deployments.

Automated Translation Updates

Automatically update translations when source files change.

What you do:

1. Add translation step to your CI pipeline
2. Run: algebras update --only-missing
3. Commit and push translation files automatically

Why this helps: Keeps translations in sync with code changes automatically. No manual intervention needed when developers add new features.

Pre-Deployment Translation Sync

Ensure all languages are translated and validated before release.

What you do:

1. In your deployment pipeline, run: algebras ci
2. If missing translations found, run: algebras translate --only-missing
3. Fail build if critical translations are missing

Why this helps: Prevents releasing features with untranslated content. Ensures quality and completeness across all supported languages.

Scheduled Translation Updates

Set up scheduled jobs to keep translations updated regularly.

What you do: Create a cron job or scheduled task that runs:

algebras update --only-missing

Why this helps: Keeps translations current even if developers forget to run updates. Useful for active projects with frequent content changes.

Advanced Use Cases

Multi-Framework Projects

Translate projects using multiple frameworks simultaneously (e.g., React frontend + Django backend).

What you do: Configure all source files in .algebras.config:

• React JSON files
• Django PO files
• Android XML files

Run: algebras translate to translate everything at once.

Why this helps: One command handles multiple file formats. All translations stay synchronized across your entire stack.

UI-Safe Translations

Ensure translations don’t break UI layouts by maintaining text length constraints.

What you do: Use --ui-safe flag: algebras translate --ui-safe

Why this helps: Critical for mobile apps and fixed-width UI elements. Translations stay within original length bounds, preventing layout breaks.

Custom Translation Prompts

Provide domain-specific instructions for better translation quality.

What you do:

1. Create a prompt file: custom-prompt.txt
2. Use it: algebras translate --prompt-file custom-prompt.txt
3. Or set default: algebras configure --prompt "Translate maintaining a professional tone"

Why this helps: Get translations that match your brand voice, industry standards, or specific requirements. Better than generic translations.

Batch Processing for Large Projects

Optimize translation speed for projects with thousands of strings.

What you do: Configure batch processing:

algebras configure --batch-size 50 --max-parallel-batches 10
algebras translate

Why this helps: Process large translation jobs faster by running multiple batches in parallel, while respecting API rate limits.

Multiple Source Languages

Support content creation in multiple source languages.

What you do: Create separate config files:

• .algebras.config for English → Spanish, German
• .algebras-zh_Hans.config for Chinese → Korean, Japanese

Use: algebras -f .algebras-zh_Hans.config translate

Why this helps: Platforms with content creators in different languages need flexible translation workflows. Each source language can have its own target languages.

Translation Review Workflows

Generate translations, review them manually, then update incrementally.

What you do:

1. Generate: algebras translate
2. Review: algebras review --language fr
3. Edit files manually as needed
4. Update new content: algebras update --only-missing

Why this helps: AI translations are a great starting point. Review workflows let teams refine translations while still automating the bulk of the work.