odoo-i18n

Translate and localize Odoo modules with .po/.pot files and i18n CLI.

1|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-i18n-halim-23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odoo-i18n
Source: https://github.com/halim-23/odoo-dev-plugin/tree/main/skills/odoo-i18n
Command: npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-i18n-halim-23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently manage translations and localization for Odoo modules across versions 17.0, 18.0, and 19.0, covering common i18n patterns, RTL support, and multi-language workstreams.

Core Features & Use Cases

  • _() and _lt() usage for dynamic and lazy translations
  • Manage .po/.pot files, translation fields, and CLI export/import
  • Website translations, RTL handling, and troubleshooting common pitfalls

Quick Start

Install the Odoo i18n workflow, export strings with the i18n CLI, translate the .po files, and re-import to apply translations.

Frequently Asked Questions about odoo-i18n

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

FAQPage Schema
How do I translate Odoo modules and manage .po files across versions?

Translate Odoo modules by applying _() and _lt() usage, managing .po/.pot files, and exporting/importing translations via the i18n CLI across versions 17.0, 18.0, and 19.0.

What is the difference between _() and _lt() for Odoo localization?

Odoo localization uses _() for dynamic runtime translations and _lt() for lazy translations evaluated at runtime, ensuring strings are translated in the correct context.

How do I add RTL support to Odoo websites and templates?

Add RTL support to Odoo by imposing requirements for RTL handling within website translations and templates, ensuring correct layout direction for multi-language deployments.

Why are my Odoo translations missing or showing incorrect PO structure?

Missing Odoo translations and incorrect PO structure stem from common pitfalls that require addressing translatable fields and ensuring proper .po file formatting during CLI export/import.

Does the Odoo i18n CLI support exporting and importing translations for multi-language deployments?

The Odoo i18n CLI supports exporting and importing translations, allowing you to extract strings, translate .po files, and re-import them for multi-language website deployments.