README

A PHP package for ensuring proper French typography and consistent terminology in PO translation files. Checks are split into errors (must fix) and warnings (suggestions).

The main idea is to help developers and translators maintain high-quality French translations by enforcing typographic rules and checking for consistency in terminology. The rules of typography are based on the Les règles typographiques utilisées pour la traduction de WordPress.

This package will also allow you to translate missing translations using AI providers: either through the OpenAI API (OpenAI, OpenRouter, Ollama, Deepseek, etc.) or using Claude Code CLI. The translation can be either fully automated or interactive, allowing you to finetune the suggestions, or add them as fuzzy so you can update them in your favorite PO editor. This feature is still in development and needs your feedback.

Features

Multi-Language Support

• Language Auto-Detection: Automatically detects target language from filename (e.g., plugin-de.po → German)
• French: Full typography checking + AI translation
• German, Spanish, Italian, Portuguese, Dutch, Arabic: AI translation only (no typography rules)

Typography Rules (French Only)

• Non-breaking spaces before double punctuation (!, ?, :, ;, »)
• French quotation marks (« ») with proper spacing
• Typographic apostrophes (')
• Proper ellipsis character (…)

Translation Features

• PO file parsing and generation
• Translation consistency checking via glossary (French only)
• Interactive (or not) translation mode with AI integration:
  • OpenAI API (compatible with OpenAI, OpenRouter, Ollama, Deepseek, etc.)
  • Claude Code CLI
• Supports multiple target languages based on filename detection

French Typography Reference

The implemented rules and upcoming are listed in docs/french-rules.md

Installation

composer require youniwemi/translation-checker

Usage

Command Line

Check a French file (typography + potential translation):

vendor/bin/check-translation plugin-fr.po

Check and fix French typography issues:

vendor/bin/check-translation --fix plugin-fr.po

Translate missing translations to German (using default OpenAI engine):

vendor/bin/check-translation --fix --translate plugin-de.po

Translate using Claude Code CLI:

vendor/bin/check-translation --fix --translate --engine=claude plugin-de.po

Interactive Spanish translation:

vendor/bin/check-translation --fix --translate --interactive plugin-es.po

Process multiple files (auto-detects language from each filename):

vendor/bin/check-translation --fix *.po

Language Detection Examples:

• plugin-fr.po → French (typography checking + translation)
• plugin-de.po → German (translation only)
• plugin-es_ES.po → Spanish (translation only)
• plugin-it_IT.po → Italian (translation only)
• plugin.po → French (default, typography checking + translation)

Options:

• --fix Fix issues and save changes
• --quiet Only show errors and warnings (no progress info)
• --no-warnings Only show errors (ignore warnings)
• --translate Translate the missing translations
• --interactive Use interactive mode for translation
• --engine Choose translation engine: 'openai' (default) or 'claude'
• --help Show help message

Messages

Errors (Must Fix)

• "Espace insécable manquant avant les '!'"
• "Utiliser les guillemets français « » au lieu des guillemets droits"
• "Utiliser l'apostrophe typographique (') au lieu de l'apostrophe droite (')"
• "Accent manquant sur la majuscule"
• "Utiliser le caractère unique pour les points de suspension (…)"

Warnings (Suggestions)

• "Le terme 'x' devrait être traduit par 'y'" - Suggests using consistent terminology from glossary

Glossary Review Comments

When using the --fix option, glossary violations are automatically marked with review comments in the PO file:

# glossary-review: 'submission' → 'entrée ou envoi'
msgid "Please submit your form"
msgstr "Veuillez soumettre votre formulaire"

These comments help translators identify and fix terminology inconsistencies directly in their PO editors.

Development

# Install dependencies
composer install

# Run tests
composer test

# Run code style fixer
composer cs

# Run static analysis
composer stan

# Run all quality checks
composer qa

License

MIT License. See LICENSE for more information.

Contributing

1. Fork the repository
2. Create your feature branch
3. Write tests for your changes
4. Ensure tests pass
5. Submit a pull request

All tests must pass and code must follow PSR-12 standards.

Credits and Acknowledgements

This package uses gettext/gettext for PO/MO file parsing and generation.

Environment Variables for Translation

OpenAI Engine (default)

When using the --translate option with OpenAI engine, the following environment variables are required:

• OPENAI_API_KEY: Your OpenAI API key
• OPENAI_API_URL: OpenAI API URL (optional, for custom endpoints, OpenRouter, Ollama, Deepseek, etc.)
• OPENAI_MODEL: Model to use (defaults to 'gpt-3.5-turbo')

Example using Ollama

OPENAI_API_URL=http://localhost:11434 OPENAI_MODEL=llama3 vendor/bin/check-translation --translate plugin-de.po

Example using ChatGPT

OPENAI_API_KEY=your-api-key-here OPENAI_MODEL=gpt-4 vendor/bin/check-translation --translate plugin-de.po

Claude Engine

When using the --translate option with Claude engine (--engine=claude):

• Claude CLI must be installed and available in your PATH
• CLAUDE_MODEL: Optional model name to use (e.g., 'sonnet', 'opus')

Example using Claude

vendor/bin/check-translation --translate --engine=claude plugin-de.po

Example using Claude with specific model

CLAUDE_MODEL=opus vendor/bin/check-translation --translate --engine=claude plugin-de.po