i18n-l10n-rules

Enforce i18n/l10n guidelines for locale detection and gettext wiring.

Updated Dec 4, 2025

Search Tags:#i18n #l10n #gettext #locale #.po #.pot #fr_CA

Ready to run

npx skills add https://github.com/jamieadams-nerd/umrs-project --skill i18n-l10n-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i18n-l10n-rules
Source: https://github.com/jamieadams-nerd/umrs-project/tree/main/.claude/skills/i18n-l10n-rules
Command: npx skills add https://github.com/jamieadams-nerd/umrs-project --skill i18n-l10n-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UMRS internationalization and localization guidelines ensure consistent locale detection, translation handling, and policy-compliant terminology across the product, preventing miscommunication and localization errors.

Core Features & Use Cases

Locale detection and priority rules (including fr_CA.UTF-8) to ensure Canadian French outputs are correctly selected.
Gettext wiring, string externalization, and .po/.pot lifecycle for maintainable translations.
TB policy compliance for security labels and bilingual output in government contexts.
Use Case: When delivering multilingual UI, apply these rules to guarantee correct locale resolution and compliant translations.

Quick Start

Configure your environment to generate fr_CA.UTF-8 locale and apply the i18n-l10n rules when creating new strings.

Frequently Asked Questions about i18n-l10n-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure gettext wiring for fr_CA.UTF-8 locale detection?▼

To configure fr_CA.UTF-8 locale detection with gettext, set the required environment variables and apply locale resolution order rules. This ensures Canadian French outputs are correctly selected during multilingual UI delivery.

What is the correct .po and .pot file lifecycle for maintaining translations?▼

The .po and .pot file lifecycle for maintaining translations involves string externalization and gettext wiring. Managing these files correctly ensures maintainable translations across development, QA, and content workflows.

How do I ensure TB policy compliance for bilingual output in government contexts?▼

Ensure TB policy compliance for bilingual output by applying i18n and l10n guidelines to security labels and terminology. This enforces correct translation fidelity and policy-compliant terminology in government contexts.

Do I need to generate fr_CA.UTF-8 locale before starting string externalization?▼

Yes, you need to generate the fr_CA.UTF-8 locale in your environment before starting string externalization. Configuring this prerequisite ensures correct locale resolution and French Canadian terminology handling.

Why does my French Canadian translation output show incorrect locale resolution?▼

Incorrect French Canadian locale resolution occurs when environment variables and locale priority rules are not properly configured. Applying strict locale resolution order rules for fr_CA.UTF-8 fixes the translation output selection.