Skip to content

[I18N] *: Arabic translations - #373

Open
vip6009 wants to merge 2 commits into
odoomates:20.0from
vip6009:20.0-i18n-ar-inventory-reports-user-audit
Open

vip6009 wants to merge 2 commits into
odoomates:20.0from
vip6009:20.0-i18n-ar-inventory-reports-user-audit

Conversation

@vip6009

@vip6009 vip6009 commented Nov 17, 2026

Copy link
Copy Markdown

What and why

Adds i18n/ar.po to the four modules that have no Arabic yet: om_inventory_reports (422 entries), om_inventory_reports_valuation (43), om_inventory_reports_expiry (24) and om_user_audit (145). Translation files only, no code.

  • Built on Odoo's own export of the 20.0 branch, so it follows the modules as they are now.
  • Terms follow Odoo's Arabic for stock and accounting. Every entry is translated, none is fuzzy, and placeholders (%(x)s, %s) are kept.
  • Note: the shipped .pot files lack about 105 strings that Odoo's exporter finds in the code, and the module summary/description strings differ from the manifests. The .po files include them. I can send a regenerated .pot in a separate PR if you want it.

An AI tool helped with the first draft of the translation; it was proofread twice by me.

How to test

  1. Install the module on a fresh database with Arabic loaded.
  2. Switch the user language to Arabic and open the module's menus and reports.

Versions

Branch 20.0. Not applicable to other branches for now.

Checklist

  • The pull request targets the right version branch (20.0).
  • One commit, [I18N] *: Arabic translations, translations of several modules together.
  • No code changed; tests unaffected.
  • User-facing texts are translatable.
  • I have read and follow the AI contribution policy.

vip6009 and others added 2 commits November 18, 2026 14:54
Add i18n/ar.po to om_inventory_reports, om_inventory_reports_valuation,
om_inventory_reports_expiry and om_user_audit (634 entries in all).
@odoomates
odoomates force-pushed the 20.0-i18n-ar-inventory-reports-user-audit branch from 42c5c5e to a265971 Compare November 18, 2026 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants