Not a single "formatting" step — a real production pipeline, walked through stage by stage.
Written by Ata Rafi, Founder and Chief Formatter at Format Fix, describing the actual pipeline used on every project.
Get A Free QuoteIntake and assessment, digitization if needed, layout, native-reader proofing, and output-specific export. This is the technical production pipeline — separate from the quote request and engagement process. See Pricing & Quote for how a project actually gets started.
Script, condition, and structural scope reviewed before anything is priced or started.
Only when the manuscript isn't already a clean digital file.
Where RTL, kashida, and letterform handling actually happen.
Checked by someone who reads the language, not just compared visually.
Print-ready PDF and ebook export are two different final stages.
Every manuscript is reviewed for script and language, current condition (clean digital file vs. scanned or handwritten), and structural scope — footnotes, cross-references, multi-volume status — before anything is priced. This assessment is what actually drives the quote. Manuscripts are kept confidential from this first stage on, regardless of subject matter. See What Affects Arabic Book Typesetting Cost for how these factors translate into a real number, or How to Prepare Your Manuscript for what to organize on your end before this stage begins.
A handwritten or scanned manuscript is typed into editable text before formatting begins — a distinct stage with its own timeline, not folded into the layout work. Skipping this step and formatting directly from a scan is where broken letter joining and disconnected characters usually start. See Arabic Typing Services or Urdu Typing Services.
This is where right-to-left layout, kashida-based justification, and contextual letterforms are actually handled — the technical core of the process. See the Arabic Typography Glossary for what these terms mean, and Arabic Typesetting Software Explained for the tools involved.
Typed and typeset text is checked by someone who reads the language fluently, not just visually compared against the source. For Quranic or diacritic-sensitive text, this stage catches meaning-level errors a purely visual check would miss entirely. See Why Tashkeel Placement Errors Change the Meaning of Your Text for why this distinction matters.
Print and ebook are two different final stages with different technical requirements, not one export applied twice. See Print-Ready PDF Formatting and Arabic eBook Formatting Services for what each involves, including the specific requirements covered in Common Arabic eBook Formatting Mistakes That Get Rejected by KDP.
Real, documented issues exist even in professional RTL-capable software — Arabic periods relocating on paste from Word, and dropped punctuation under kashida-based justification. This is why the layout stage specifically needs trained execution, not just RTL-capable software.
See Arabic Punctuation Placement Problems for the full detail on both documented issues.
A clean digital manuscript with simple structure moves through all five stages faster than a scanned document with heavy cross-referencing or diacritic-sensitive text. Quoting a fixed number here would mean ignoring exactly the factors that determine it — the real timeline comes from the same intake assessment that sets the price, not a generic estimate.
See What Affects Arabic Book Typesetting Cost for the same underlying factors, or the portfolio for real finished projects of comparable scope.
Wanting to know what actually happens to their manuscript before or during a project.
Checking whether a vendor's process is actually thorough, not just a quick turnaround claim.
Comparing a candidate vendor's stated process against what a legitimate one actually looks like. See Red Flags to Avoid When Hiring an Arabic Book Formatter.
Intake and assessment, digitization if the manuscript isn't already digital, layout and typesetting, native-reader proofing, and output-specific export for print or ebook.
No — only manuscripts that aren't already a clean digital file. A handwritten or scanned document needs to be typed into editable text first, as a separate stage.
Right-to-left layout, kashida-based justification, and contextual letterform handling all happen at this stage — the technical core of the process, and where documented software bugs most commonly surface.
Because it checks for meaning-level accuracy, not just visual correctness. A visual check can miss a diacritic error that changes grammatical meaning, which only a fluent reader would catch.
Yes — print-ready PDF export and ebook export are two different final stages with different technical requirements, not one export applied twice.
It depends on manuscript length, condition, and structural complexity — the same factors that determine cost also determine timeline. There's no single fixed number that applies to every project.
