nuance – Fakhri Azzouz

In WordPress Arabic localization, the choice between كاتب and مُطوِّر for translating "author" is strictly context-driven. The official WordPress Arabic glossary provides a clear baseline, but real-world usage requires nuance.

Official Rule (WordPress Glossary)

Author → كاتب
في سياق المحتوى الكتابي مثل مقال، صفحة، تعليق..الخ

كاتب is the default, approved translation for “author” when referring to the person who wrote content within WordPress (posts, pages, comments).

When to Use Each Term

Term	Use When…	Example Contexts	Why
`كاتب`	Referring to the writer of content (posts, pages, comments, custom post types)	`كاتب المقالة`، `عرض جميع مقالات الكاتب`، `كاتب التعليق`	Matches the glossary; aligns with Arabic UX expectations for content attribution.
`مُطوِّر`	Referring to the creator of a plugin or theme	`مُطوِّر الإضافة`، `مُطوِّر القالب`	`مُطوِّر` implies “originator/creator of a substantial work” – used outside content authorship. Is also synonym with developer.

Critical Distinction in WordPress Core

WordPress uses contextual strings (_x()) to disambiguate. Always check the msgctxt:

// Content authorship → كاتب
_x( 'Author', 'post author' );           // → كاتب

// Plugin/theme creator → مُطوِّر
/* translators: %s: plugin author name */
__( 'By %s', 'my-plugin' );              // Context: plugin header → مُطوِّر

// Theme author (official glossary)
'Theme Author' → 'مُطور القالب'          // Note: glossary uses مُطوِّر, not مؤلف

🚫 Common Pitfalls to Avoid

Mistake	Why It’s Wrong	Correction
Using مؤلف for post authors	Sounds overly formal; breaks consistency with WP admin UI	Use كاتب
Using كاتب for plugin authors	Understates the technical/creative role	Use مُطوِّر (preferred) or مؤلِّف
Ignoring `msgctxt`	Leads to inconsistent translations across contexts	Always check context in `.pot` files
Translating “Author” without context	Ambiguous; may be post author, plugin author, or book author	Request context from developers or use glossary defaults

✅ Quick Reference Decision Tree

Is "author" referring to…?
│
├─► A person who wrote a post/page/comment? → كاتب
│
├─► The creator of a plugin/theme? → مُطوِّر (glossary-preferred) 
││
└─► Uncertain? → Default to كاتب + flag for review

In WordPress Arabic localization, the choice between أب and الأصل for translating "parent" is strictly context-driven. The WordPress Arabic translation team maintains a consistent convention to avoid ambiguity in UI, code, and documentation.

Note: we use أم instead of الأب, that is “mother” instead of “father” when translating “parent page” as “page is feminine” in Arabic.

Here’s the practical breakdown:

✅ Use `أب` when:

Context	Example Translation	Why
Parent/Child Themes	`القالب الأب`	Mirrors the technical `parent/child` metaphor used in WP theme inheritance. Pairs naturally with `القالب الابن`.
Code/Developer Contexts	`ملف القالب الأب`, `دوال القالب الأب`	Used in dev docs, hooks, or CLI output where the familial metaphor is preserved for clarity.
Term/Theme/Plugin Inheritance UI	`تحديث القالب الأب`	Matches how WP core handles theme relationships.
Page	`صفحة أم`	We use `أم` (mother) as page is feminine

✅ Use `الأصل` when:

Context	Example Translation	Why
Hierarchical Content (Categories, Custom Post Types)	`الصفحة الأصل`, `التصنيف الأصل`, `الأصل` (dropdown label)	`الأصل` implies “root/source/base” in Arabic UX. It’s the standard for content trees.
Menu Structure	`العنصر الأصل`, `الأصل`	Menus use `الأصل` to denote top-level items in nested lists.
Taxonomy/Relationship UI	`اختيار الأصل`, `بدون أصل`	Avoids biological connotations; focuses on hierarchy origin.

🔍 How WordPress Enforces This

WordPress uses contextual translation functions to distinguish these cases. In the source code, you’ll find:

_x( 'Parent', 'child theme' );        // → الأب
_x( 'Parent', 'theme parent' );      // → القالب الأب
_x( 'Parent', 'menu parent' );       // → الأصل

Always check the msgctxt (message context) in .pot files. It’s the single source of truth.

Conclusion

Navigating these subtleties in WordPress Arabic localization demands more than a quick glossary lookup—it calls for deliberate, context-aware investigation. When doubt arises, always check the message context (msgctxt) in source files, cross-reference previously approved translations, and inspect the surrounding code to confirm meaning. Filtering a term across the entire project helps you maintain a consistent, precise translation that respects both the official glossary and real-world user expectations.

Tag: nuance

Beyond the Glossary: Context-Driven Arabic Translations for ‘Author’ and ‘Parent’ in WordPress