Advertisement
Advertisement

Does a right-to-left language mean the page geometry is redone?

2026-04-22 02:00:58

Yes. The page geometry is redone. Right-to-left reading changes which edge is the start of a line, which margin is the binding, where the running head sits, how a sequence of figures progresses, and which way a table is scanned. Placing translated strings into the existing left-to-right frames produces a page that looks filled and still asks the reader to begin at the wrong edge. The words are a translation job. The geometry is a layout job, and it is priced and scheduled as its own line.

An English brochure was ordered as a booklet in a right-to-left language. The first attempt kept the facing pages, slid the paragraphs to the right, and translated the captions. The cover still opened on the left. Page numbers still climbed toward the right-hand edge. A before-and-after pair of product photos still ran left to right, so the “after” picture was encountered first. A contents list still put the page number on the wrong side of the title. A reader could fight their way through it. They were fighting the geometry, not the vocabulary. The honest redo mirrored the grid, moved the binding, rebuilt the masters, and checked every sequence against the new reading direction.

What has to move with the text

Margins and gutter swap their roles so the bound edge is still the bound edge. Running heads and folios move to the edge where that language expects them. Columns are reordered so the first column is the one the eye meets first. Bullets and indents hang from the right. Tables are set so the stub column sits on the right, unless the client has a published convention that says otherwise. Captions follow their figures, and the figure itself may need its internal left-right sequence rebuilt, including arrows. A process that must stay in physical order, such as a machine’s real left and right, is queried. Physical left does not automatically mirror. Reading order does.

Fonts and punctuation for the language have to exist in the file. A font that covers the letters and lacks the right punctuation marks will leave a geometrically correct page full of boxes. That discovery belongs at the start of the layout, not at the printer.

What the translation still owns inside the new grid

The translator owns the words, the term list, and the force of warnings. The layout artist owns the grid. They meet on strings that no longer fit, on bidirectional lines where an English product name sits inside a right-to-left sentence, and on numbers. Numbers often stay in their own direction inside the sentence, and a sloppy embed will kick the following word to the wrong side. Those lines are read in the placed page, not only in the export from the translation tool. English source is billed by the word, and the target is billed according to its own unit. The geometry is neither of those rates. There is no public unit price that swallows a full page redo into the word price.

Exact repeated sentences truly reused can still take the lower language rate. They do not reduce the geometry. Every page is being rebuilt whether the sentence is old or new.

Quote it as a redo, and check a printed signature

The quote names the page size, the binding edge, and the software. It says that masters will be rebuilt. A promise of “right-aligned text” is not that quote. Allow time for a check of one signature: cover, a contents spread, a table, a figure with arrows, and a page of mixed product names and target-language sentences. Review of the language still proceeds at about two to three thousand source words a day and does not include this visual pass. The visual pass is where backward arrows and a wrong binding show up.

Deliver the package that opens correctly, plus a PDF exported for the binder, named with version and date. Keep the editable file in the project system. A later “small text change” in a right-to-left file is still a layout touch, because the line may reflow toward the binding.

Does every right-to-left language need the same mirror?

The reading direction is the same family of problem. The typographic details differ: which quotation marks, how much line height, how a particular script handles bold. Ask which language, look at a page the client already accepts in that language, and follow that page’s geometry rather than a generic mirror. If the client has no sample, propose one spread and wait for a yes before the whole book is built.

Can the source stay left-to-right and only the target booklet be rebuilt?

Yes, and that is the usual split. The English file keeps its geometry. The right-to-left file is a new layout linked to the translated strings. Do not overwrite the source masters. Two geometries, two files, two names. A single file with “both directions” hidden in layers is how the wrong one gets exported the night before the event.

The related service page is desktop publishing.

Quick FAQ: AI Translation Accuracy

  • How accurate are AI translators? Accuracy is often high for repetitive or general content, while domain-sensitive content still needs expert review.
  • How to improve AI translation quality? Use glossary control, domain prompts, QA checks, and human post-editing in one workflow.
  • Where does human translation still win? Legal, medical, and high-stakes brand content usually requires human nuance and accountability.