i18n-internationalization

Organize multilingual UI strings in PHP/HTML templates with __(), <lang>, and @lang.

1|Updated Mar 2, 2024
One-click install
npx skills add https://github.com/Aiweline/WelineFramework --skill i18n-internationalization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-internationalization
Source: https://github.com/Aiweline/WelineFramework/tree/main/dev/ai/skills/i18n-internationalization
Command: npx skills add https://github.com/Aiweline/WelineFramework --skill i18n-internationalization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization reduces manual translation effort by providing a simple structure to manage multilingual strings across UI where text is rendered via __(), <lang>, or @lang, and translation mappings live in i18n CSV files.

Core Features & Use Cases

  • Lightweight i18n configuration for PHP/HTML templates using common idioms (__(), <lang>, @lang).
  • Enforces translation file placement: i18n/zh_Hans_CN.csv and i18n/en_US.csv for Chinese and English translations.
  • Supports taglib-friendly attributes and lightweight templating across multilingual interfaces.

Quick Start

Create translation files at i18n/zh_Hans_CN.csv and i18n/en_US.csv, and use __(), <lang>, or @lang in your PHP/HTML templates.

Frequently Asked Questions about i18n-internationalization

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

FAQPage Schema
How do I add internationalization to a PHP application?

To add internationalization to a PHP application, you organize UI strings and templates using translation idioms like __(), <lang>, or @lang in your HTML codebase. This lightweight i18n setup maps multilingual text via CSV files.

What is the best way to manage multilingual strings in HTML templates?

Managing multilingual strings in HTML templates is best handled by using taglib-friendly attributes like <lang> and @lang. These idioms render translated user-visible text by pulling mappings from structured language CSV files.

Do I need specific translation files for PHP localization?

Yes, PHP localization requires specific translation files placed at i18n/zh_Hans_CN.csv and i18n/en_US.csv. Enforcing this file placement ensures your application correctly maps Chinese and English translations.

Can I use lightweight i18n configuration without heavy framework dependencies?

You can use lightweight i18n configuration without heavy framework dependencies because the Skill operates with zero required dependencies. It applies common translation idioms directly across PHP and HTML templates for multilingual interfaces.

Why does my PHP translation not display correctly in the user interface?

Your PHP translation may not display correctly if translation mappings are missing from the required i18n/zh_Hans_CN.csv and i18n/en_US.csv files. Ensure all user-visible text uses the enforced __(), <lang>, or @lang idioms.