# Arabic localization — 12 September 2026

The Arabic interface uses concise Modern Standard Arabic suited to construction-marketplace users. It is contextual copy, with consistent equipment, quote, booking, delivery, company and supplier terminology. Legal pages remain translations of the existing drafts, not newly approved policies.

## Implementation

- `components/i18n/arabic-copy.ts`: 2,837 reviewed interface and curated demo phrases, covering the existing Hebrew dictionaries.
- `arabic-extra-copy.ts` and `arabic-kit-copy.ts`: detail-screen gaps, feedback and the developer reference.
- `arabic.ts`: complete dynamic phrases, singular/dual/plural counts, prices, dates, units and search aliases. Official KLIGO branding, plan names, model codes, filenames, IDs, URLs and amounts remain intact.
- `translateCommon` selects Arabic; `InterfaceText` and localized controls render labels. `SeedText` preserves user-authored content. Never run dictionary replacement on submitted data.
- The language menu includes العربية, persists the selected locale and sets document `lang`/`dir`. Maps request Arabic place labels; calendars use Arabic locales. Noto Sans Arabic is the Arabic font, with Tahoma/Arial fallbacks; English/Hebrew keep their existing fonts. External font binaries are not in the ZIP.
- Arabic search includes normalized letter variants and diacritics, familiar equipment aliases, translated categories and locations. Existing IDs and filter values stay canonical. Both messaging searches use the same matching function.
- The demo support assistant routes Arabic delivery, invoice, booking, cancellation, verification and quote questions to the existing pages. Provider prompts also recognize listing and campaign questions. It is a keyword-based demo assistant, not a live support service.

## Validation and boundaries

Arabic regression tests cover dictionary and route-title parity, catalogue copy, plural forms, Arabic search, support intents, rendered registration/customer/provider/supply workflows, RTL tab/map configuration and preservation of user data. Static page rendering was inspected for untranslated text, followed by the existing full regression suite and production build. This is source/render verification; interactive browser and independent human native-speaker review were not performed in this pass.

Before production, confirm server-selected locale and locale persistence across authenticated devices; review the Arabic layout in desktop/mobile browsers, font delivery, zoom, screen readers and keyboard use. Local demo state remains local; this update does not implement the pending backend. Source and component ZIPs are regenerated with these files.

The downloadable photo-guide PDF and developer Markdown documents remain explicitly English technical artifacts; the on-screen guide/reference and print view support Arabic. Attribution names, license identifiers, original source titles, filenames and code samples retain their original forms.