MarginaGet Margina
記事

公開

Right-to-Left and Vertical Text: How Arabic, Hebrew, and Japanese Books Are Laid Out

Right-to-left and vertical text aren't the same thing, though they're often confused. One is about which way a line reads; the other is about whether text runs in columns at all. Here's how EPUBs and reading systems keep the two straight — and what breaks when they don't.

What It Is

A book's layout has two settings that get talked about as if they're one. They aren't. The first is reading direction: does a line of text run left to right, like English, or right to left, like Arabic and Hebrew? The second is writing mode: does text run in horizontal lines at all, or in vertical columns, the way traditional Japanese and Chinese text does? A document can be right-to-left without being vertical. It can be vertical without being right-to-left in the Arabic sense. The two are independent knobs, and a reading system has to get both right.

CSS names these settings plainly. writing-mode: vertical-rl is what a Japanese novel or a Chinese book uses: each column of characters reads top to bottom, and successive columns progress right to left across the page. Mongolian uses the mirror version, vertical-lr — columns still read top to bottom, but advance left to right instead. And when a right-to-left script like Arabic turns up inside vertical text, a quoted phrase inside a Japanese sentence, say, it doesn't switch conventions. It runs bottom to top along the line, the top of each letter facing right, the same orientation it would have on an ordinary horizontal line (W3C, Styling vertical CJK and Mongolian text; MDN, writing-mode).

Why It Matters

Reading direction is set once, for the whole book, at the file's spine level, through an attribute called page-progression-direction. It takes one of three values — ltr, rtl, or default — and it decides something concrete: which page a reading system renders first when it builds a two-page spread. A right-to-left book renders its right-hand page first. That single flag is why a manga volume "turns backwards" next to a Western graphic novel: the spine declares page-progression-direction="rtl", and every spread composes in mirror order from what an English reader expects (IDPF, EPUB 3 Fixed Layout Documents).

Vertical writing mode is a separate decision made separately, inside the book's own content — its CSS says writing-mode: vertical-rl, independent of whatever the spine says about page order. A book can be right-to-left without being vertical (most Arabic and Hebrew titles), or vertical without triggering the RTL page-order flag at all (some modern Japanese web content is set horizontally). Get one right and ignore the other, and you end up with a book that turns pages correctly but renders text wrong. Or the reverse.

Where You'll See It

Japanese still treats vertical setting, tategaki, as its default for novels, newspapers, and manga — columns run top to bottom, ordered right to left across the page, a convention inherited from classical Chinese. Horizontal setting, yokogaki, only became common in the Meiji era, when publishers needed left-to-right lines to interleave with Western-language dictionaries. Plenty of Japanese print today still runs both conventions on the same page: a vertical body of prose next to a horizontal caption, or a stray line of English (Wikipedia, Horizontal and vertical writing in East Asian scripts). If you've read our piece on how apps lay out a document, tategaki is the sharpest example of layout doing real interpretive work. It's not decoration. It's how the text is meant to be read.

Arabic and Hebrew apps face a related but distinct set of decisions. Good RTL support mirrors most of an interface — text alignment, navigation, list layouts — but deliberately leaves some things alone. Phone numbers, clocks, video scrubbers, and musical notation stay put regardless of the surrounding language's direction, because reversing them would make them wrong, not just unfamiliar (Apple, Supporting Right-to-Left Languages). Manga readers hit the same category of decision from the vertical-writing side; see reading CBZ and CBR manga on your phone for how that plays out in a comics reader specifically.

How Margina Handles It

A document that specifies page-progression-direction: rtl or writing-mode: vertical-rl is telling a reading app something about how it wants to be read — not offering a suggestion. Margina renders what a PDF or EPUB declares, rather than flattening every file into the same left-to-right, horizontal assumption. It's the same principle behind turning a fixed PDF into a reflowable EPUB without losing what the original layout was doing. Nothing about a file's own layout metadata gets rewritten or "corrected" along the way. It stays local, untouched, and reads the way its author or publisher set it up to read.

Frequently Asked Questions

Is right-to-left text the same thing as vertical text?

No — they're two separate axes. Right-to-left (Arabic, Hebrew) is about which direction a line of horizontal text flows. Vertical writing (traditional Japanese, Chinese) is about whether text runs in columns at all, and those columns happen to progress right to left. A book can be RTL without being vertical, and vertical without being RTL in the Arabic/Hebrew sense.

Why do manga read "backwards" compared to a Western comic?

Manga pages declare page-progression-direction: rtl at the book level, so a reading system renders the right-hand page of a spread first. It's the same mechanism EPUB uses for any right-to-left book — manga just pairs it with vertical Japanese text.

Does an EPUB's vertical writing mode live in the same place as its reading direction?

Not quite. The overall page-progression-direction is set once for the whole book. Vertical writing mode is set separately, inside the book's own CSS, on the content itself — so a single EPUB has to get both settings right, not just one.

What goes wrong if an app only reverses page order without respecting layout?

You get pages that turn in the right direction but render text incorrectly — Latin words rotated the wrong way inside a vertical Japanese line, or an Arabic quotation inside an English paragraph running the wrong direction. Reading direction and text layout both have to agree.

Conclusion

Reading direction and writing mode are two separate settings. A book's layout only makes sense when a reading app respects both together, not just whichever one happens to be easier to implement. As more readers open documents that weren't written in English or set horizontally to begin with, that kind of layout fidelity — not just translation — is what actually makes a book readable.