Thaana history · 4 min read · 741 words

Thaana and the written life of Dhivehi

Understand Thaana as a Maldivian writing system with right-to-left direction and a history of adapting vowel information.

A script for the Maldives

Thaana is used to write Dhivehi, the modern language of the Maldives. Its history is connected to the island environment and to the need for a script that could represent the language's sounds.

The modern script is therefore best approached through Dhivehi words and pronunciation, not through an abstract character list.

Borrowed shapes, a distinct system

Some Thaana glyphs were historically influenced by Arabic-Indic digits and other forms, but Thaana is its own alphabet. Its written vowels are obligatory, which distinguishes its structure from an abjad.

This is a useful reminder that visual ancestry does not determine the whole writing-system category.

Direction and separation work together

Thaana is written right to left but is not cursive. The line therefore combines a directional reading habit with separate letterforms and vowel marks.

Practise both features together so the page feels like Thaana rather than a flipped Latin exercise.

Thaana has a Maldivian writing history

Unicode identifies Thaana as the modern script of Dhivehi in the Maldives and notes that it appeared alongside Dives Akuru in the eighteenth century before replacing it as the regular script by the turn of the nineteenth century. These dates place the script in a specific island history rather than in a generic category of Arabic-influenced writing.

A historical guide should label which period and language form each example represents.

Sources: [1], [2]

Borrowing does not erase invention

The script’s history includes glyphs based in part on Arabic-Indic digits and vowel notation that resembles Arabic practice, but Unicode classifies Thaana as an alphabet because vowels are obligatory. This is a useful lesson in how writing systems combine inherited visual ideas with a new structural solution.

Use the comparison to sharpen the learner’s understanding of Thaana, not to treat it as a partial Arabic alphabet.

Sources: [1]

Connect history to Dhivehi practice

After reading the timeline, choose a current Dhivehi reference and practise one consonant with two vowel signs and sukun. Keep the language label beside the line and separate any Dives Akuru comparison from the current set.

The history becomes useful when it leads to an accurate, present-target exercise.

Sources: [1]

Use dates instead of a smooth origin story

A guide should not imply that Thaana appeared fully formed or that all Arabic influence happened at one moment. State the source, period, and specific feature being discussed. If a current claim is not supported by the Unicode overview, link to a newer institutional or scholarly source rather than filling the gap.

That discipline is part of respectful writing about a living Maldivian script.

Sources: [1], [2]

Read the Dives Akuru transition carefully

Unicode places Thaana alongside Dives Akuru in the eighteenth century and describes Thaana replacing it as the regular Dhivehi script by the turn of the nineteenth century. This is a historical sequence, not proof that every community or text changed at exactly the same time.

Use dates and source labels when comparing the systems.

Sources: [1], [2]

Explain borrowed forms without reducing the script

The Arabic-Indic digit influence on some Thaana glyphs is an example of visual borrowing. The obligatory vowel system and right-to-left non-cursive structure show how Thaana became its own solution for Dhivehi. A history guide should explain both parts.

The comparison is useful when it helps the learner recognise what is shared and what is distinct.

Sources: [1]

Use the timeline to choose a practice model

After the historical section, select a current Dhivehi reference and practise a small set with vowel marks. Keep Dives Akuru or Arabic comparisons in a separate column and label their period. End with a current right-to-left line.

The history should make the target clearer, not leave the learner with several blended alphabets.

Sources: [1]

Avoid a single-cause history

Unicode gives a timeline involving Dives Akuru, Arabic-Indic visual influence, and the development of a vowel-writing system for Dhivehi. Present those as distinct pieces of evidence rather than claiming that one influence explains every Thaana form.

A careful history guide names what the source documents and leaves wider claims to additional research.

Sources: [1], [2]

Make the historical comparison actionable

Choose one current Thaana consonant, one vowel mark, and one short Dhivehi example after the historical section. Put any Dives Akuru or Arabic comparison in a separate note and label its period. The learner should leave knowing exactly what to practise now.

History should clarify the target, not multiply unmarked inventories.

Sources: [1]

Further reading

These references provide more historical, linguistic, and technical context for the script.

Keep exploring

Continue with another useful guide before you move into practice.

Thaana learning library

Would you like a Thaana practice app?

This script is ready to explore, but its focused mobile app has not been released yet.

Email me when it is ready