Not a generic list translated from English typesetting advice — these are the specific, Arabic-script signs that separate a professionally typeset book from one that reads as self-published.
Each sign below is tied to a documented Arabic typesetting mechanic, reviewed by Ata Rafi, Founder and Chief Formatter at Format Fix, who checks manuscripts against this exact list before calling a project finished.
Request A Free QuoteUneven justification instead of proper kashida stretching, disconnected letters, numbers or dates in the wrong order, punctuation on the wrong side, inconsistent or missing tashkeel, inconsistent heading styling, a font without real Arabic support, mismatched Arabic-English content, missing structural front matter, and a file that was never checked against its final export. Each is covered below.
Arabic justifies by stretching letters (kashida), not by adding word spacing the way English does. A page with visibly uneven word gaps instead of smooth letter elongation is a tell that the layout tool wasn't given real Arabic justification rules. See Arabic Punctuation Placement Problems for a documented kashida bug that can drop punctuation entirely under full justification.
Arabic letters must join into continuous ligatures based on their position in a word. Isolated, floating letterforms scattered through the text are one of the most immediately visible signs of an amateur setup. See Why Does My Arabic Text Look Broken, Reversed, or Disconnected? for the full diagnostic.
Numerals read left-to-right even inside right-to-left Arabic text. A reversed digit sequence in a date, page reference, or citation is a small detail that trained readers notice immediately. See Mixed Arabic-English Text: Numbers, Names & Dates for why this happens.
A period, comma, or question mark in the wrong position — or a full stop that's simply missing — is a documented, recurring formatting failure, not a rare glitch. Full breakdown on Arabic Punctuation Placement Problems.
Diacritical marks are positioned precisely relative to the base letter. Marks that drift, disappear, or apply inconsistently across the manuscript signal that the file wasn't checked page by page after formatting. See Quranic Text & Tashkeel Formatting for how this is handled where precision matters most.
Chapter titles and section headings that shift in size, weight, or spacing from one chapter to the next read as unplanned, not stylistic. A consistent heading system, applied the same way from the first page to the last, is one of the simplest and most visible signals of a professionally structured book. See Arabic Editorial Formatting for how heading hierarchy is planned before layout begins.
A font chosen for its Latin character set, with Arabic support added as an afterthought, often lacks full glyph coverage or a complete ligature set — leading to tofu boxes or awkward letterforms. See Arabic Font Selection & Licensing for how fonts are checked for genuine Arabic support before a project starts.
An embedded English name, date, or citation that visually clashes with the surrounding Arabic — wrong spacing, inconsistent numeral system, or awkward positioning — shows the two scripts were handled separately instead of as one planned layout. See Mixed Arabic-English Text: Numbers, Names & Dates.
A missing or inconsistently placed title page, copyright page, or table of contents — or one that wasn't adapted for how these pages sit in an RTL-bound book — is a structural gap readers notice even if they can't name what's missing. See Arabic Editorial Formatting for how front matter and structure are handled for a full manuscript.
A file can look correct inside the design tool and still break on export — a dropped period, a font that isn't embedded, a digit sequence that reverses. Skipping this final check is the single most common reason avoidable mistakes reach a reader or a KDP rejection. See Common Arabic eBook Formatting Mistakes That Get Rejected by KDP for the specific export failures to check for.
Readers Notice Layout Quality, Even Without Naming ItMost readers can't identify "kashida justification" or "tashkeel drift" by name, but they notice when text looks uneven, disconnected, or inconsistent — the same way a reader of any language notices a book that "feels" unpolished without knowing exactly why. These aren't cosmetic details layered on top of the writing; they're part of how a book is judged on sight, before a single word is read.
Most of these signs are fixable on the existing file, not a full re-typeset from scratch. The manuscript's actual writing and structure stay untouched; what changes is the layer of typesetting decisions sitting on top of it.
Get a quote for a review of an existing file, or see the portfolio for examples of projects taken from a rough or self-formatted state to a finished one. Still deciding whether to redo it yourself or hire it out? See DIY vs. Professional Arabic Typesetting.
Writers who self-typeset a first attempt and sense something looks off, without knowing which specific issue to search for.
Publishers checking a delivered file against a professional standard before approving it for print or ebook release.
Authors who've heard vague complaints about how a published book "looks" without a reader naming the exact cause.
Ten specific, recognizable signs: uneven justification instead of kashida stretching, disconnected letters, reversed number order, misplaced punctuation, inconsistent tashkeel, inconsistent headings, a font without real Arabic support, mismatched mixed-script content, missing front matter, and a file never checked against its final export.
Most readers can't name the specific technical issue, but they notice when text looks uneven, disconnected, or inconsistent — the same way readers of any language sense an unpolished book without identifying exactly why.
Yes — it's one of the most visible signs, caused by a font or export process that isn't handling Arabic's contextual letter joining correctly.
Yes — using a numeral system that doesn't match the book's target region, or mixing systems inconsistently within one document, is a detail regional readers notice immediately.
Usually, yes. Most of these signs are fixable on the existing file — a font swap, a justification correction pass, a punctuation and numeral audit — without redoing the manuscript's structure from scratch.
Yes — a font chosen primarily for its Latin character set, with Arabic support added as an afterthought, often lacks full glyph coverage or a complete ligature set, leading to visible rendering problems.
