Ar Php Laravel Laravel Package

Product Decisions This Supports

• Arabic/MENA localization roadmap. Laravel's built-in i18n covers UI strings only. This package supplies the text primitives that __() and lang/ar files do not: Arabic glyph shaping (for PDFs and image rendering), Arabic↔Latin transliteration (slugs, search aliases, name deduplication), Hijri (Umm al-Qura) date conversion, and Arabic number-to-words (Tafqeet).
• Invoice, receipt, and contract generation. Spelled-out amounts in Arabic are a practical compliance expectation for printed invoices and cheques in several GCC markets. Correct Tafqeet — dual forms, gender agreement, currency fractions — is weeks of specialist work and a permanent localization-QA liability. This is the single strongest "buy" argument for the package.
• Hijri-calendar features. Subscription/renewal dates, Ramadan- and Eid-aware notifications, Islamic banking cycles, HR/payroll periods. A scoped feature build avoided.
• Arabic search and data hygiene. Transliteration plus Arabic-aware normalization (hamza/alef variants, tashkeel stripping) measurably improves matching and duplicate detection across spelling variants.
• Build vs buy. The substance lives in the mature upstream ar-php library; this package is a thin Laravel adapter (service provider, facade, config). Buying is cheap. The dependency risk sits upstream, not in the wrapper — so budget for a thin internal abstraction layer rather than for a fork.
• Not a differentiator. This is table-stakes infrastructure for Arabic support, not a roadmap feature. Fund it as a localization enabler inside the Arabic-market initiative, not as a standalone line item.

When to Consider This Package

Adopt when:

• Arabic is a first-class locale and you need at least one of: text shaping for rendered output, Hijri dates, Arabic number-to-words, or transliteration. If you need none of those, you don't need this package.
• You are on PHP ≥ 8.2. Release 3.0.0 explicitly raises the PHP floor and adds Laravel 13 support; a major bump with no feature changelog almost always means a support-matrix drop. Verify the composer.json require block before upgrading — the changelog does not state the exact illuminate/support constraint range.
• You want a low-ceremony integration (facade + config) rather than hand-rolling these algorithms.

Look elsewhere / proceed with caution when:

• You only need translated UI strings. Use Laravel's lang/ar files plus a JS i18n library. Don't take a dependency for __().
• You need modern NLP: stemming, morphological analysis, NER, sentiment, embeddings. Ar-PHP is classical rule-based processing — pair with a real NLP service instead.
• You need shaping or image rendering on a hot request path. It is CPU-bound; benchmark, then move to a queued job or a dedicated rendering service.
• Maintenance signal matters to you. The 3.0.0 changelog is almost entirely Dependabot and CI-tooling noise plus one community PR for Laravel 13. That's acceptable for a thin adapter, but a wrapper whose only recent activity is bots warrants a fallback plan. Put the integration behind your own ArabicTextService interface so you can call ar-php directly, or swap libraries, without touching call sites.
• You haven't cleared licensing. Confirm the license of both the wrapper and the bundled ar-php library against legal requirements before shipping commercially.

Upgrade checklist for 3.0.0:

• Diff PR #56 to see the real support-matrix change (PHP floor, Laravel min/max).
• Confirm whether Laravel 11/12 remain supported; pin to ^2.0 if you're on PHP 8.1 or an older Laravel.
• Run Arabic-output regression fixtures: shaping, Tafqeet edge cases (0, 1, 2, 11, 100, currency fractions), and Hijri boundary dates (month ends, leap years). That's where regressions hide.

How to Pitch It (Stakeholders)

For executives: This is a small, free, open-source adapter that lets our Laravel application handle Arabic properly — correct letter joining, Hijri dates, spelled-out amounts on invoices, and Arabic-to-Latin name conversion. It replaces work we would otherwise build and maintain ourselves, and the grammar-heavy parts are exactly the kind of thing that is expensive to get wrong and expensive to fix later. Release 3.0 is mostly housekeeping plus support for the newest Laravel and a newer PHP, which tells us the project is being kept current. Cost is near zero; risk is low but not zero. Mitigation is one small internal interface so we are never locked in.

For engineering: still-code/ar-php-laravel — a service provider plus facade over ar-php. 3.0.0 adds Laravel 13 support and moves to PHP ^8.2; the remainder of the changelog is Dependabot and CI maintenance, so read PR #56 for the actual support-matrix delta rather than trusting the release notes. The wrapper is thin — the substance is upstream: Arabic shaping, transliteration, Hijri conversion, Tafqeet, and Arabic normalization. Treat shaping and rendering as CPU-bound and keep them off hot paths. Wrap it in our own ArabicTextService interface so an upstream stall or a future library swap costs a day, not a sprint. Gate the upgrade on Arabic-output fixtures, particularly number-to-words and Hijri month boundaries.