RTL Book Translation: Arabic and Hebrew Layout Checks for PDF and EPUB

An Arabic or Hebrew book is not publication-ready merely because its paragraphs align to the right. A correct right-to-left edition needs the intended text direction, stable bidirectional behavior inside mixed-script passages, correct page progression, matching language metadata, suitable fonts, and a cover and navigation system built for the chosen format and retailer.

Test the edition in this order:

1. Confirm the target locale, script, format, and retailer requirements.
2. Check paragraph direction separately from page progression.
3. Stress-test numbers, punctuation, Latin names, URLs, email addresses, and code.
4. Check tables, lists, notes, images, navigation, and cover order.
5. Inspect the actual PDF or EPUB in more than one relevant reader.
6. Log defects by severity and recheck the final exported file.

Download the RTL book translation checklist and record the reader, device, format, and location for every result.

Separate four kinds of direction

Teams often collapse several independent settings into one idea called "RTL." Review them separately.

Right-aligning text affects none of these reliably by itself. Do not use alignment as the acceptance test.

Amazon KDP's language and reading-direction guidance says the selected content language, book content, and metadata must match and that the chosen reading direction must match the file. Retailer rules and format availability can change, so verify the exact language and edition type immediately before publishing.

Define the exact target locale and script

"Arabic" and "Hebrew" are incomplete production specifications. Record:

• target language and regional variety;
• script and orthographic conventions;
• target readers and expected register;
• numeral style and date conventions;
• quotation marks and punctuation policy;
• transliteration rules for names and titles;
• treatment of untranslated Latin terms;
• output format and required reading systems; and
• retailer, print vendor, or distribution constraints.

Arabic typography and vocabulary vary by market and purpose. Hebrew output can mix unpointed text, vowel points, Latin terms, and numerals. A reviewer who knows only that the file "looks RTL" cannot resolve those editorial choices.

Build approved forms for names and repeated terms before the complete translation. Use the terminology consistency workflow to search every accepted and rejected variant across the final book.

Stress-test bidirectional text

The Unicode bidirectional algorithm resolves visual ordering when strong RTL characters, strong LTR characters, numbers, punctuation, and neutral characters share a line. Problems often appear at the boundary between runs rather than inside ordinary Arabic or Hebrew prose.

Create a synthetic test page using non-sensitive sample data that contains:

• an Arabic or Hebrew sentence containing an English product name;
• a sentence containing 2026, 12.5%, a negative value, and a date;
• a URL with a path and query string;
• an email address;
• parentheses around mixed-script content;
• an ISBN and a page range;
• a numbered list;
• a table containing both RTL and LTR cells; and
• a footnote marker next to punctuation.

Review meaning and visual order. Copy each line into a plain-text editor and another application to reveal whether the appearance depends on fragile positioning. Search the exported PDF or EPUB for the Latin name, number, and URL to confirm that the underlying text remains usable.

Do not "fix" mixed-script lines by inserting arbitrary spaces until one screenshot looks right. Spaces can wrap differently on another device. Use the direction metadata, semantic markup, or isolation mechanism appropriate to the source format.

Check numbers and punctuation in context

Numbers are usually read left-to-right even inside RTL paragraphs, but surrounding labels and punctuation participate in bidirectional ordering. Inspect:

• decimal and thousands separators;
• currency symbols and whether they belong before or after the amount;
• percentages, negative signs, ranges, and units;
• dates and times;
• chapter, figure, table, and page references;
• ISBNs, phone numbers, version strings, and equations;
• opening and closing parentheses or brackets; and
• colon, semicolon, slash, quotation mark, and ellipsis placement.

Compare every material value with the source. A visually reordered number can become a translation defect, while a linguistically correct number can still be attached to the wrong label after table reconstruction.

Verify fonts and shaping

Choose fonts with coverage and shaping behavior for the exact script and styles in the book. Then test regular, bold, italic or oblique, headings, captions, footnotes, tables, and cover typography.

Reject:

• disconnected Arabic letters;
• missing glyph boxes;
• combining marks colliding with letters;
• substituted glyphs after export;
• fake styling that damages readability;
• clipped ascenders, descenders, or marks;
• excessive letter spacing applied to a connected script; and
• a fallback font that changes line length enough to break the page.

Inspect the final file on a system that does not have the production font installed when embedded fonts are expected. For EPUB, test with user-selected fonts as well as the publisher style; readers can override presentation.

PDF checks for Arabic and Hebrew books

A fixed PDF can hide underlying direction errors behind visually positioned glyphs. Test both appearance and document behavior.

Interior

• Confirm the intended first page and physical page sequence.
• Verify mirrored inner and outer margins for print.
• Inspect columns, tables, captions, footnotes, lists, and page numbers.
• Select and copy mixed-script paragraphs to test logical text order.
• Search for Arabic or Hebrew terms and Latin names.
• Check bookmarks and table-of-contents destinations.
• Confirm fonts are embedded when the print or distribution workflow requires it.
• Inspect tagged reading order when accessibility is part of the delivery.

Cover

The physical cover arrangement depends on the print provider and reading direction. KDP's current Hebrew, Persian, and Yiddish publishing guidance says that for its RTL paperback cover PDF, the front cover is placed to the left of the spine and the back cover to the right. Do not generalize one vendor's template to another: download the exact template for the edition's trim size, page count, paper, and reading direction.

Check title, subtitle, author, translator credit, spine direction, barcode safe area, bleed, and back-cover copy. The translated-book cover guide helps decide whether the existing design needs text replacement, relayout, partial adaptation, or redesign.

Use the complete PDF translation QA checklist for missing text, tables, clipping, links, forms, and final-export checks.

EPUB checks for Arabic and Hebrew books

An EPUB contains both a logical reading order and presentation rules interpreted by a reading system. Test the package, the content, and real readers.

Package and navigation

• Set the publication language to the exact target language tag.
• Confirm the spine order follows the intended chapter sequence.
• Set the appropriate page-progression direction rather than relying on a reader default.
• Check title, author, description, accessibility metadata, and cover labels.
• Open every table-of-contents entry and landmark.
• Confirm footnote links and return links work in both directions.

The W3C's EPUB overview explains that EPUB can specify global page progression and uses HTML directionality features for bidirectional text. Semantic direction is more portable than visual hacks tied to one viewport.

Content documents

• Set the base direction at the document or block level where appropriate.
• Isolate embedded LTR names, codes, or URLs when their direction would otherwise affect surrounding punctuation.
• Avoid manual spaces and reordered source characters.
• Check lists, table columns, image-caption pairs, poetry, and side notes.
• Increase and decrease font size to expose reflow defects.
• Change typeface, theme, and orientation where the reader permits it.

Reader matrix

Use at least two independent reading systems relevant to the actual audience. Record the application and version, operating system, device class, font setting, and orientation. Include the retailer's preview tool when the book will be sold there.

A pass in one desktop reader is insufficient evidence for a mobile or e-ink release. Retailer support is also specific: KDP's current Arabic guidance requires RTL direction for Arabic Kindle content and recommends reviewing the file in Kindle Previewer.

Test tables, lists, notes, and images separately

Complex structures combine content order with visual direction.

Tables

Decide whether the first semantic column belongs on the visual right. Check header-to-value relationships, numbers, units, column order, overflow, and screen-reader order. Do not mirror a data table automatically if the source's sequence has a conventional or logical meaning that target readers expect to retain.

Lists

Check marker position, indentation, hanging alignment, nested levels, and mixed-script list items. Verify that numbered steps still describe the same sequence.

Footnotes and endnotes

Check marker placement beside punctuation, note direction, numbering, backlink behavior, and page or chapter references. A note can be linguistically correct but unreachable in an EPUB.

Images and diagrams

Identify text embedded in images. Decide whether arrows, timelines, charts, screenshots, and directional diagrams must be localized or mirrored. Mirroring an image can reverse logos, maps, controls, or factual relationships; approve each transformation individually.

Use severity to control release

Any blocker invalidates the release. Two similar major defects suggest a systematic markup, font, or reconstruction problem; expand review beyond the pages where the issue was first noticed.

Final RTL release gate

Release only when:

• the target locale, script, register, numerals, and transliteration policy are documented;
• content language, metadata, and retailer setup match;
• paragraph direction and page progression are both correct;
• mixed-script stress tests pass for names, numbers, punctuation, URLs, and email;
• fonts shape and embed correctly in every required style;
• tables, lists, notes, figures, and navigation work;
• PDF cover and interior order match the current vendor template, or EPUB spine and progression metadata are correct;
• the book has been tested in the required PDF environment or at least two relevant EPUB readers;
• every blocker and major defect is fixed and rechecked in the final export; and
• a qualified Arabic or Hebrew reviewer approves connected prose, not just page geometry.

BookTranslator can create a complete-file translation draft for supported book formats. Use that output as the beginning of the production workflow, then apply the direction, typography, device, and language-review gates above. For whole-book acceptance beyond RTL behavior, continue with the book translation QA checklist.