Image, layout and catalog fields

Check catalog times in ManYue: published and updated do not replace volume order

Convert offsets in an original Atom report and separate first availability, entry updates, feed updates and comic chapters.

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

Nine in the morning need not be later than another entry’s 02:30 because offsets can differ. Prepare two original OPDS 1.2 entry reports, normalize to UTC and keep published, updated and volume identity separate. Browse an authorized catalog in ManYue or read a report PDF. Paper checking works without a server and is not a claimed private-catalog test.

Fix the Atom-based version and two entry identities

Limit the exercise to OPDS 1.2 Atom XML. Entry A is“山路卷二”(Mountain Road volume 2), B volume 1, each with stable identity and an original cover marker. List title, id, published and updated per entry rather than copying feed updated into all entries. A different-generation JSON catalog needs its own field rules, not automatic reuse of XML element names. For offline reading export the table/covers as a two-page PDF and identify it as external material, not an app-generated protocol report.

Read the meanings of published and updated first

Atom published identifies an early event in an entry’s lifecycle, usually associated with creation or initial availability; updated identifies the most recent modification considered significant by the publisher. Neither automatically means story date, print publication date or completed download time. Title/description corrections can update an entry without new chapters. Retain unknown or absent fields rather than substituting updated as the original work’s debut. Identify the resource represented by each field before comparing A/B: correct arithmetic cannot fix comparing different objects.

Convert A’s plus-eight offset to UTC

Set A updated to 2026-11-16T09:00:00+08:00. Its clock is eight hours ahead of UTC, so subtract eight hours to obtain 01:00:00Z on the same date. Do not add eight to get 17:00 or treat the plus sign as an arithmetic instruction rather than an offset. Preserve date, T separator, seconds and offset; 09:00 alone loses comparison conditions. This is an original exercise instant, not a claimed private-server update. Calculate externally without assuming an in-app UTC converter.

Compare B after retaining both original strings

Set B updated to 2026-11-16T02:30:00Z, already UTC and 90 minutes later than A’s 01:00. Comparing 09 against 02 alone incorrectly orders different clocks. Keep original strings beside normalized instants to distinguish copying from conversion errors. Direct string ordering needs matching offset/representation conditions; this example explicitly avoids that shortcut. Volume 1 being updated later than volume 2 does not automatically change story reading order to 2 then 1.

Check an initial time across a date boundary

Give A published 2026-11-15T20:00:00Z. In plus-eight time that is November 16 at 04:00, five hours before A’s 09:00 updated. Crossing 15 to 16 does not mean a two-day interval; normalize before subtraction. The interval connects declared events, not reading duration or drawing time. If actual updated precedes published, preserve the anomaly and inspect source clocks rather than silently swapping fields. Do not invent an instant from a timestamp lacking an offset by assuming your own region.

For another rollover check, November 15 at 23:30:00-07:00 converts by adding seven hours to November 16 at 06:30:00Z, four hours after B’s 02:30:00Z. It is not seven hours earlier. Positive and negative offsets use the same relation, local=UTC+offset. Rearrange that relation rather than memorizing inconsistent shortcuts.

Browse visible sorting while checking work identity

With an authorized OPDS library, verify A/B titles and cover markers in ManYue before recording visible sorting controls and actual order. Missing timestamp display neither proves no parsing nor guarantees updated-based sorting. In the report PDF use separate arrows for temporal and volume order so differences remain explicit. Ordinary whole-package OPDS entries gain no direct page-reading capability from these fields; retain the published protocol boundary. This lesson studies metadata without changing download or reading protocols.

Add a declared feed update of November 16 at 03:00:00Z, later than both entry updates. That does not mean every work changed at 03:00. Collection-level changes can concern its entry list; inspect publisher scope. If the interface merely says recent, record its level instead of swapping it with volume order or initial availability.

Diagnose feed times and missing offsets

Identical copied times may come from feed updated instead of each entry’s value. A sixteen-hour error can result from adding eight instead of subtracting eight; a one-day error calls for checking midnight rollover. Server configuration or caching may need separate investigation, but one list order proves no unique cause. Retain original strings and parser behavior when correcting, rather than deleting offsets for superficial consistency. Share an original table and field paths while removing private URL tokens; credentials are unnecessary.

Reopen and answer with two separate orders

Reopen the catalog/report, identify A/B by id and marker, then recalculate 01:00Z, 02:30Z, the 90-minute difference and A’s five-hour published-to-updated interval. Answer separately which declared instant is later, which volume comes first and what the current interface actually shows. Keep original reports, normalized columns and observations, marking unknown sort rules. Recheck semantics after changing server, offset or catalog version. A list order is not original publication order, and an updated timestamp does not guarantee new comic content.

Related tutorials and sources

Catalog pagination and content; OPDS reading scope.

Sources checked on 16 November 2026: Apple public lookup shows ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. Published reading capabilities appear in the official App Store listing. Use controls actually available in the installed version.

Method references: RFC 4287 Atom date elements; RFC 3339 offsets and ordering; OPDS 1.2 specification. Diagrams, numbers, counterexamples and recording arrangements are original exercises. Separate external preparation, paper expectations and actual reading results. Available documentation does not substitute for device observation, and no private-server or universal file-environment test is claimed.