Egyptian WordPress hosting where both sets of digits work.
Arabic content uses Eastern Arabic numerals and Western ones interchangeably. A form validator or a search box that knows only one rejects half your visitors' input.
Two ways to write a number.
Digits are the part of Arabic localisation that everybody forgets, and they appear in every form on the site.
Validation that accepts either set
A phone number or postcode typed in Eastern Arabic digits is entirely valid and fails a validator written for Western ones. Input is normalised before it is checked.
Search that matches across numeral systems
A product code written one way and searched the other returns nothing. Digits are folded to a single representation for matching.
Prices and quantities stored one way
Mixed numeral systems in stored data make sorting and arithmetic unreliable, so storage is normalised even when display is not.
Right-to-left with numbers running the other way
Numerals read left to right inside right-to-left text, which is the most common place a mirrored layout goes wrong.
An origin in the region
Signed-in and checkout requests always reach the origin, and Egypt is well served from within the region.
Valid input, rejected.
A customer types their phone number the way they always write it and the form says it is invalid. There is no error to investigate because nothing went wrong except an assumption.
- Input normalised before validation
- Digits folded for search matching
- Stored numbers normalised to one representation
- Numeral direction handled inside RTL text
The measure is forms that submit.
Speed is not what loses Egyptian orders. A validator refusing digits somebody has written that way their whole life is.
What we change for Egyptian sites
Two numeral systems coexisting in one language touches validation, search and storage separately.
| Setting | What we do | Why |
|---|---|---|
| Input normalisation | Applied before any validation runs | Eastern Arabic digits are entirely valid input that a validator written for Western numerals rejects, giving the customer no way to proceed. |
| Search digit folding | Numerals folded to one representation for matching | A product code written in one numeral set and searched in the other returns nothing, though both spellings are the same number. |
| Numeric storage | Normalised even where display is not | Mixed representations in stored data make sorting and arithmetic unreliable in ways that surface as wrong totals rather than errors. |
| Numeral direction | Handled inside right-to-left text | Numbers run left to right within right-to-left content, which is where mirrored layouts most often break visibly. |
| Origin region | Asia, close to the audience | Egyptian audiences are large and concentrated, and every uncached request travels to wherever the origin actually sits. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why does my form reject valid phone numbers?
Why does search miss a product code?
Should I store numbers in Arabic digits?
What breaks most often in Arabic layouts?
Accept the digits people write.
Move the site to an Asia origin - migration is free, input handling reviewed.