Updated 7 July, 2024
This page brings together basic information about the Arabic script and its use for the Modern Standard Arabic language. It doesn't cover Quranic usage. It aims to provide a brief, descriptive summary of the modern, printed orthography and typographic features, and to advise how to write Arabic using Unicode.
Richard Ishida, Modern Standard Arabic Orthography Notes, 07-Jul-2024, https://r12a.github.io/scripts/arab/arb
المادة 1 يولد جميع الناس أحرارًا متساوين في الكرامة والحقوق. وقد وهبوا عقلاً وضميرًا وعليهم أن يعامل بعضهم بعضًا بروح الإخاء.
المادة 2 لكل إنسان حق التمتع بكافة الحقوق والحريات الواردة في هذا الإعلان، دون أي تمييز، كالتمييز بسبب العنصر أو اللون أو الجنس أو اللغة أو الدين أو الرأي السياسي أو أي رأي آخر، أو الأصل الوطني أو الإجتماعي أو الثروة أو الميلاد أو أي وضع آخر، دون أية تفرقة بين الرجال والنساء. وفضلاً عما تقدم فلن يكون هناك أي تمييز أساسه الوضع السياسي أو القانوني أو الدولي لبلد أو البقعة التي ينتمي إليها الفرد سواء كان هذا البلد أو تلك البقعة مستقلاً أو تحت الوصاية أو غير متمتع بالحكم الذاتي أو كانت سيادته خاضعة لأي قيد من القيود.
Source: Unicode UDHR, clauses 1 & 2
Origins of the Arabic script, 6thC – today.
Phoenician
└ Aramaic
└ Nabataean
└ Arabic
The Arabic script is the 2nd most widely used script after Latin by number of countries, and 3rd by number of speakers (after Latin and Chinese). It used for writing the Arabic language and several other languages of Asia and Africa, such as Persian, Urdu, Azerbaijani, Pashto, Uighur, etc. Historically, it was used far more widely, as its spread followed that of Islam into many countries of not only West and Central Asia, and North Africa, but also Southern and Eastern Europe, South Asia, Malaysia, East Africa, etc.
ألأبجدية ٱلعربية ʔalʔabd͡ʒadiːjaʰ lʕarabiːjaʰ Arabic alphabet
The script was first used to write texts in Arabic, most notably the Qurʼān, the holy book of Islam. It descended from the Nabataean abjad, itself a descendant of the Phoenician script, and has been used since the 4th century for writing the Arabic language.
Many of the languages written in Arabic script are non-Semitic, and so employ very different sound systems from spoken Arabic. As a result the script has had to be adapted and is used slightly differently by speakers of different languages.
More information: Scriptsource, Wikipedia
The Arabic script is an abjad. This means that in normal use the script represents only consonant and long vowel sounds. This approach is helped by the strong emphasis on consonant patterns in Semitic languages (however the Arabic script is also adapted for use with other kinds of language, such as Urdu, Uighur. and African ajami, not all of which are abjads). See the table to the right for a brief overview of the features of Standard Arabic.
Arabic text runs right-to-left in horizontal lines, but numbers and embedded Latin text are read left-to-right.
The script is cursive, and some basic letter shapes change radically, depending on what they join to. It is also very common for adjacent characters to ligate and to stretch to fill available space. Many of the characters share a common base form, and are distinguished by the number and location of dots or other small diacritics, called i'jam. For example, س ش ݜ ݰ ݽ ݾ ڛ ښ ڜ ۺ.
There is no case distinction. Words are separated by spaces (except some very short, usually 1-letter conjunctions and prepositions, which attach to the following word).
Modern Standard Arabic has 28 letters in its alphabet, but regularly uses 8 more. Most of those involve representations of the hamza, for which the usage is complicated. This page also lists 3 letters for foriegn sounds, and 6 others which are used infrequently.
A mandatory ligature has to be used for combinations of lam + alif.
The diacritic 0651 indicates gemination in vowelled text.
❯ basicV
The orthography for the Arabic language is an abjad, and so vowels are written using a mixture of combining marks and letters in vocalised text, but normally the diacritics are not used (and so it is difficult to accurately read the text unless you recognise the consonant patterns). However these diacritics and other phonetic information can be written where needed, and are regularly used for Qur'anic texts, dictionaries, educational materials, and where the pronunciation needs to be made clear.
In vowelled text, the Arabic language uses 3 basic vowel diacritics, but 4 more and 1 letter are occasionally also used. Long vowel locations are marked by matres lectionis (consonants indicating vowel locations).
In vowelled text, 0652 is used to indicate vowel absence in consonant clusters.
Arabic uses both European and native digits, and has local forms for several of the more common punctuation marks.
Because the Arabic script is 'cursive' (ie. joined-up) writing, letters tend to have different shapes depending on whether they join with adjacent letters or not (see cursive). In addition, vowels can be represented using different characters, depending on where in a word they appear.
In scripts such as Arabic, several characters have no left-joining form. In what follows we'll use the characters ي and د to illustrate shapes. The former can join on both sides, but the latter can only join on the right.
Left-joining glyphs are commonly called initial; dual-joining are called medial; and right-joining are called final. Glyphs that don't join on either side are called isolated. However, these glyph shapes can be found in various places within a single word.
Word-initial characters usually have initial glyph shapes (eg. 064A ). However, characters that only join to the right will use an isolated glyph shape (eg. 062F ). Furthermore, words beginning with a vowel are always preceded by a vowel carrier, which is normally ا (eg. 0627 06CC or 0627 064E ).
Word-medial characters will typically join on both sides (eg. 064A ) but those that only join to the right will use a final glyph (eg. 062F ). However, if either of those is preceded by another character that only joins to the right, the glyph shapes rendered will be initial (eg. 064A ) and isolated (eg. 062F ), respectively.
Word-final characters will typically use a final glyph shape (eg. 064A and 062F ). However, if the previous character joins only to the right, they will use isolated glyph shapes (eg.064A and 062F ).
In all this contextual glyph shaping the basic shapes used for a character can vary significantly in a script like Arabic. This also includes some characters that only have ijam dots in certain contexts.
These items only occur in decomposed text.
Click on the sounds to reveal locations in this document where they are mentioned.
Phones in a lighter colour are non-native or allophones. Source Wikipedia.
The above chart is for 'Standard Arabic'. Even so, many regional variants of the standard pronunciation exist, not to mention local dialects.wp
o, oː and e, and eː are sometimes used for foreign words, and are sometimes introduced into speech as allophones due to regional dialects.
In addition, the adjacent consonants can also affect the vowel sounds. In particular, the sound a is retracted to ɑ around a neighboring r, q or emphatic consonants. æ is also a common allophone of a.wp
Most of the phonetic transcriptions for examples in this page therefore just use basic phonemic representations when it comes to vowels.
For more details, see Wikipedia.
Source wp..
The diphthong aj is colloquially pronounced more like ej, however in this page we will continue to transcribe it phonetically per the official pronunciation.
Modern Standard Arabic covers many territories, most of which have their own dialects or languages, and these tend to influence the local pronunciation of Standard Arabic. In the chart above, we remain conservative, only mentioning variants that tend to apply to the standard pronunciation. For a slightly more detailed set of notes, see Wikipedia.
p and v are sometimes pronounced by some speakers for foreign words, such as باكستان فيروس
Sometimes alternative letters are used for such words (see foreign).wp
Although most dialects include it as a phoneme, ɡ is only used in Modern Standard Arabic as a marginal phoneme to pronounce some dialectal and loan words.wp
The sound ɫ occurs as a phoneme in a handful of loanwords, though not in all pronunciations. It also occurs in the name اللّٰه
The sound, d͡ʒ is used in Algerian, Hejazi, Najdi, Iraqi, and Gulf regions, whereas ʒ is used in Moroccan, Tunisian, Egyptian, Levantine, and Israeli regions. In both cases, the sound is written using ج.wp,#Local_variations_of_Modern_Standard_Arabic
ظ is pronounced zˤ in some regions, rather than ðˤ.
Arabic is not a tonal language.
The following notes on structure are taken from Wikipedia.wp,#Phonotactics
[C1] [S1] V [S2] [C2 [C3]]
C
V
S
Arabic syllable structure consists of an optional syllable onset, consisting of one or two consonants; an obligatory syllable nucleus, consisting of a vowel optionally preceded by and/or followed by a semivowel; and an optional syllable coda, consisting of one or two consonants.
The following restrictions apply:
The following table summarises the main vowel to character assigments, in both vowelled and unvowelled forms.
Each table cell shows word-initial, word-medial, and word-final forms from right to left. The glyphs shown are illustrative; alternative shapes may occur (see joining_forms).
Unvowelled: |
|
||||
---|---|---|---|---|---|
Vowelled: |
|
For additional details see vowel_mappings.
Because the sukun is also dropped in non-vocalised text, where a mater lectionis remains it only implies a vowel location, since it may either represent a consonant or a glide.
In word-initial position vowels are attached to ا. However, more often than not, a hamza is also attached to the alef to indicate the glottal stop. Although this actually constitutes a consonant plus vowel, in unvocalised text the alef (plus any hamza) signals the location of a vowel. The table therefore shows these maximal combinations.
The sounds eː, o, and oː are only used for transliterations of foreign words, and are spelled identically to iː u, and uː, respectively.
The letter ى, used as an alternative for a final aː, is a dedicated vowel character (see vletter).
Here is the set of characters described in this section, grouped by general category. Three of the combining marks are only found in decomposed text. The remaining combining marks are not typically used either (see below).
The Unicode Standard makes an important distinction between ijam and tashkil diacritics, which is particularly relevant for this section about vowels. For more information, see Ijam, tashkil, hamza.
Vowels are written using a mixture of combining marks and letters in vocalised text, but normally the diacritics are not used (and so it is difficult to accurately read the text unless you recognise the consonant patterns). However these diacritics and other phonetic information can be written where needed, and are regularly used for Qur'anic texts, dictionaries, educational materials, and where the pronunciation needs to be made clear.
In vowelled text, the Arabic language uses 3 basic vowel diacritics, but 4 more and 1 letter are occasionally also used. Long vowel locations are marked by matres lectionis (consonants indicating vowel locations).
0649 represents aː at the end of many words when it is written with YEH instead of an ALEF. In this case, YEH has no dots below, and this code point produces the requisite shape. It is the only letter used for vowels alone.
حتى
It also produces aː in informal speech for some words that end with nunation (though formally the ending is pronounced -an).
معنى
If any suffix is added, the spelling reverts to the normal alef, eg.
معناهم mæʕnaː-hum
In Arabic, the consonants listed just above may indicate the location of a long vowel, eg. قلوب تاريخ They are always visible, whether or not the text shows vowel diacritics.
ا in word final position commonly either represents a short a, eg.
أنا
or is silent, eg.
رَسْمِيًا
كَتَبُوا
In situations where it is necessary to unambiguously indicate the underlying vowel sounds, short vowels can be expressed using diacritics called harakat, eg. العَرَبِيَّة
However for languages such as Arabic, Persian and Urdu they are typically not used unless there is a particular need to help the reader understand the pronunciation. The previous example would therefore usually be written العربية
On the other hand, when the script is used for some other languages (such as Uighur, Kashmiri, or Hausa), all vowels are shown, as a matter of course. These diacritics are also used in the Qur'an (though not originally), to reduce ambiguity.
The basic short vowel marks in the Arabic language repertoire are:
Although the phonemic distinctions for Arabic involve only 3 vowel sounds, the phonetic realisation often varies with context. For example, vowel_mappings includes e and o sounds, which can be found in a few foriegn loan words.
Tanwin refers to a secondary set of vowel diacritics with origins in classical Arabic, where indefinite nouns, and adjectives were marked by a final n-sound, called تنوين tænwiːn or, in English, 'nunation'. This is indicated by visually doubling the vowel diacritic, but there are precomposed Unicode characters for each combination.
In modern text this is particularly common for adverbs.jm,51
064B is often used in the combination 064B 0627, where the ALEF is silent and the ending is pronounced -an, eg. فَوْرًا
The same applies before ALEF MAKSURA in formal pronunciation (but see also vletter).
أَفْعًى
If it appears as 064E 0629 064B the pronunciation is -atan, eg. عَادَةً
After a final YEH, the pronunciation has an extra j sound,jm,51 ie. -iːjan, eg. رَسْمِيًا
In modern Arabic printing the fathatan may be dropped, but the alef is retained.
The other two diacritics are much less common.jm,51
0670 is used in only a few Arabic words, however they tend to be commonly used words. It represents the sound aː.
هٰذَا
اللّٰه
The 2 diphthongs aj and aw are written using a combination of short a with the semivowels ي and و,wp,#Vowels. In vocalised text this usage can be detected by the presence of sukun, but in non-vocalised text it is not so obvious.
عين
عود
Long vowels are generally distinguished from short vowels by the use of matres lectionis (see matres).
The 5 multipart vowels listed here only appear in vocalised text. Three represent long vowels, where the vowel diacritic is followed by a letter. Two more represent standalone vowels, with alef used as a carrier for the vowel diacritics. Diphthongs and glides are not included here.
Click on the letters for examples.
Standalone vowels at the beginning of a word usually incorporate ا.
In principle, Arabic has very few true standalone vowels, since vowels are nearly always preceded by a glottal stop or other consonant, and in Arabic, unlike many other languages, the glottal stop is phonemic and a distinct letter of the alphabet.
When ا appears without any hamza diacritic at the beginning of a sentence, it may be pronounced a, for the definite article, or i in various other circumstances (ie. there is no glottal stop).
When preceded by another word these sounds are elided, although the spelling remains unchanged.
انتباه
المدير
As just mentioned, many Arabic words begin with a glottal stop followed by a vowel, which can be indicated using the characters listed above. Strictly speaking, they represent consonants, although, like the matres lectionis, they strongly imply the presence of a vowel.
Alef alone or with wasla. When ا appears on its own it represents a vowel that will usually be elided if it doesn't appear at the beginning of a sentence (but the spelling doesn't change). Before ل it is usually part of the definite article and is pronounced a (see also defarticle), and otherwise it is usually pronounced i. Note that Arabic words do not begin with onset clusters, so borrowed words will often add this vowel to the start of the word, but it is also used for various grammatical forms of words.
المدير
اسم
In classical Arabic, this behaviour was indicated using the wasla diacritic, ie. as ٱ. In modern text, however, this is rarely seen.
أنت المدير
ما ٱسمك
Alef with hamza. In the majority of cases, the alef also carries a hamza that indicates that the glottal stop and vowel are always pronounced. The list of characters above shows 4 variant forms of this. أ can be followed by a(ː) or u(ː), whereas i(ː) (and only that vowel) follows إ.
آ represents the sound ʔaː (see alifmadda).
When text is vowelled, 0652 can be used over a consonant to indicate that it is not followed by a vowel sound. Like other vowel diacritics, this is typically not used in modern text, unless it is necessary to clarify pronunciation.
مكتب
This section maps Modern Standard Arabic vowel sounds to common graphemes in the Arabic orthography. Sounds listed as 'infrequent' are allophones, or sounds used for foreign words, etc.
The columns run right to left and indicate typical word-initial, word-medial, and word-final usage. The joining forms shown are illustrative; alternative shapes may occur (see joining_forms). They are also fully-vowelled, although the examples show normal unvowelled usage as well as vowelled.
Click on a grapheme to find other mentions on this page (links appear at the bottom of the page). Click on the character name to see examples and for detailed descriptions of the character(s) shown.
0650 064A
في
0650 064A
حشيش
0625 0650 064A
إيقاف
064F 0648
كتبوا
064F 0648
دودة
0623 064F 0648
أوروبا
0650
بسبب
0650
باكستان
0627 0650
انتباه
0625 0650
إنسان
064F
منذ
064F
كنة
0623 064F
أذن
0650 064A
سكرتير
064F
064F
0623 064F
أكتوبر
064F 0648
064F 0648
بنطلون
0623 064F 0648
أوتيل
064E
شرب
064E
حجر
0627 064E
الآن
0623 064E
أخضر
064E 0627
إذا
064E 0649, only in certain words.
متى
064E 0627
اثنان
0670, only in a few common words.
هذا
0622
آنسة
064E 064A
عين
064E 0648
عود
The following table summarises the main consonant to character assigments.
Stops | |
---|---|
Affricates | |
Fricatives | |
Nasals | |
Other | |
Special |
For additional details see consonant_mappings.
The main Unicode Arabic block contains 153 letters, with 77 more in the extended blocks. As shown in the previous section, only a small subset of those are used to write a given language. The others represent special characters added to the repertoire for one or other of the many languages for which the Arabic script is used.
The vast majority of letters represent consonants. A few represent long vowels.
The following consonant letters are those generally recognised as constituting the list representing what is called the 'alphabet' for the Standard Arabic language.
The recognised alphabet also includes 0627, although that is generally used in the context of vowels (see alef). 0648 and 064A can also represent long vowel locations or combinations of consonant plus vowel (see matres).
Besides those that are listed as part of the alphabet, other Unicode letters regularly used in Arabic include:
Most of the above letters with diacritics decompose in Unicode Normalization Form D (NFD), however 0629 does not.
The following describe basic letters that require some more lengthy description.
Formally speaking, 0627 has no sound of its own. It is really a vowel lengthener and carrier. Its main uses in arabic orthography are:
as a carrier letter for a word-initial vowel, eg.
الآن
انتباه
as a lengthening sign for the a-vowel, eg. بارد
as a carrier letter for the hamza (see 0623, 0625, 0622, and 0671).
That said, its presence usually indicates the location of a vowel.
It also has one or two minor functions such as in conjunction with tawiin (nunation) (see 064B).
Certain parts of the arabic verb end in a long u-vowel that is conventionally written with a following alef that has no effect on pronunciation, eg. كتبوا ktbwɑ kætæbuːThe alef is omitted if a suffix is added, eg. كتبوها ktbwhɑ kætæbuː-haa
0621 represents the glottal stop sound. For historical reasons, it is treated as an orthographic sign rather than as a letter of the alphabet. It sometimes stands alone, but usually appears with a 'carrier' letter - ALEF, WAW, or YEH for which separate precomposed characters are available in Unicode ( أ إ ؤ ئ ). Examples of use include أنكر نائم بناء
In modern printed arabic, the hamza is rarely shown when it occurs at the beginning of a word, but may appear in conjunction with another character. When the hamza is above another character you should typically use 0654 with the appropriate base character, although there are a number of exceptions, and for the Arabic language all the needed combinations are available as precomposed characters. For more details, see the character description.
Classical arabic distinguishes between 'cutting' and 'joining' hamza. 'Cutting' means always pronounced, 'joining' means frequently elided. The joining hamza is of little practical importance in modern arabic pronounced without the old case endings. When it does appear in modern Arabic, 0671 is used to indicate a joining hamza.
0622 is used when either of the two following combinations of glottal stop and a vowel appear in a word:
ʔaʔ (hamza, short a, hamza) eg. آثار
ʔaː (hamza, long a) eg. القرآن
Normal pronunciation in both cases is ʔaː.
The madda sign is still very often shown in print.
ة usually has no sound, eg. مَدْرَسَة
However, it is sometimes pronounced t in specific grammatical contexts.
It is used for historical reasons to indicate the feminine ending, a, and is only used in final position. The dots are borrowed from 062A. If any suffix is added, the ending is spelled with that letter, eg.
مَدْرَسَتْنَا
In modern Arabic it is not uncommon to find the two dots omitted, particularly on masculine proper names that have the feminine ending, eg.
طلبه
Vowelled text may omit the short a diacritic before the TEH MARBUTA, because the sound is always the same.
The following characters are not part of the standard Arabic language set but are occasionally used to represent foreign sounds.
Two of the above are borrowed from Persian/Urdu.
The following characters also have the general property of Letter, but are less commonly used for modern Arabic language text.
06A2 and 06A7 are alternative forms that are used in Northwest Africa. 08B2 is used for Berber.
0671 is described in the section hamza. Whereas many of the above letters with diacritics decompose in Unicode Normalization Form D (NFD), this letter does not.
0640 is used to stretch words for simple justification, or to make a word or phrase a particular width, or as a form of emphasis. For more information see justification.
Characters in the Arabic Presentation Forms blocks should not normally be used, but they contain just a few characters that are not just for compability use, including the following, which have compatibility decompositions but which are sometimes used as regular characters. See also presentationForms.
FDF2 is used to write the name of Allah. The composition of this character differs from font to font in terms of glyph forms. With some fonts it is necessary to add diacritics, whereas with others it is not.
The other characters represent honorifics or common phrases. Click on the character glyphs in the list above for descriptions.
The pronunciation of ال (alif followed by lām) varies when it represents the Arabic definite article.
The lām is not pronounced if it precedes one of the following characters, but instead the following sound is doubled, eg. السلام علیکم
These are called 'sun letters' in Arabic. The other letters are 'moon letters'.j,32
The alif is also not pronounced if the preceding word ends with a vowel or h. It is, however, written.j,32
No special features are used for syllable onset clusters, other than the sukun in vowelled text.
Final consonants in Arabic are simply written using ordinary consonant letters.
Consonant clusters in Arabic are simply written using a sequence of consonant letters. In vowelled text the consonant(s) without a following vowel may carry a sukun (see novowel).
The diacritic 0651 doubles the value of the consonant it is attached to, which is phonemically significant in Arabic, eg. تجّار
Like the short vowels, it, too, is not often used, although sometimes it appears when vowel signs don't.
When both shadda and kasra are attached to the same base consonant, a common, though not universal, practice is to display the kasra below the shadda, rather than below the base consonant, eg. مُمَثِّلْ Some fonts, such as Amiri, don't do this. (See also gpos.)
This section maps Modern Standard Arabic consonant sounds to common graphemes in the Arabic orthography. Sounds listed as 'infrequent' are allophones, or sounds used for foreign words, etc.
The right-hand column shows various joining forms.
Click on a grapheme to find other mentions on this page (links appear at the bottom of the page). Click on the character name to see examples and for detailed descriptions of the character(s) shown.
Used only for foreign words.
0628
باريس
062806280628 ⏴
067E
پاريس (from Persian/Urdu).
067E067E067E ⏴
0628
بيت
062806280628 ⏴
062A
تلك
062A062A062A ⏴
062F
ديوان
062F062F ⏴
0637
طريق
063706370637 ⏴
0636
ضمان
063606360636 ⏴
0643
كيف
064306430643 ⏴
0642
قدم
064206420642 ⏴
0621
بناء
0621 ⏴
0622
آب
06220622 ⏴
0623
أول
06230623 ⏴
0625
إدارة
06250625 ⏴
0624
رؤوس
06240624 ⏴
0626
رئيس
06260626 ⏴
Used only for foreign words.
0686 (from Persian/Urdu)
068606860686 ⏴
062C
جبل
062C062C062C ⏴
0686 (from Persian/Urdu) in Egypt for foreign names.
چاكارتا
068606860686 ⏴
0641
فقيد
064106410641 ⏴
Used only for foreign words.
0641
064106410641 ⏴
06A4 (not in the Arabic alphabet)
ڤيينا
06A406A406A4 ⏴
062B
ثلاثة
062B062B062B ⏴
0630
ذَاتِيَّة
06300630 ⏴
0638
ظلام
063806380638 ⏴
0633
سنة
063306330633 ⏴
0632
زيارة
06320632 ⏴
0635
صحيفة
063506350635 ⏴
Regional variant. See ðˤ.
0634
شمس
063406340634 ⏴
Regional variant. See d͡ʒ.
062E
خلال
062E062E062E ⏴
063A
غابة
063A063A063A ⏴
062D
حتى
062D062D062D ⏴
0639
على
063906390639 ⏴
0647
هناك
064706470647 ⏴
0645
منذ
064506450645 ⏴
0646
نحو
064606460646 ⏴
0648
واسع
06480648 ⏴
0631
رؤوس
06310631 ⏴
0644
لحم
064406440644 ⏴
064A
يَمّ
064A064A064A ⏴
Sources: Wikipedia, and Google Translate.
Characters in the Arabic Presentation Forms blocks that are not just for compability use include the following. Click on the characters in the list for more information.
See also presentationForms.
Other characters in the Arabic Presentation Forms blocks that are not just for compability use include the following symbols that can be used for pedagogical purposes. In educational materials there is sometimes a need to show pictures of the dots and marks used to distinguish Arabic characters, particularly the ijam. These code points provide for that use case. They are never used as combining marks, nor in composition with Arabic letter forms, but are simply symbols.
See also presentationForms.
The combination 0644 0627 is always written as a ligature. The underlying code points are, however, preserved. The form of this ligature that joins to the right is لاand unjoined it is لا
Observation: When diacritics are used with this ligature, they sometimes appear to be over the ALEF, rather than over the LAM, eg. قليلاً This would require a typing order that is different from the spoken sequence.
Other combinations of characters are likely to also ligate (see gsub). The number of ligatures in text typically depends on the font used, but ligation can also be used as a device to manage justification, in which case it needs some degree of manual control
Modern Arabic text makes use of a relatively large set of invisible formatting characters, especially in plain text, many of which are used to manage text direction. Descriptions of these characters can be found in the following sections:
The code points in the Unicode blocks Arabic Presentation Forms-A and Arabic Presentation Forms-B provide positional forms of Arabic letters and ligatures. They should not be used for ordinary text. Those code points are provided for compatibility with legacy code pages, and have (compatibility) character decomposition mappings. Normally, Arabic text should be written with code points from the main Arabic block and its extensions; positional forms are dealt with by the font and rendering algorithms.
However, there are some exceptions to this rule, which are listed here. These characters are not included in the Unicode repertoire for compatibility but may be used in Arabic texts, in their own right.u,398-400 They normally don't have character decomposition mappings. (See also Arabic ‘presentation form’ exceptions.)
The useful code points include the following:
In addition to the honorifics described earlier, the basic Arabic block has a small number of corresponding combining marks. Click on the characters in the list below for more details.
In the Persian orthography different sequences of Unicode characters may produce the same visual result. Here we look at those, and make notes on usage.
Unicode support for the various uses of the hamza is complicated.u,384 In general, the Unicode Standard recommends to use 0654 in combination with a base character. However, there are a few exceptions to consider.
A number of combinations with the hamza diacritic can be represented as either an atomic character or a decomposed sequence, where the parts are separated in Unicode Normalisation Form D (NFD) and recomposed in Unicode Normalisation Form C (NFC), so both approaches are canonically equivalent. These include the following:
The single code point per vowel-sign is the form preferred by the Unicode Standard and the form in common use for Arabic language text, but either could be found.
When typing and in storage, combining marks always follow the base character they are associated with.
In principle, if more than one combining mark appears on the same side of the base character, Unicode expects applications to render the marks such that those marks closer to the base character in memory appear closer to the base character when rendered. (This is called the inside-out rule
.) However, due to the reordering applied by the Unicode normalisation forms, some of the Arabic script diacritics end up in an inappropriate order on display.
For example, if a user types the sequence of characters in fig_amtra, the order of the marks will be changed such that applying the inside-out rule would render the shadda above the vowel (which is incorrect). (In fact, most application renderers have special rules to correct this.)
The Unicode Standard formally addresses this anomaly in the Technical Annex Unicode® Arabic Mark Rendering (AMTRA), with a set of rules for how to render sequences of Arabic characters. The rules generally move shadda, hamza, round dots, etc. so that they are close to the base character.
User input | Post-normalisation output |
---|---|
بُّ ب ّ ُ |
بُ͏ّ ب ُ ّ |
In the rare exceptions where the AMTRA rules should not change the rendering, this can be achieved by placing an invisible 034F character between the combining marks. (In fact, this is what was done to simulate the incorrect appearance in fig_amtra, because otherwise the browser rendering engine would have automatically produced the same output as in the first column. Clicking on the example will show the sequence used.)
See type samples.
A set of arabic-indic digits are typically used in Middle Eastern and Gulf countries, whereas North African countries tend to use European digits. In neither area, however, is one digit style used exclusively.
The Unicode bidi_class
property for these native digits is Arabic_Number
, which makes them behave differently from ASCII digits, and differently from the set of extended digits used for Persian, Urdu, etc. For more information, see expressions.
Arabic script has its own number separators, which are used in Arabic language text when the non-European digits are used. They are ٫ and ٬.
Arabic also has its own characters for ٪, ؉. The ASCII % and ‰ are also used.
The CLDR standard-decimal pattern is #,##0.###
. The standard-percent pattern is #,##0%
or #,##0٪
.c
See also expressions about directional implications for handling expressions or sequences of numbers.
Extended-Arabic digits. Still in the basic Unicode Arabic block, as mentioned, there is a second set of digits in Unicode for use in languages such as Persian and Urdu.
The glyph shapes are typically different for 3 of the digits (although not always the same 3 digits) in Persian, Urdu and Sindhi.
Arabic | |
---|---|
Persian | |
Urdu | |
Sindi |
Unicode has a character for the rial:
Arabic script text is written horizontally and right-to-left in the main but, as in most right-to-left scripts, numbers and embedded text in other scripts are written left-to-right (producing 'bidirectional' text).
The Unicode Bidirectional Algorithm automatically takes care of the ordering for all the text in fig_bidi, as long as the 'base direction' (ie. the surrounding directional context) is set to right-to-left (RTL).
Characters are all stored in the order in which they are spoken (and typed). This so-called 'logical' order is then rendered as bidirectional flows by the application at run time, as the text is displayed or printed. The relative placement of characters within a single directional flow is based on strong directional properties (RTL or LTR) assigned to each Unicode character by the Unicode Standard. There exist, however a set of neutral direction property values, mostly for punctuation, where the placement of characters depends on the base direction.
Show default bidi_class
properties for characters in this orthography.
If the base direction is not set appropriately, the directional runs will be ordered incorrectly as shown in fig_bidi_no_base_direction, making it very difficult to get the meaning.
In some circumstances the Unicode Bidirectional Algorithm requires additional assistance to correctly render the directionality of bidirectional text. For such cases the Unicode Standard provides invisible formatting characters for use in plain text. See directioncontrols.
In HTML the base direction and higher level controls can be set using the dir
or bdi
attributes. CSS should not be used to control direction. Unicode formatting codes should also not be used where markup is available.
For more information about how directionality and base direction work, see Unicode Bidirectional Algorithm basics. For information about plain text formatting characters see How to use Unicode controls for bidi text. And for working with markup in HTML, see Creating HTML Pages in Arabic, Hebrew and Other Right-to-left Scripts.
For authoring HTML pages, one of the most important things to remember is to use <html dir="rtl" … >
at the top of a right-to-left page, and then use the dir
attribute or bdi
tag for ranges within the page, but only when you need to change the base direction. Also, use markup to manage direction, and do not use CSS styling.
For other aspects of dealing with right-to-left writing systems see the following sections:
Unicode provides a set of 10 formatting characters that can be used to control the direction of text when displayed. These characters have no visual form in the rendered text, however text editing applications may have a way to show their location.
202B (RLE), 202A (LRE), and 202C (PDF) are in widespread use to set the base direction of a range of characters. RLE/LRE comes at the start, and PDF at the end of a range of characters for which the base direction is to be set.
In Unicode 6.1, the Unicode Standard added a set of characters which do the same thing but also isolate the content from surrounding characters, in order to avoid spillover effects. They are 2067 (RLI), 2066 (LRI), and 2066 (PDI). The Unicode Standard recommends that these be used instead.
There is also 2068 (FSI), used initially to set the base direction according to the first recognised strongly-directional character.
061C (ALM) is used to produce correct sequencing of numeric data. Click on the character name, and see also expressions for details.
200F (RLM) and 200E (LRM) are invisible characters with strong directional properties that are also sometimes used to produce the correct ordering of text.
For more information about how to use these formatting characters see How to use Unicode controls for bidi text. Note, however, that when writing HTML you should generally use markup rather than these control codes. For information about that, see Creating HTML Pages in Arabic, Hebrew and Other Right-to-left Scripts.
This section is about sequences of numbers, rather than a sequence of digits. Sequences of numbers are sets of numbers separated by punctuation or spaces, such as 10–12–2022. Sequences of digits, such as 123, in Arabic text run LTR automatically.
A sequence of numbers used to express a range of values generally runs right to left in the Arabic language (and languages using the Thaana or Syriac scripts), whereas for Persian language text (and in Hebrew, N’Ko or Adlam scripts) it runs left to right.
This also tends to apply to expressions such as 1 + 2 = 3.
fig_range_ar shows Arabic text which is right-to-left overall, containing an ASCII-digit numeric range that is also ordered RTL, ie. it starts with 10 on the right and ends with 12 on the left.
In Persian, however, the sequence would generally run LTR, so 10 would be on the left, and 12 on the right. The underlying order of the characters that make up the expression, and the order in which they are typed, remain the same. (Click on each figure to see the underlying character sequences.)
However, the preferred order for a sequence of numbers may also depend on the context. For ISBN numbers, telephone numbers, and so forth, a left-to-right sequencing is likely to be preferred.
The default direction for a sequence in an application that implements Unicode fully will depend on:
The table below shows default sequence orders for Arabic text, with separators drawn from 4 different Unicode bidi_class
properties. The base direction in all cases is RTL. The coloured items are LTR sequences; the black sequences run RTL.
The ASCII digits have the bidi property European_number
, and the Arabic digits have the property Arabic_number
.
If you add spaces after any separator (such as the solidus on the right), the order will be RTL, per the left-hand column.
bidi_class | White_Space | Other_Neutral | European_Separator | Common_Separator |
---|---|---|---|---|
Includes: | ASCII space, and 15 others | Hyphen (U+2010), en-dash, and 5,500+ other code points | Hyphen-minus (U+002D), minus sign, plus sign, +9 more | Solidus, Arabic comma, comma, full stop, colon, nbsp, +9 more |
Bare ASCII | 12 34 56 | 12‐34‐56 | 12-34-56 | 12/34/56 |
Bare native | ١٢ ٣٤ ٥٦ | ١٢‐٣٤‐٥٦ | ١٢-٣٤-٥٦ | ١٢/٣٤/٥٦ |
ASCII after Arabic | ن 12 34 56 | ن 12‐34‐56 | ن 12-34-56 | ن 12/34/56 |
Native after Arabic | ن ١٢ ٣٤ ٥٦ | ن ١٢‐٣٤‐٥٦ | ن ١٢-٣٤-٥٦ | ن ١٢/٣٤/٥٦ |
Changing the direction of the bare ASCII digits with ASCII hyphen. If you have a line that only contains digits the direction for the sequences varies, depending on whether the digits are ASCII (European_Number
) or Arabic (Arabic_number
).
If you want the ASCII digit sequence to run RTL (eg. for a range) you need to start the line with the formatting character 061C (ALM). This is effectively an invisible Arabic script character. The required order cannot be achieved by simply setting the base direction, nor by using 200F. It has to be ALM.
An alternative would be to use ‐ U+2010 HYPHEN or 2013 instead, since they have a different bidi class.
Making other sequences run LTR. Sequences using most other separators, such as the non-ASCII hyphen, run RTL by default in RTL text. This is appropriate for ranges in Arabic, but not for ISBN numbers, telephone numbers, etc. To make these run LTR, you can either precede the sequence with a 200E (LRM), or set the base direction of the sequence to LTR using markup or formatting characters.
Making Common_separator
sequences run RTL. Sequences separated by commas (ASCII and Arabic), full stops, colons, and no-break spaces run LTR and are resistant to change. The direction cannot be changed using RLM or by changing the base direction. Which means that, for example, if you want the components of numeric dates to be ordered RTL, you should avoid using these separators. (Although, surrounding the separators by a space would produce the RTL direction, eg. compare 12/34/56 and 12 / 34 / 56, where the only difference is the addition of spaces.)
Alphanumeric sequences. Some sequences, such as MAC addresses, contain a mixture of numbers and letters. The strong directionality of the letters influences the resulting order, and so these sequences are best managed by explicitly setting the base direction.
Although we are describing Arabic here, it may also be useful to include data for Persian to allow for comparison.
This table is the same as the Arabic table, except for the cell that is the junction of European_separator
and native Arabic digits. This is because the native digits are from the Extended Arabic-indic range, and have a bidi_class
property of European_number
, like the ASCII digits.
bidi_class | White_Space | Other_Neutral | European_Separator | Common_Separator |
---|---|---|---|---|
Includes: | ASCII space, and 15 others | Hyphen (U+2010), en-dash, and 5,500+ other code points | Hyphen-minus (U+002D), minus sign, plus sign, +9 more | Solidus, Arabic comma, comma, full stop, colon, nbsp, +9 more |
Bare ASCII | 12 34 56 | 12‐34‐56 | 12-34-56 | 12/34/56 |
Bare native | ۱۲ ۳۴ ۵۶ | ۱۲‐۳۴‐۵۶ | ۱۲-۳۴-۵۶ | ۱۲/۳۴/۵۶ |
ASCII after Arabic | ن 12 34 56 | ن 12‐34‐56 | ن 12-34-56 | ن 12/34/56 |
Native after Arabic | ن ۱۲ ۳۴ ۵۶ | ن ۱۲‐۳۴‐۵۶ | ن ۱۲-۳۴-۵۶ | ن ۱۲/۳۴/۵۶ |
You can experiment with examples using the Arabic character app.
Arabic orthographies can be grouped into a number of writing styles, some of which are more common for particular languages, while others can be used interchangeably for the same language. Sometimes the variations are adapted to usage, for example book text vs. inscriptions; sometimes the variants reflect regional, cultural or stylistic calligraphic preferences.
The different styles include Naskh, Nasta'liq, Ruq'a, Thuluth, Taʻlīq, Kufi, Diwani, Maghribi, Kano. The examples in this page use a naskh writing style. For a brief introduction to font styles, with examples, see Text layout requirements for the Arabic script.
The naskh writing style is the most prominent style for the Arabic language, and has become the default form of Arabic language content in most contexts. It has clearly distinguished letters, which make it easy to read, and can be written in small sizes.
The ruq’ah writing style was designed for use in education, in official documents, and for every-day writing. It is known for its clipped letters composed of short, straight lines and simple curves, as well as its straight and even lines of text. It is a functional style of writing that is quick to write and easy to read. It also doesn’t extend baselines, like a naskh font does. In 2010's rebranding of Amman a ruq'ah font family was created to serve as an italic face. Monotype has an interesting article on the development of ruq'ah.
The nasta’liq writing style is the standard way of writing Urdu and Kashmiri, and is also often a preferred style for Persian text. Key features include a sloping baseline for joined letters, and overall complex shaping and positioning for base letters and diacritics alike. There are also distinctive shapes for many glyphs and ligatures.
The kano writing style is a common way of writing Hausa in Nigeria in the ajami script, and like other East African writing it is based on Warsh (Warš) forms, which incorporate Maghribi characteristics. Some sources describe an alternative Hafs (Ḥafṣ) orthography, used with hand-written adaptations for the newspaper Al-Fijir.
The kufi writing style is the original style used for the Koran, but is not used for newspapers or official content today. However, it is used in modern content for logos and other stylised applications.
See type samples.
Arabic script is always cursive, ie. letters in a word are joined up. Fonts need to produce the appropriate joining form for a letter, according to its visual context, but the code point used doesn't change. This results in four different shapes for most letters (including an isolated shape). Ligated forms also join with characters alongside them.
The highlights in the example below show the same letter, ع, with three different joining forms.
Most Arabic script letters join on both sides. A few only join on the right-hand side: this involves 4 basic shapes for Modern Standard Arabic.
ء doesn't join on either side.
Most dual-joining characters add or become a swash when they don't join to the left. A number of characters, however, undergo additional shape changes across the joining forms. fig_joining_forms and fig_right_joining_forms show the basic shapes in Modern Standard Arabic and what their joining forms look like. Significant variations are highlighted.
isolated | right-joined | dual-join | left-joined | MSA letters |
---|---|---|---|---|
ب | ـب | ـبـ | بـ | |
ن | ـن | ـنـ | نـ | |
ق | ـق | ـقـ | قـ | |
ف | ـف | ـفـ | فـ | |
س | ـس | ـسـ | سـ | |
ص | ـص | ـصـ | صـ | |
ط | ـط | ـطـ | طـ | |
ك | ـك | ـكـ | كـ | |
ل | ـل | ـلـ | لـ | |
ه | ـه | ـهـ | هـ | |
م | ـم | ـمـ | مـ | |
ع | ـع | ـعـ | عـ | |
ح | ـح | ـحـ | حـ | |
ي | ـي | ـيـ | يـ |
isolated | right-joined | MSA letters |
---|---|---|
ا | ـا | |
ر | ـر | |
د | ـد | |
و | ـو |
200D (ZWJ) and 200C (ZWNJ) are used to control the joining behaviour of cursive glyphs. They are particularly useful in educational contexts, but also have real world applications.
ZWJ permits a letter to form a cursive connection without a visible neighbour. For example, the marker for hijri dates is an initial form of heh, even though it doesn't join to the left, ie. ه. For this, use ZWJ immediately after the heh, eg. الاثنين 10 رجب 1415 ه..
ZWNJ prevents two adjacent letters forming a cursive connection with each other when rendered. For example, it is used in Persian for plural suffixes, some proper names, and Ottoman Turkish vowels. Ignoring or removing the ZWNJ will result in text with a different meaning or meaningless text, eg, تنها is the plural of body, whereas تنها is the adjective alone.2 The only difference is the presence or absence of ZWNJ after noon.
034F is used in Arabic to produce special ordering of diacritics. The name is a misnomer, as it is generally used to break the normal sequence of diacritics.
See just above for shaping related to cursive joining.
In all but the most basic fonts, glyph shapes are highly variable for Arabic letters. For example, fig_mishafi_ka shows a wide variety of shapes produced by default in the Mishafi font for ك when followed by various letters.
A good font will constantly change the shape of glyphs slightly so as to create a more aesthetically pleasing, and in some cases a more easily readable, flow.
teeth_letters shows an example where the same word is displayed using different fonts.a,#h_teeth_letters The font on the left applies rules to distinguish the letter bases clearly. Note, in particular, that although there are 3 letters which are repeated, none of those letters uses the same shape twice.
In more traditional fonts, you will also often see the join between certain characters above the baseline. Compare the highlighted character joins in fig_raised_joining, showing the same sequence of letters but with joins above vs. along the baseline. (The first font is Mishafi, and the second Scheherazade New.)
But actually a good font will typically have a range of shapes and placements for a given letter, depending on the adjoining letter. This is illustrated in noon_joining_forms.a,#multi-context-joining
Characters within a word may also combine vertically in certain groupings. See the example in vertical_joining.
Ligated glyph forms are common in Arabic. Some, such as لا are mandatory. Most of the remainder depend on the font style. The lam-alif ligature also affects other characters that are based on the alif, such as for لإ لأ لآ.
Traditional fonts tend to have more optional ligated forms than modern styles.
Ligatures are often used to manage justification. Since they generally reduce the horizontal width of a word, they can be used to fit more text on the end of a line, or balance baseline stretching.
When vowel or shadda diacritics are used they can be placed in different positions, according to the context.
When both shadda and vowel signs are combined with a base character, a more complicated set of rules may be applied. Depending on the font used, some vowel diacritics may be placed relative the shadda diacritic, rather than relative to the base character.
See type samples.
Arabic text does use slanting letters. In some cases the letters may be slanted to the left as in fig_font_style_italic.
Arabic has no case distinction.
However, as mentioned in numbers, Arabic sometimes uses ASCII digit glyphs and other times uses local digit glyphs. Some fonts and authoring applications allow you to choose which glyph shapes to use for the same underlying characters.
Arabic fonts may also have alternative shapes for glyphs, which can be turned on in certain circumstances. For example, some fonts have a set of swash forms for certain characters, which can be used for justification, or just for effect.
Words are separated by spaces.
In Arabic, small words like 'and' (و) are written alongside the following word with no intervening space (eg. الجامعات والكليات means 'universities and colleges', but there is only one space). Such small words are handled typographically as part of the word they are attached to.
In most cases Arabic text uses precomposed characters and omits vowels. Therefore grapheme boundaries are consistent with individual letters. Where this is not the case, the additions are combining marks, and the Unicode grapheme cluster is designed to span combinations of base character plus any number of following combining marks.
One potential complication is that fonts often render sequences of characters as ligated forms. The ligated forms are a font-specific feature, whereas grapheme clusters are based on code point sequences: some fonts may display the same sequence of characters without a ligated form. Most applications tend to move character by character through the text, producing situations like the cursor position in fig_gc_ligature_cursor.
This approach allows for easy deletion or insertion of any component of a ligated form.
Many Brahmi-derived scripts are segmented by units that incorporate more than one grapheme cluster, for operations such as in-word line-breaking, justification, letter-spacing, and initial letter highlighting. It is not clear whether such typographic units are needed for Arabic language text, since there is usually no hyphenation, and no initial letter highlighting, and letter-spacing and justification follow quite different rules, extending the baseline. It may be worth looking at the very rare examples of vertically-set lines with upright Arabic letters to check whether ligatures like lam-alif or others are kept together. (My expectation is that lam-alif is not split, but the others may be.)
Apart from lam-alif, where one can expect a rule to apply consistently, another issue is that an application that wants to keep ligatures together as a single unit would have to be aware of the rendering behaviour of the particular font in use, since some fonts have ligatures for a given code point sequence and others don't. There is no way of deriving this information from the code point sequence itself, since that is always exactly the same.
Test in your browser. The words test units that equate to grapheme clusters only, and others that include conjuncts. First, the text is displayed in a contenteditable paragraph, then in a textarea. Results are reported for Gecko (Firefox), Blink (Chrome), and WebKit (Safari) on a Mac.
أنتن أَنْتُنَّ الإسلام أسو
The last word on each line (only) has a decomposed sequence for the lam+hamza.
Cursor movement. Move the cursor through the text.
Gecko , Blink, and WebKit browsers steps through the text using grapheme clusters. This means that it takes 2 steps to get past the lam-alif ligature. The decomposed sequence in the last word is treated like any other grapheme cluster.
Selection. Place the cursor next to a character and hold down shift while pressing an arrow key.
The behaviour is the same as for cursor movement.
Deletion. Forward deletion works in the same way as cursor movement. The backspace key deletes code point by code point, for all browsers.
Arabic language uses a mixture of ASCII and Arabic punctuation. Other languages using the Arabic script may use different punctuation, such as the full stop in Urdu.
phrase | ، ؛ : |
---|---|
sentence | . ؟ ! |
Arabic language text also uses ‐ U+2010 HYPHEN, –, and —.
Arabic commonly uses ASCII parentheses to insert parenthetical information into text.
start | end | |
---|---|---|
standard | ( |
) |
The words 'left' and 'right' in the Unicode names for parentheses, brackets, and other paired characters should be ignored. LEFT should be read as if it said START, and RIGHT as END. The direction in which the glyphs point will be automatically determined according to the base direction of the text.
The number of characters that are mirrored in this way is around 550, most of which are mathematical symbols. Some are single characters, rather than pairs. The following are some of the more common ones.
Although characters in the Arabic Presentation Forms blocks should not normally be used, the following are sometimes used for Arabic text.
Unlike other parentheses, for legacy reasons these are not automatically mirrored when used in text, so you need to choose the right code point based on the expected glyph shape.
See type samples.
Two different styles of quotation mark can be found in Arabic language texts. When quoted text appears within quoted text different characters are used, though usually of the same type. (Of course, depending on ease of input, quotations may also be surrounded by ASCII double and single quote marks.) Spacing inside the marks is optional.wqm
start | end | |
---|---|---|
primary | « | » |
nested | ‹ | › |
Because they are mirrored, when using the guillemets, LEFT should be read as if it said START, and RIGHT as END. The guillemet shapes are typically rounded, as shown in fig_quotation_marks.
start | end | |
---|---|---|
primary | ” |
“ |
nested | ’ |
‘ |
Unlike the guillemets, these quote marks are not mirrored during display. As a result, LEFT means use on the left, and RIGHT means use on the right.
Sometimes these styles are mixed in the same text. The example in fig_quotation_marks uses both in a single sentence.
Emphasis can sometimes be expressed by stretching the baseline of one or more words. See the section on justification below for more information about baseline stretching.
Arabic uses ….
Underlines and overlines in Arabic text are usually further from the baseline than they are in Latin text. This is because the Arabic letters extend further from the baseline, and because there are also sometimes diacritics beyond those long extensions. Typically, the line will be drawn so that it is further from the baseline than any other glyphs reach.§
In some cases, however, while still keeping the line further from the baseline than in Latin text, typographers don't clear the glyphs. In this case, the lines usually skip the ink of the other glyphs.
When skipping ink it is important to avoid leaving very short remnants of the line between glyphs, since these may look like dots or diacritics.
The Qur'an tends to use overlines, rather than underlines.
Other punctuation marks used in Arabic include the following.
This section focuses mainly on Arabic language text, however attention is sometimes drawn to differences when the Arabic script is used for other languages.
Lines are normally broken at word boundaries.
They are not broken at the small gaps that appear where a character doesn't join on the left.
Hyphenation isn't used for the Arabic language, however other languages using the Arabic script may hyphenate (such as Uighur).a
As in almost all writing systems, certain punctuation characters should not appear at the end or the start of a line. The Unicode line-break properties help applications decide whether a character should appear at the start or end of a line.
Show default line-breaking properties for characters in this orthography.
The following list gives examples of typical behaviours for characters affected by these rules. Context may affect the behaviour of some of these and other characters.
When a line break occurs in the middle of an embedded left-to-right sequence, the items in that sequence need to be rearranged visually so that it isn't necessary to read lines upwards.
latin-line-breaks shows how two Latin words are apparently reordered in the flow of text to accommodate this rule. Of course, the rearragement is only that of the visual glyphs: nothing affects the order of the characters in memory.
See type samples.
Arabic script justification can be implemented using a number of different techniques, which ideally are applied in combination. These include:
(In hand-written manuscripts it is also possible to find instances where the letters the would appear at the end of the line are squeezed above the last word in the line, or hang into the margin.)
The application of the various techniques is generally subject to rules governing the frequency and location of use of particular methods. Rules can differ by writing style – for example, elongation is not normally used at all for ruq'a fonts. Where baseline stretching is applied, the rules for what can be stretched, and how much, are complicated. Unlike space-based width adjustments, baseline extension is not a question of simply adding equal-length extensions across the line. The rules tend to differ across orthographies, and eminent typographers of the past also had their own preferred or idiosyncratic rules.
The baseline extension character ـ is sometimes suggested as a way of producing justification by extending the baseline, however when a browser window is resized, or when new text is added near the start of a paragraph, lines wrap differently and all the places where tatweel would be needed have to be recalibrated. Thus tatweels only work for static text with fixed dimensions.
Better quality justification systems stretch glyphs, rather than adding baseline extensions. This dynamic stretching of glyphs is often called 'kashida'. In some typesetting systems, such as InDesign, the stretching can be produced automatically without the need for tatweel characters. InDesign has controls to vary the preferred length of the extensions.
Note that the result of the automatic justification in fig_kashida_justification is different from that in the newspaper clipping. For one thing, the kashida effect is only applied once per word (but is applied to most words). The rules determining which combinations of characters receive baseline stretching, and the extent of that stretching also differ.
InDesign also allows fonts to substitute long swash variants for certain characters, which soak more some of the horizontal space.
Well justified text would apply a mixture of swash characters, space stretching, kashidas and ligatures to achieve a visually appealing and effective justification. Also, the baseline stretching in fig_kashida_justification is flat. A more advanced system would instead produce elegantly curved kashidas more like handwritten text.
It is very common to see baseline stretching in modern Arabic text where a word or phrase is stretched to fill a particular space, eg. the Arabic tag line (الابداع المتجدد Creativity renewed) below the word Lexus in fig_lexus is stretched to be the same width.
Observation: Text that is stretched in this manner very often has multiple kashidas per word. This is perhaps understandable, given that usually only a small number of words are involved.
See type samples.
Spaces are not added between characters, with the exception of micro-spacing during justification, which is applied to word-medial letters that don't join to the left. On the other hand, the baseline within words is often stretched.
It is quite common to see Arabic text stretched to fit a given width, as shown in fig_lexus, but that type of stretching is more akin to justification than the typical letter-spacing that is applied to other scripts. The amount of stretch is determined by the area that needs to be filled.
In some cases, it may be that elongation of words is driven by stretching the distance between letters rather than matching an external template, for example to express emphasis or prolonged sound. However, as for justification, this is not normally based on an even amount of stretch between all letters, as letter-spacing tends to be in other scripts.
The alphabetic baseline is a strong feature of Arabic script on the whole, since characters tend to join there. This is not always the case: for example, some adjacent pairs or ligatures have joins above the baseline, and initial letters in some fonts may start slightly above the baseline, but for most cases it remains a strong feature.
The nastaliq writing style, on the other hand, uses arrangements of joined glyphs that cascade downwards from right to left, and ressemble a strongly sloping baseline.
However, even writing styles with an ostensibly flat baseline may, in good quality fonts, draw words on a slightly slanted baseline, or multiple baselines, as shown in fig_word_baselines.a,#multi-level-baselines
Characters within a word may also combine vertically in certain groupings, as mentioned in the previous section.
Line height and multi-script positioning. Even without the deviations from the baseline described above, the ascenders and descenders of Arabic letters tend to travel further from the baseline that is usual in Latin script text. Allowances for this need to be made for line height settings on a page, but also it can be problematic when combining Latin and Arabic text on the same line using different fonts for each.
If the Arabic font supports the needed Latin letters, the font design will already take into account the relative sizes of the letters, and their placement relative to the baselines of each script. If different fonts are used, though, it's important to match the baselines and harmonise the font sizes used.
Arabic letters have ascenders and descenders that tend to be longer than the Latin ones. fig_baselines shows ascenders and descenders for Arabic letters in the Scheherazade New font. With the addition of diacritics above and below the letters, the line height needs to be significantly higher than for Latin script text.
You can experiment with counter styles using the Counter styles converter. Patterns for using these styles in CSS can be found in Ready-made Counter Styles, and we use the names of those patterns here to refer to the various styles.
The Arabic language uses 1 numeric and 2 fixed styles. Wikipedia lists 2 more styles: an old maghrebi
sequence and the hijai
sequence.
The arabic-indic numeric style is decimal-based and uses these digits.rmcs
Examples:
The arabic-abjad fixed style uses these letters. It is only able to count to 28.rmcs
Note that the 5th counter includes a zero-width joiner formatting character. This makes the shape distinguishable from ٥.
Examples:
The maghrebi-abjad fixed style uses these letters. It is also only able to count to 28. The letters are the same as those used for the arabic-abjad style, but 6 occur in different positions.rmcs
The 5th counter also includes a zero-width joiner formatting character.
Examples:
Arabic lists generally use a full stop suffix as a separator.
The table below shows the differences between fixed counter styles for the Arabic and Persian languages. In addition to the styles described above are two other sequences that are mentioned in Wikipedia – an old maghrebi
sequence and the hijai
sequence.
A blank cell uses the same letter as the nearest non-blank cell above it.
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
persian-abjad |
ا | ب | ج | د | ه | و | ز | ح | ط | ی | ک | ل | م | ن | س | ع | ف | ص | ق | ر | ش | ت | ث | خ | ذ | ض | ظ | غ | ||||
arabic-abjad |
ي | ك | ||||||||||||||||||||||||||||||
magrebi-abjad |
ص | ض | س | ظ | غ | ش | ||||||||||||||||||||||||||
WP old magrebi |
ت | ث | ج | ح | خ | د | ذ | ر | ز | ط | ظ | ك | ل | م | ن | ص | ض | ع | غ | ف | ق | س | ش | ه | و | ي | ||||||
WP hijai |
س | ش | ص | ض | ط | ظ | ع | غ | ف | ق | ك | ل | م | ن | ||||||||||||||||||
persian-alphabetic |
پ | ت | ث | ج | چ | ح | خ | د | ذ | ر | ز | ژ | س | ش | ص | ض | ط | ظ | ع | غ | ف | ق | ک | گ | ل | م | ن | و | ه | ی |
It is possible to find cases where Arabic enlarges and styles the first character at the beginning of a paragraph, but it is quite rare.
Observation: It is not clear whether it is appropriate to maintain the joining forms of the initial letter and the following letter. A good proportion of the examples seen have the initial letter in a box, in which case it appears to be in isolated form. For further discussion see this thread and this one.
Arabic books, magazines, etc., are bound on the right-hand side, and pages progress from right to left.
Columns are vertical but run right-to-left across the page.
Tables, grids, and other 2-dimensional arrangements progress from right to left across a page.
Form controls should display Arabic text from right to left, starting at the right side of the input field. Form controls should also usually be arranged from right to left.
fig_form shows some form fields from an Arabic language web page. Note the position of the labels relative to the input fields and the checkbox, mirror-imaging a similar page in English. Note also that the input text in the first field appears to the right of the box.
The position of a scrollbar should depend on the user's environment, not on the content of a page. A non-Arab user viewing a web page in Arabic shouldn't have to look for the scroll bar on the left side of the window. In a system that is set up for an Arab user, however, the scrollbar can appear on the left.