Locale


๐Ÿ“ Description

Manage GetX locale translations with powerful internationalization tools. The locale command provides comprehensive translation management for Flutter applications, including automatic code generation, multi-language support, and advanced features like variable replacement and smart pluralization.


โš™๏ธ Usage

gexd locale <subcommand> [options]

๐Ÿงฉ Aliases

l


๐Ÿ“š Available Subcommands

๐ŸŒ Translation Management

Description: Generate GetX locale translations from JSON files with advanced features

Key Features:

  • ๐Ÿ”‘ Type-safe LocaleKeys - Compile-time safety with generated constants

  • ๐Ÿ”— Variable replacement - Dynamic content with trVars({})

  • ๐Ÿ”ข Smart pluralization - Universal language support with trCount({})

  • ๐ŸŒ Multi-language support - Arabic, English, and 100+ languages

  • โšก Hot reload friendly - Real-time translation updates


๐Ÿš€ Common Usage Patterns

๐Ÿ“„ Basic Translation Setup

๐ŸŽฏ Advanced Multi-language Project

๐Ÿ”„ Development Workflow


๐ŸŽฏ Supported Features

๐Ÿ”‘ Type-Safe Translations

  • LocaleKeys Generation: Compile-time safety for all translation keys

  • IDE Autocomplete: Full IntelliSense support for translation keys

  • Refactoring Support: Safe renaming and deletion of translation keys

๐ŸŒ Multi-Language Support

  • JSON-Based: Simple JSON file structure for translations

  • Nested Keys: Support for hierarchical translation organization

  • Variable Syntax: Both {variable} and @variable formats supported

๐Ÿ”— Dynamic Content

  • Variable Replacement: LocaleKeys.welcome.trVars({'name': 'Ahmed'})

  • Smart Pluralization: LocaleKeys.items.trCount({'count': '5'})

  • Combined Features: Variables + pluralization in single translation

๐Ÿ“ Project Integration

  • GetX Template: Generates to lib/app/locales/translations.g.dart

  • Clean Template: Generates to lib/locales/translations.g.dart

  • Custom Output: Specify your own output location


๐Ÿ“– Translation File Structure

Input Structure (JSON Files)

Example JSON Content

Generated Output


๐Ÿš€ Real-World Examples

๐Ÿ“ฑ Shopping App Translations

๐ŸŒ Multi-Regional App


๐Ÿ’ก Best Practices

๐ŸŽฏ File Organization

  1. Use Locale Codes: en_US.json, ar_SA.json instead of simple en.json

  2. Consistent Structure: Keep the same key structure across all languages

  3. Logical Grouping: Group related translations under common parents

๐Ÿ”ง Development Workflow

  1. Start Simple: Begin with basic translations, add features incrementally

  2. Use --sort-keys: Keep translations organized and version-control friendly

  3. Test Pluralization: Verify plural forms work correctly for each language

  4. Hot Reload: Generate translations during development for immediate feedback

๐ŸŒ Translation Quality

  1. Native Speakers: Use native speakers for translation accuracy

  2. Context Aware: Provide context for translators about variable usage

  3. Plural Forms: Research correct plural forms for each target language

  4. Cultural Adaptation: Consider cultural differences, not just language translation


๐Ÿ”ง Advanced Configuration

Custom Output Locations

Key Naming Conventions


For detailed documentation on locale subcommands:


๐ŸŽฏ Quick Reference

Most Common Commands

Usage in Flutter


Generated automatically by gexd_doc

Last updated