EPUB language settings involve two editorial decisions: the publication’s bibliographic language and the visible labels used for navigation, colophon fields, and dates.
When working on EPUB language settings, consider a Japanese-language art book with an English work title and a Western-style numeric date. The task is complete only when primary language of the prose and year-month-day presentation can both be confirmed after the saved output is reopened. An export message by itself does not answer the search question.
Decide what success means for this book
For this example—a Japanese-language art book with an English work title and a Western-style numeric date—the first decision is whether primary language of the prose has a known starting value. The final decision is whether year-month-day presentation survives export and reopening. Keeping those two moments separate prevents a temporary editor display from becoming the handoff criterion.
Preserve the received manuscript, edit a trial manuscript, and write the EPUB separately. With EPUB language settings as the goal, those three files keep the source, intentional edits, and packaged book distinct.
The direction is one-way: preserved source, editable duplicate, separately written EPUB, then a reopened EPUB. The method does not recreate the manuscript from the EPUB or treat the package as an editing source.
Build a representative test case
Build the example around a Japanese-language art book with an English work title and a Western-style numeric date. Keep the part that could genuinely fail. If the risk concerns visible navigation heading, include the exact chapter, character, path, or label that creates that risk. Removing it for a cleaner demo would produce an easy pass with no value for the real book.
Review four independent facts
- Primary language of the prose: while you choose the reader’s primary language, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from visible navigation heading.
- Visible navigation heading: while you separate proper names from interface-like labels, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from colophon field labels.
- Colophon field labels: while you record desired navigation, colophon, and date wording, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from year-month-day presentation.
- Year-month-day presentation: while you export and review the relevant pages, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from primary language of the prose.
Complete the operation in order
- Choose the reader’s primary language. Before moving on, confirm primary language of the prose; if it differs from the expected state, correct that step rather than compensating later.
- Separate proper names from interface-like labels. Before moving on, confirm visible navigation heading; if it differs from the expected state, correct that step rather than compensating later.
- Record desired navigation, colophon, and date wording. Before moving on, confirm colophon field labels; if it differs from the expected state, correct that step rather than compensating later.
- Export and review the relevant pages. Before moving on, confirm year-month-day presentation; if it differs from the expected state, correct that step rather than compensating later.
- Compare display text with the OPF language code. Before moving on, confirm primary language of the prose; if it differs from the expected state, correct that step rather than compensating later.
Walk the example from source to handoff
During step 1, choose the reader’s primary language. In the case of a Japanese-language art book with an English work title and a Western-style numeric date, review primary language of the prose before changing anything else. This prevents using title language as the package language. If the observation is unknown, repeat that step with the trial manuscript instead of editing the master manuscript.
During step 2, separate proper names from interface-like labels. In the case of a Japanese-language art book with an English work title and a Western-style numeric date, review visible navigation heading before changing anything else. This prevents expecting a reader to rewrite editorial date text. If the observation is unknown, repeat that step with the trial manuscript instead of editing the master manuscript.
During step 3, record desired navigation, colophon, and date wording. In the case of a Japanese-language art book with an English work title and a Western-style numeric date, review colophon field labels before changing anything else. This prevents claiming visual readability from recorded settings alone. If the observation is unknown, repeat that step with the trial manuscript instead of editing the master manuscript.
During step 4, export and review the relevant pages. In the case of a Japanese-language art book with an English work title and a Western-style numeric date, review year-month-day presentation before changing anything else. This prevents using title language as the package language. If the observation is unknown, repeat that step with the trial manuscript instead of editing the master manuscript.
During step 5, compare display text with the OPF language code. In the case of a Japanese-language art book with an English work title and a Western-style numeric date, review primary language of the prose before changing anything else. This prevents expecting a reader to rewrite editorial date text. If the observation is unknown, repeat that step with the trial manuscript instead of editing the master manuscript.
What the example showed
The trial produced this observation: The layout read back pattern=h2, linked scroll enabled, 17-point content, 14-point UI, and 2 tabs.
That value belongs to the files and settings used for this example. It supports the documented sequence; it does not turn EPUB language settings into a promise for every manuscript, reading system, or retailer.
The untested boundary is equally important: The recorded settings do not establish readability or visual scroll alignment; chapter-ID screen checks remain separate. Outside this scope: Readability remains personal and one setting is not promised for every manuscript. Add retailer preview, device testing, accessibility review, or rights clearance when the book requires those decisions.
Recover from the three likely mistakes
- Using title language as the package language: go back to “choose the reader’s primary language,” then re-examine primary language of the prose. Change only the responsible input so the next comparison remains meaningful.
- Expecting a reader to rewrite editorial date text: go back to “separate proper names from interface-like labels,” then re-examine visible navigation heading. Change only the responsible input so the next comparison remains meaningful.
- Claiming visual readability from recorded settings alone: go back to “record desired navigation, colophon, and date wording,” then re-examine colophon field labels. Change only the responsible input so the next comparison remains meaningful.
Decide whether Rune Studio fits
Rune Studio is a candidate when an editor wants manuscript work and EPUB preparation in one Mac application for a project involving a Japanese-language art book with an English work title and a Western-style numeric date. Product documentation describes available functions; the observation above documents only this example.
See the product on the Rune Studio website. Keep the adoption boundary explicit: readability remains personal and one setting is not promised for every manuscript.
Take the next step
Start with this action: choose the reader’s primary language. Then follow the remaining steps until year-month-day presentation can be reproduced from the reopened publication. That is the practical finish line when working on EPUB language settings.