localization-i18n

Configure ERP localization for languages, currencies, time zones, and locale formats.

2|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/erphq/skills --skill localization-i18n-erphq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization-i18n
Source: https://github.com/erphq/skills/tree/main/departments/information-technology/03-org-1k-plus/localization-i18n
Command: npx skills add https://github.com/erphq/skills --skill localization-i18n-erphq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Localization & Internationalization enable ERP applications to operate globally by supporting multiple languages, currencies, time zones, and locale-specific formats across UI, data, and documents.

Core Features & Use Cases

  • Internationalization architecture separates i18n and l10n, uses Unicode UTF-8, and externalizes strings for translation workflows.
  • ICU Message Format support and CLDR-based formatting for locale-aware strings, numbers, dates, and plurals.
  • Multi-language UI, multi-currency handling (functional, presentation, and transaction currencies), timezone-aware display, and RTL/LTR considerations.
  • Locale-aware data modeling for addresses, phone numbers, and statutory reporting templates; end-to-end translation and localization workflow integration.
  • Use case: A global enterprise deploys ERP across DE, JP, BR subsidiaries, translating UI, formatting currencies, and producing locale-compliant reports.

Quick Start

Enable i18n, load locale data bundles, and validate with a sample locale.

Frequently Asked Questions about localization-i18n

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

FAQPage Schema
How do I implement i18n and localization for a multi-country ERP application?

Locale-aware data modeling formats addresses, phone numbers, and statutory reporting templates using CLDR-based locale data integration. It ensures per-entity regulatory compliance across multi-country deployments and diverse user bases.

What is the best way to handle multiple currencies and time zones in an ERP system?

Multi-currency and timezone localization in an ERP system requires handling functional, presentation, and transaction currencies alongside timezone-aware display configurations to ensure accurate global financial and operational data representation.

How does ICU message formatting work with CLDR data for localization?

ICU Message Format support combined with CLDR-based formatting enables locale-aware strings, numbers, dates, and plurals. This integration ensures accurate internationalization across UI, data, and documents for diverse user bases.

Can I use externalized string translation workflows for ERP internationalization?

Yes, internationalization architecture externalizes strings to support end-to-end translation and localization workflows. This allows global enterprises to deploy ERP across subsidiaries while translating UI and producing locale-compliant reports.

Do I need CLDR and ICU support for ERP multi-language UI and RTL layouts?

Yes, CLDR and ICU support are required for multi-language UI and RTL/LTR considerations. They provide the locale-aware string formatting and data integration necessary for global ERP deployments across different language directions.