العربية

Typeface projects do not usually stall because of the design. They stall because the two sides went in with different ideas of what a “custom typeface” means.

The company imagines a file being handed over. The designer sees a system being built. The gap between those two pictures is what produces the delays and the endless revisions.

This article explains what a company needs to know before signing, not once the work is underway.

📐 First: the scope of work is not the number of letters

What gets underestimated most often in Arabic typeface projects is the size of the system.

An Arabic letter has up to four forms depending on its position in the word. Then come the required ligatures, then the diacritics (tashkeel) and how they behave over each letter, then the numerals and punctuation. A single Arabic font file usually contains hundreds of glyphs, most of which cannot be typed directly: they appear automatically, depending on context.

That is why “How many letters?” is the wrong question. The right questions are:

  • How many weights? Every additional weight expands the drawing, testing and review work. It is not just a mechanical increase in stroke thickness.
  • Does it include Latin? A second script is designed alongside the Arabic, not bolted onto it.
  • Does it cover other languages written in Arabic script? Urdu, Kurdish and Persian have additional glyphs and behave differently.
  • What level of diacritics do you need? Fully vocalized text takes far more work than text without diacritics.
  • Which OpenType features do you need? Stylistic alternates, discretionary ligatures, localized forms.

Each of these answers changes the size of the project substantially.

👤 Second: who decides

In our experience, this is one of the most common reasons projects stall, and one of the least discussed.

Choosing a typeface is a matter of taste, and it touches many people inside a company: marketing, product, management and perhaps the board. When final approval is not settled in advance, every review turns into an open debate, contradictory feedback comes back and the work is redone repeatedly.

Before you start, settle:

  • Who gives feedback (this can be several people)
  • Who gives final approval (this must be one person or a defined committee)
  • How conflicting feedback is reconciled before it is sent

These three points matter more than any technical clause in the contract.

Specimen of the Omnia Naskh typeface
Specimen of the Omnia Naskh typeface

🔄 Third: how reviews are managed

A typeface project moves from the general to the specific: a visual direction, then a first set of letters, then expansion, then weights, then final refinement.

A common problem is that the company comments on fine details at the direction stage, or asks to change direction after the weights are finished. The first wastes time; the second sends the project back to square one.

The practical rule: at every stage, ask “Is this the right direction?” rather than “Do I like this letter?” The question about the letter comes later, at its own stage.

Also agree with the designer, before you begin, on the number of review rounds for each stage. A project with no cap on revisions never ends.

📦 Fourth: what actually gets delivered

Agree on the list of deliverables in writing. These are the items that usually get forgotten and later become a problem:

  • File formats for the environments you work in: desktop, web and possibly your app
  • A usage guide that explains the weights, when to use each one and how to turn on the optional features
  • A test file that shows the typeface in real contexts taken from your own materials
  • Who handles changes after delivery, and how to request them

The second item in particular is the difference between a typeface that lives on in the company and one that everyone forgets after three months.

⚖️ Fifth: ownership and exclusivity

These are the points that cause the most confusion, and they need to be clear before you sign, not after:

  • Who owns the final design?
  • Is the typeface exclusive to you, or can the designer release it later?
  • If it is exclusive, for how long and in what scope? (Your sector only? Your market? Without any limit?)
  • What happens if you want to extend the typeface later with new weights or languages?

Each of these options has its own logic, and there is no single right answer. But there is an answer, and it has to be in writing.

Specimen of Zajel, a Naskh typeface
Specimen of Zajel, a Naskh typeface

🚩 Early warning signs

  • A designer who does not ask you where the typeface will be used before proposing a direction
  • A price quoted before the number of weights and the language coverage are defined
  • A promise to deliver a full family in a timeframe that seems short for the size of the system
  • No mention at all of diacritics or OpenType features
  • No discussion of who owns what

🧪 A simple test before you commission

Ask the designer to show you a previous typeface in a real context, not in a showcase image: a page full of text, a table of figures, a paragraph with diacritics, a small heading.

Showcase images show a typeface at its most beautiful. A real context shows whether it works.

You can run the same test on any retail typeface with the type tester on its page: type your own text and see for yourself.

To talk about a custom typeface project, start with our custom fonts page.

🔖 Browse the collection

❓ Frequently asked questions

What determines the size of an Arabic typeface project?

The number of weights, whether it includes Latin, whether it supports other languages written in Arabic script, the level of diacritics required, and the OpenType features. The number of letters is not a measure, because an Arabic letter takes several forms depending on its position.

What is the most common reason custom typeface projects stall?

The lack of a clear approver. When it is not settled who gives feedback and who gives final approval, contradictory feedback comes back and the work is redone repeatedly.

What should I ask for in the list of deliverables?

File formats for your working environments, a usage guide that explains the weights and features, a test file in real contexts, and a written agreement on who handles changes later.

How do I evaluate a type designer before commissioning?

Ask to see previous work in a real context (a page of text, a table of figures, a paragraph with diacritics), not in a showcase image. And notice whether they ask you where the typeface will be used before proposing a direction.

When should we discuss ownership and exclusivity?

Always before signing. Who owns the design, whether it is exclusive, for how long and in what scope, and what happens when it is extended later: all of these are terms to put in writing, not to assume.