ManYue volume filenames: distinguish numbering, editions and extras

When volume ten appears before volume two, the problem may lie in filenames or sorting rather than page order inside the reader. This exercise creates a naming plan before import so volumes remain identifiable. Internal page order is a separate check, and renaming files does not automatically merge existing shelf entries.

List the main volumes and extras

Make an inventory containing the series, volume, edition, language and extra-volume status of every file. Inspect contents or publication information when a cover number is ambiguous. An omnibus can include several volumes, and a special edition may share a number with a standard one. Keep uncertain items aside until you identify them. A simple table is sufficient.

Choose one width for volume numbers

Use two digits for a series of a few dozen volumes, or three digits when needed. Apply the same width to every volume after a common series name. Avoid mixing Chinese number words, Arabic numerals and descriptive labels in the numeric position. Padded names make lexical file sorting easier, but you must still verify the app’s chosen shelf order after importing.

Put edition information in a stable position

Place a consistent edition label after the volume number when keeping colour, monochrome, revised or translated editions. Avoid vague labels such as “new” without identifying the difference. Keep detailed provenance in the inventory rather than an excessively long filename. Rename working copies and preserve originals. Reimporting a renamed file may create another entry instead of transferring existing progress.

Identify extras and omnibus volumes

Label extras explicitly with their own sequence, and identify the included range in an omnibus. Do not invent main-series volume numbers for bonus material. Decide whether extras belong beside the main books or in a separate shelf group. Filenames should identify a file; the app’s shelf tools can handle reading priorities and organisation where available.

Validate three volumes before a batch

Test working copies of volumes one, two and ten first. Preserve their actual extensions and check displayed titles, covers, order and contents after importing. Embedded information or import rules may influence a displayed name. Inspect the available sorting controls and record the selected mode. A small trial exposes naming problems before a full series fills the shelf.

Connect shelf entries to original files

Record which inventory items were imported and their actual shelf names. If you use groups, leave and reopen the target group to confirm the result. Before replacing a volume already in progress, note its chapter and a recognisable scene. File storage, shelf membership and progress are separate objects. Finish identification before deleting old copies.

Check gaps separately from duplicates

Check numeric gaps against the original inventory; do not renumber another volume to conceal a missing book. Open apparent duplicates because shared covers and similar file sizes do not establish identical contents. Confirm the edition before removing an extra entry, and read the app’s deletion prompt to understand its scope. Keep the previous inventory for traceability.

Questions and a reverse check

Why can padded filenames still appear in import order? Check the selected shelf sort; names do not control every list. Should all volumes go into one large archive? That changes the packaging task and is unnecessary for this naming exercise. Finally inspect the series backwards, reading each number and edition aloud. Completion means finding the correct shelf volume and tracing it to its original file.

Related guides and sources

Organise ManYue shelves: to read, reading and finished; ManYue file formats: choose CBZ, CBR, CB7 or PDF and check page order.

Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.