Check EPUB language declarations in ManYue: publication metadata and local content have different scopes

An EPUB language declaration is neither an automatic translation control nor an application-menu preference. Inspect an original bilingual EPUB externally and save a short report as a supported PDF for reading and return in ManYue. Record publication language, chapter-root language and local passages separately, without requiring XML inspection in the app or guaranteeing every EPUB variant on a given path.

Build a two-paragraph original sample

Externally prepare a Chinese main paragraph and an English paragraph, such as an original Chinese statement about a lamp and The lamp is by the door. Record container, package path and XHTML path, preserving the source. Neither en in the filename nor English on the cover establishes declarations. Without a creator tool, use a clearly labelled paper report rather than claim an EPUB was generated. Produce the PDF report externally; ManYue reads it without an invented format-editing feature.

Read the first package language element

The example lists <dc:language>zh-Hans</dc:language> first and <dc:language>en</dc:language> second. The first declares the publication’s primary language; repeated elements can describe multilingual content, not a fabricated concatenated tag. Preserve document order rather than alphabetise and then infer a different primary language. Tags describe language and optional refinements, not file paths, server locations or copyright jurisdiction; do not replace zh-Hans with a translated book title or folder name.

Do not assume the chapter inherits package metadata

Publication resources do not automatically inherit language from dc:language, so inspect the chapter’s own language mechanism. This XHTML root uses matching xml:lang="zh-Hans" and lang="zh-Hans". Give package metadata and root attributes separate columns rather than call an omitted chapter declaration correct because the package mentions Chinese. This concerns document declarations, not a guarantee that an app path exposes them or selects a particular voice. Missing evidence cannot establish internal language handling.

Inspect the scope of a local English span

The English paragraph can carry matching xml:lang="en" and lang="en" on its own element, differing from the Chinese root. Record start, end and enclosed text; do not extend a local declaration into later Chinese text outside that element. A span around one word covers that word, not the whole page. Read the text to check the declaration: an incorrect attribute cannot transform Chinese into English, and a present tag alone does not establish correctness.

Separate language from reading direction

Record language separately from direction. English or Chinese declarations do not directly set page progression, right-to-left paragraphs or vertical CSS layout. Language, direction, progression and styling are distinct conditions. Rightward comic paging does not make the content Japanese; horizontal English does not require an English-primary package. Leave direction unchanged and unexamined here instead of altering layout while fixing language. Image-based lettering likewise does not become searchable OCR merely through a language attribute.

Read the declaration-to-text report as PDF

Externally make a short PDF listing package order, root language, English scope and both original paragraphs. Label it an inspection report, not proof of faithful EPUB rendering. Open through a supported local PDF path in ManYue, enlarging quotes, hyphens and the English sentence and recording marker and location. If report wrapping breaks a tag visually, consult the original field rather than infer added XML characters. Reading and returning to the report does not establish an unperformed direct EPUB import.

Check interface-language and declaration mismatches

English menus can coexist with Chinese publication metadata; this alone requires no file change. An English passage inheriting a Chinese root without a local declaration calls for a recorded scope mismatch and authorised external correction of a copy. Underscore-style tags or several values forced into one element require specification and validator checks; opening a file does not establish valid metadata. Change only confirmed issues and preserve both reports. Translated text is not evidence that the declaration itself performed translation.

Reopen and reconstruct three language scopes

Reopen the report PDF, confirm identity and original paragraphs, then reconstruct package primary language, chapter root and local paragraph scopes, keeping menu language separate. Retain paths, element order, covered text and unknowns, explaining the absence of automatic dc:language inheritance. Reinspect relevant scopes after adding chapters or changing language order rather than edit a cover or filename alone. Completion is traceable declaration-to-text correspondence, not proof of automatic translation, EPUB repair or every language-assistance feature in ManYue.

Related guides and sources

Check EPUB identity in ManYue: unique-identifier points to an identifier element, not a title; ManYue EPUB image order: separate the manifest, spine and image occurrences.

Checked on November 14, 2026: Apple public information lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. See the official App Store for published capabilities; verify specific controls in the installed version.

Method reference: W3C: EPUB dc:language and resource language scope. Samples, passages and controls are original exercises. Sources establish definitions and checking methods rather than new automatic analysis in the app. Manual records may be kept externally, and unknown fields should remain explicit. This article does not claim step-by-step testing on a physical device, private server or every output environment.