Glossary · Arabic & RTL

٠١٢٣ and 0123: same values, different characters.

Syrian users read and type both sets of digits, and even the names are tangled: what English calls Arabic numerals, Arabic usually calls something else. Here is what the term means and how an app should treat both.

Updated 19 November 2026Sources checked 16 November 2026Reviewed by Eng. Hasan Kassas

What it means

Arabic-Indic digits are the digit shapes ٠ ١ ٢ ٣ ٤ ٥ ٦ ٧ ٨ ٩, Unicode U+0660 to U+0669. They have the same values as 0 to 9 but are different characters, so software must convert them before calculating or searching. Chrome and Node use them by default for Syrian Arabic (ar-SY).

The names are where people trip. In English, "Arabic numerals" means 0 to 9, and Unicode calls ٠ to ٩ "Arabic-Indic". Arabic often turns this around: ٠ to ٩ are «الأرقام الهندية», the Indian digits, and 0 to 9 are «الأرقام العربية». Both names point at the same history: the digits began in India and reached Europe through Arabic, and each side named them after the people it learned them from. To keep things clear, this page says Arabic-Indic for ٠ to ٩ and Western digits for 0 to 9.

There is a second set. Extended Arabic-Indic digits, U+06F0 to U+06F9 (۰ ۱ ۲ ۳ ۴ ۵ ۶ ۷ ۸ ۹), are what Persian keyboard layouts type. Most look like the first set and a few, such as ۴ and ۶, are drawn differently, but all ten are separate code points. English names for the two sets overlap ("Eastern Arabic numerals" is used for either), so code points are the precise way to talk about them.

Names

What it is called

NameNotes
EnglishArabic-Indic digitsUnicode's name. Also "Eastern Arabic numerals" and, from the Arabic, "Hindi numerals". "Arabic numerals" usually means 0 to 9.
Modern Standard Arabicالأرقام الهنديةThe usual formal name for ٠ to ٩, with 0 to 9 called «الأرقام العربية». Some writers swap the two to match English.
Also heard in Syria«أرقام عربي» and «أرقام إنكليزي»Everyday speech often calls ٠ to ٩ the Arabic digits and 0 to 9 the English ones, the reverse of the formal names.
In code or standardsU+0660 to U+0669, U+06F0 to U+06F9Arabic-Indic and Extended Arabic-Indic digits. A locale tag asks for them with -u-nu-arab, or for Western digits with -u-nu-latn.

An example from a Syrian app

A classifieds app in Latakia asks sellers for a price and a contact number. One seller types the price ١٢٥٠ and the number ٠٩٣٣١٢٣٤٥٦. Another types 1250 and 0933123456. A third, on a Persian keyboard layout, types ۱۲۵۰. To the app these are different strings, yet they mean the same thing.

All of them should end up as the same stored values: the phone number in Western digits and the price as an integer. Our tested parser turns ١٬٢٥٠٫٥٠ (with the Arabic thousands and decimal separators), 1,250.50 and 1250.5 into the same 125050 hundredths, and ۱۲۵۰ into 125000 (tested 16 November 2026). A description that mentions ١٢٥٠ is found by a search for 1250, because the search copy is converted to Western digits too, and the screen can still show the price as ١٬٢٥٠٫٥٠ ل.س.

Defaults

Which digits you get without asking

DigitsWhat we saw
ar-SY in Chrome or NodeArabic-Indic١٬٢٥٠ for 1250
ar-SY-u-nu-arabArabic-Indic١٬٢٥٠٫٥٠ ل.س. as currency
Plain ar in Chrome or NodeWestern1,250 for 1250
ar-SY-u-nu-latnWestern1,250.50 ل.س. as currency
Flutter, intl 0.20.2, locale arWestern1,250.50 with ل.س. as currency
In practice

What to accept, store and show

  • Accept all three sets in every numeric field: Western, Arabic-Indic and Extended. Convert as soon as input arrives; each Arabic-Indic digit is its code point minus 0x0660, each Extended one its code point minus 0x06F0, which is exactly what our tested helpers do.
  • Store Western digits only. Phone numbers, prices, quantities and codes go into the database as 0 to 9, and money as integers, so sorting, totals and duplicate checks behave.
  • Search on Western digits. Convert digits in the same pass as the letter rules, so ١٣ in a listing and 13 in a query meet; see Arabic text normalization.
  • Show digits per locale, on purpose. Pick Arabic-Indic or Western for the Arabic interface, set it explicitly (-u-nu-arab or -u-nu-latn on the web, a fixed format in Flutter), and keep the same choice for prices, dates and counters.
Pitfall

Groups that swap places

One display bug belongs to these digits alone. In our Chrome 157 test on 16 November 2026, the phone number ٠٩٣٣ ١٢٣ ٤٥٦, typed with spaces between the groups and placed in a span with dir="ltr", was drawn with its groups in reverse order. The reader sees the last group first and may copy the wrong number.

The cause is the bidirectional algorithm, which classes ٠ to ٩ as Arabic numbers and lets them pull the spaces between groups toward right-to-left, even inside a left-to-right element. Two fixes passed in the same test: unicode-bidi: isolate-override on the element, or writing the number as one run with no spaces.

FAQ

Common questions

The digit shapes ٠ ١ ٢ ٣ ٤ ٥ ٦ ٧ ٨ ٩ (Unicode U+0660 to U+0669). They mean the same as 0 to 9 but are different characters, so apps convert them before doing anything with the number.

Sources

Where these facts come from

  1. Arabic block chart (U+0600 to U+06FF)Unicode Consortium · accessed 16 Nov 2026
  2. Intl.NumberFormat() constructorMDN Web Docs · accessed 16 Nov 2026
  3. UAX #9: Unicode Bidirectional AlgorithmUnicode Consortium · accessed 16 Nov 2026
  4. intl packagepub.dev · version 0.20.2

Digit output checked with Node 24 (ICU 78), Chrome 157 and flutter test (intl 0.20.2) on 16 November 2026.

Numbers coming out the wrong way round?

Tell us where it happens: a form, a receipt, an SMS. We build Arabic-first apps and will help you find the cause.