g18n-dev

Package Version Hex Docs

Development tools and CLI for the g18n internationalization library for Gleam.

Installation

gleam add g18n_dev@1

Usage

The CLI provides commands to generate Gleam translation modules from various file formats:

Generate from Flat JSON Files

gleam run -m g18n/dev generate

Place flat JSON files in src/<project>/translations/ directory:

{
"ui.button.save": "Save",
"ui.button.cancel": "Cancel",
"user.name": "Name",
"user.email": "Email"
}

Generate from Nested JSON Files

gleam run -m g18n/dev generate --nested

Place nested JSON files in src/<project>/translations/ directory:

{
"ui": {
"button": {
"save": "Save",
"cancel": "Cancel"
}
},
"user": {
"name": "Name",
"email": "Email"
}
}

This format is compatible with popular i18n libraries like react-i18next, Vue i18n, and Angular i18n.

Generate from PO Files (gettext)

gleam run -m g18n/dev generate --po

Place PO files in src/<project>/translations/ directory:

msgid "ui.button.save"
msgstr "Save"
msgid "user.name"
msgstr "Name"

Translation Coverage Report

gleam run -m g18n/dev report

Generate a comprehensive translation coverage report that automatically detects your file format (flat JSON, nested JSON, or PO files) and shows:

gleam run -m g18n/dev report --primary es

Use a specific locale as the primary reference for comparison.

Key Management

# List all translation keys
gleam run -m g18n/dev keys --list
# Find keys with specific prefix
gleam run -m g18n/dev keys --prefix ui.button
# Find unused keys (requires file with used keys, one per line)
gleam run -m g18n/dev keys --unused used-keys.txt

Format Conversion

# Convert translations between formats
gleam run -m g18n/dev convert --to flat # Convert to flat JSON
gleam run -m g18n/dev convert --to nested # Convert to nested JSON
gleam run -m g18n/dev convert --to po # Convert to PO files

Parameter Analysis

# Check for parameter issues across all locales
gleam run -m g18n/dev params --check
# Extract parameters from a specific translation key
gleam run -m g18n/dev params --extract user.greeting

CI/CD Validation

# Validate translations with proper exit codes (perfect for CI/CD)
gleam run -m g18n/dev check # Exit 0 = success, 1 = errors
gleam run -m g18n/dev check --primary en # Use specific primary locale

The check command is designed for automation and will:

Help

gleam run -m g18n/dev help

File Naming Convention

Translation files should be named using locale codes:

Locale codes must be 2 or 5 characters long.

Generated Output

The tool generates a translations.gleam module with functions for each locale:

import my_project/translations
pub fn main() {
let translator = translations.en_translator()
let message = g18n.translate(translator, "ui.button.save")
// Returns: "Save"
}

Supported Formats

Automation & CI/CD Integration

GitHub Actions

name: Check Translations
on: [push, pull_request]
jobs:
translations:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: erlef/setup-beam@v1
with:
otp-version: "26.0"
gleam-version: "1.0.0"
- run: gleam deps download
- run: gleam run -m g18n/dev check --primary en

Pre-commit Hook

#!/bin/sh
# .git/hooks/pre-commit
gleam run -m g18n/dev check --primary en
if [ $? -ne 0 ]; then
echo "❌ Translation validation failed. Fix issues before committing."
exit 1
fi

Build Scripts

# In your build script
echo "Validating translations..."
gleam run -m g18n/dev check --primary en || exit 1
echo "✅ Translations valid!"

Development

gleam run -m g18n/dev help # Show help
gleam test # Run the tests
gleam format # Format the code

Documentation

Further documentation can be found at https://hexdocs.pm/g18n_dev.