Structure and meaning in file reports

Read an EPUB direction report in ManYue: rtl does not reverse three spine entries

Track global progression, document sequence and local writing separately, then check content order with an original three-page story.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

A report can declare right-to-left progression beside an ordered list of three content documents. A direction arrow can be mistaken for reversal of that list. Compare two declarations in ManYue while preserving the story order open door, enter, close door, with separate records for local writing and actual reader settings.

Prepare three original cause-linked panels

Externally draw A opening a door, B entering and C closing it from inside. Add letters and short captions, using door-handle details and clothing colours as return anchors rather than realism to infer order. Export a reading PDF and a separate field report, fixing panels A,B,C and labelling report R. These are self-made static materials, not a tested EPUB. Text in three boxes is sufficient if drawing tools are unavailable, but empty pages with filenames cannot establish correct story content.

Read the unchanged document order from the spine

Map a to A, b to B and c to C, then place the excerpt below on the same report page. Ordered itemrefs remain a,b,c; their sequence comes from element order. rtl does not mean read the list bottom-up. Cover the attribute, state the three contents, then uncover it and check whether you incorrectly switch to c,b,a. This excerpt omits other required publication structures and is not a complete validated ebook. Preserve case, hyphens and quotes rather than insert broken attribute names.

<spine xmlns="http://www.idpf.org/2007/opf" page-progression-direction="rtl">
  <itemref idref="a"/>
  <itemref idref="b"/>
  <itemref idref="c"/>
</spine>

Give each allowed value its own meaning

List ltr,rtl,default as left-to-right, right-to-left and no author preference with the reading system choosing direction. Default is not a universal left-to-right promise, and rtl is not a ninety-degree rotation switch. The global flow declaration does not change these referenced identities or story-event order. Draw a separate progression arrow and numbered document chain instead of one unexplained arrow for both. If absent, record undeclared rather than fabricate a detected value; actual presentation requires another check.

Leave spread placement unknown: rtl alone does not establish whether this first page must be left or right. Single-page versus synthetic-spread behavior,local placement and system choices may matter. Do not fill those missing conditions or present one pairing as universal. The report establishes ordered identities and the global declaration; presentation needs separate evidence.

Separate local writing from global progression

Add a local text box containing Door opens and note independently specified styling. CSS writing-mode concerns writing mode and HTML dir concerns text direction; global rtl does not justify reversing characters to snepo rooD. Content documents or parts may override global flow, and reading systems may offer user overrides. This describes responsibilities without promising particular controls. For layout comparisons create visible examples externally with declared conditions; editing a field string in a PDF report does not automatically rearrange its pages.

A local text control can use the Chinese phrase门开了. Changing language does not automatically reorder references. If the action drawing also changes, label multiple changes rather than call it a writing-direction-only comparison.

Read content and report as separate ManYue tasks

Import both clearly named PDFs. Read panels A,B,C to establish opening before entering before closing, then inspect report R’s rtl and reference order. Bookmark its key page and externally record orientation, single/double-page layout and any visible reading-direction setting. Compare only controls that exist; otherwise record unavailable without inventing gestures or button names. The PDF’s fixed sequence came from external export. Reading it successfully does not establish EPUB-attribute handling, so name the opened file type in observations.

Make separate direction-only and list-only controls

Copy R to L and change only rtl to ltr; references remain a,b,c and the story stays open,enter,close. Copy another report to O, retain rtl but reorder itemrefs c,b,a: this changes document sequence. Label each change on its cover rather than replace both panels and attributes and attribute everything to direction. Paper-only controls can be report pages without real EPUB files, provided they are labelled models. These separate changes show why both concepts affect reading yet are not one field.

Locate mistakes through state and character checks

If closing precedes opening, identify O versus R and check exported PDF order before changing every reader setting. Correct order with reversed letters calls for inspecting source text; vertical content calls for external layout or actual rotation checks rather than blaming rtl for every direction. After zooming return to the whole report to avoid attaching L’s field to R’s observations. Retain errors and one-change corrections. Without trying a direction control, stop at report reasoning rather than claim its influence was ruled out.

Reopen and state three separate conclusions

Reopen the bookmark and state global rtl, document sequence a-to-c and locally conditioned writing, then revisit all three panel anchors. Acceptance is evidence for each field or visible content rather than apparent swipe direction. Save R,L,O and actual operations, leaving unperformed reopening pending. A later EPUB-capable tool needs fresh implementation and user-override observations; this PDF reading is not its compatibility guarantee. Deliver enough labels for another reader to distinguish sequence, progression and writing without guessing arrows.

EPUB language scope; Reading layout and spreads.

Method references: W3C EPUB3.3 section5.7.1. Diagrams, report data, counterexamples and ledgers are original exercises.

Version checked on 17 November 2026: the Apple public lookup lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later; see the official App Store for published capabilities. Use self-made PDFs or supported comic images; controls depend on the installed version. External preparation and paper predictions do not constitute device observations. Leave unperformed checks blank.