frappe-core-translation

Use when implementing translations/i18n in Frappe v14-v16 apps. Covers _() in Python, __() in JavaScript, CSV translation files, bench commands, string extraction rules, lazy translation _lt(), PO/MO files [v15+], RTL support, and custom app translations. Prevents common mistakes with f-strings, concatenation, and template literals that break string extraction. Keywords: translation, i18n, _(), __(), _lt(), CSV, PO, gettext,, translate my app, multi-language, text not translated, wrong language, how to add translation. bench get-untranslated, RTL, localization.

Ir a la instalación

Repositorio: Impertio-Studio/Frappe_Claude_Skill_Package
Última actividad en el origen: 30 de marzo de 2026 a las 18:20
Idioma detectado de SKILL.md: inglés
Estrellas: 174
Forks: 54

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-translation

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

4 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

Need to translate a string?
├── In Python (.py)?
│   ├── Inside a function/method → _("text {0}").format(val)
│   ├── Module-level constant [v15+] → _lt("text")
│   └── Module-level constant [v14] → define inside function or use lazy
├── In JavaScript (.js)?
│   └── ALWAYS → __("text {0}", [val])
├── In Jinja template (.html)?
│   └── {{ _("text") }}
├── In Vue (.vue)?
│   └── __("text") in <script>, {{ __("text") }} in <template>
└── DocType label/description/option?
    └── Auto-extracted — no _() needed

Where do translations live?
├── v14 → apps/{app}/{app}/translations/{lang}.csv
├── v15+ → apps/{app}/{app}/locale/{lang}/LC_MESSAGES/{app}.po
└── User overrides → Translation DocType (highest priority)

Need to extract untranslated strings?
├── v14 → bench --site {site} get-untranslated {lang} {output}
└── v15+ → bench generate-pot-file --app {app}

Priority	Source	Scope
1	Translation DocType (user overrides)	Per-site
2	MO files (`locale/{lang}/.../{app}.mo`)	Per-app [v15+]
3	CSV files (`translations/{lang}.csv`)	Per-app
4	Parent language (e.g., `pt` for `pt-BR`)	Fallback

Feature	v14	v15	v16
`_()` / `__()`	Yes	Yes	Yes
`_lt()` lazy translation	No	Yes	Yes
CSV translations	Yes	Yes (legacy)	Yes (legacy)
PO/MO (gettext)	No	Yes	Yes
`bench generate-pot-file`	No	Yes	Yes
Babel JS extractor	No	Yes	Yes
Type hints on `_()`	No	No	Yes

File Type	Extractor	What It Finds
`.py`	Babel (AST)	`_("...")`, `_lt("...")` calls
`.js`	Babel tokenizer [v15+] / regex [v14]	`__("...")` calls
`.html`	Regex	`{{ _("...") }}` in Jinja
`.vue`	Same as JS	`__("...")` in script/template
`.json`	DocType parser	Labels, descriptions, options

Pattern	Why It Breaks	Correct Form
`_(f"Hello {name}")`	f-string not extractable	`_("Hello {0}").format(name)`
`_("Hello " + name)`	Concatenation fragments	`_("Hello {0}").format(name)`
`_("Welcome %s") % name`	Old-style not extractable	`_("Welcome {0}").format(name)`
__(`Hello ${name}`)	Template literal not extractable	`__("Hello {0}", [name])`
`_(" Hello ")`	Leading/trailing spaces trimmed	`_("Hello")`
`_("item" if x else "items")`	Ternary inside _()	`_("item") if x else _("items")`
`_(variable)`	Variable not extractable	`_("Known String")`

"source","translation","context"
"Hello","Hallo",""
"Change","Wisselgeld","Coins"
"Change","Wijziging","Amendment"

# Generate POT template
bench generate-pot-file --app {app}

# Migrate existing CSV to PO
bench migrate-csv-to-po --app {app}

# Compile PO to MO (required for runtime)
bench compile-po-to-mo --app {app}

Command	Version	Purpose
`bench --site {site} get-untranslated {lang} {output.csv}`	All	Export untranslated strings
`bench update-translations {lang} {untranslated.csv} {translated.csv}`	All	Import translations
`bench generate-pot-file --app {app}`	v15+	Generate .pot template
`bench migrate-csv-to-po --app {app}`	v15+	Convert CSV to PO format
`bench compile-po-to-mo --app {app}`	v15+	Compile PO to binary MO

# Python
if frappe.utils.is_rtl():
    # Apply RTL-specific logic

// JavaScript
if (frappe.utils.is_rtl()) {
    // Apply RTL-specific logic
}

File	Contents
references/api-reference.md	Full Python _() and JS __() API with all signatures and edge cases
references/csv-and-bench.md	CSV format spec, bench commands, PO/MO workflow, custom app setup
references/anti-patterns.md	Complete anti-pattern catalog with failing and corrected examples

name	frappe-core-translation
description	Use when implementing translations/i18n in Frappe v14-v16 apps. Covers _() in Python, __() in JavaScript, CSV translation files, bench commands, string extraction rules, lazy translation _lt(), PO/MO files [v15+], RTL support, and custom app translations. Prevents common mistakes with f-strings, concatenation, and template literals that break string extraction. Keywords: translation, i18n, _(), __(), _lt(), CSV, PO, gettext,, translate my app, multi-language, text not translated, wrong language, how to add translation. bench get-untranslated, RTL, localization.
license	MIT
compatibility	Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
metadata	{"author":"OpenAEC-Foundation","version":"3.0"}

Task	Python	JavaScript
Translate string	`_("Hello")`	`__("Hello")`
With substitution

name	frappe-core-translation
description	Use when implementing translations/i18n in Frappe v14-v16 apps. Covers _() in Python, __() in JavaScript, CSV translation files, bench commands, string extraction rules, lazy translation _lt(), PO/MO files [v15+], RTL support, and custom app translations. Prevents common mistakes with f-strings, concatenation, and template literals that break string extraction. Keywords: translation, i18n, _(), __(), _lt(), CSV, PO, gettext,, translate my app, multi-language, text not translated, wrong language, how to add translation. bench get-untranslated, RTL, localization.
license	MIT
compatibility	Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
metadata	{"author":"OpenAEC-Foundation","version":"3.0"}

Task	Python	JavaScript
Translate string	`_("Hello")`	`__("Hello")`
With substitution

frappe-core-translation

Opciones de instalación

Revisa los archivos de origen

Frappe Translation / i18n

Quick Reference

Frappe Translation / i18n

Quick Reference

Decision Tree

Translation Priority (Highest First)

Version Differences

Auto-Extracted Strings (No _() Needed)

String Extraction Rules

Anti-Patterns (NEVER Do These)

CSV Translation File Format

PO/MO Files [v15+]

Bench Commands

RTL Support

Custom App Translation Workflow

Adding translations to your custom app:

Reference Files

frappe-core-translation

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Frappe Translation / i18n

Quick Reference

Frappe Translation / i18n

Quick Reference

Decision Tree

Translation Priority (Highest First)

Version Differences

Auto-Extracted Strings (No _() Needed)

String Extraction Rules

Anti-Patterns (NEVER Do These)

CSV Translation File Format

PO/MO Files [v15+]

Bench Commands

RTL Support

Custom App Translation Workflow

Adding translations to your custom app:

Reference Files