One-time downloads · $0.99 USD. No subscription.

Perunlight

Step-by-step guide

FolioMend

Revise a book index after pages move. Compare old and new passages, choose explicit destinations, and deliver a corrected index with a reason for every change.

You already have an editable index and need to revise page references after text moves between pages in a short book or proof section.

Get FolioMend · $0.99

See it in use

Repair seven index locators after pagination

A screenshot walkthrough with fictional practice data. Select a step to explore.

1. Start with

Repair seven index locators after pagination

The fictional Rain Barrel proof moves passages and removes a brass-tap entry.

Sample files and contents

Old page 12 contains screen and winter-storage passages; old 13 contains overflow and a brass-tap passage. The new proof splits, repeats and removes material.

Practice files and guides are free. The complete app is included only where the product page says so.

2. In the app

Confirm printed labels separately from PDF positions: i;12;13 in the old proof and i;13;14;15;16;17 in the revision.
Confirm printed labels separately from PDF positions: i;12;13 in the old proof and i;13;14;15;16;17 in the revision. Enlarge image ↗

Try it in three steps

  1. Inspect each old and new passage before assigning locators.
  2. Approve split maintenance locators and remove the obsolete brass-tap locator.
  3. Export the corrected index CSV and compare expected rows.
Show every click and setting
  1. Approve foreword i, inlet screens 14, winter storage 15 and overflow 16 after inspecting their passages.
  2. Approve the two maintenance atoms separately as 14 and 16; remove the brass-tap locator with a reason.
  3. Clear and approve the tap care cross-reference, then compare the downloaded CSV with expected.json.

3. The result

Inspect the result

The CSV keeps the source row order. Maintenance points to pages 14 and 16; the removed entry has an empty locator.

The actual HTML handoff includes the seven source rows and extra columns. Maintenance refers to 14 and 16; the removed brass-tap locator remains as an empty field.
The actual HTML handoff includes the seven source rows and extra columns. Maintenance refers to 14 and 16; the removed brass-tap locator remains as an empty field. Enlarge image ↗
What to check in the practice result

foreword i; inlet screens 14; winter storage 15; overflow 16; maintenance 14;16; brass taps has an empty locator; tap care has a cleared cross-reference. Source row order and other fields remain. Seven locator decisions and one cross-reference decision are recorded.

This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.

See the workflow at a glance

Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.

One old locator can become two reviewed pages.

Repagination is not always a constant page offset. In FolioMend's fictional Rain Barrel exercise, maintenance becomes two approved locators, 14 and 16, while the removed brass-tap passage leaves an empty locator with a recorded reason. Inspect each passage and approve every decision before exporting the revised index CSV. Word overlap helps navigation; it does not establish meaning. Proofs need extractable text, and scans are rejected. The workflow was verified on Linux with Python and Chrome; the guide explains supported locator syntax and the need to reapprove reopened decisions.

View the illustrated card
One old locator can become two reviewed pages. — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card
The Page Moved. Check the Passage.

In FolioMend’s fictional rain-barrel proof, old page 12 splits into later passages. A candidate page match is a place to inspect, not a decision to trust automatically. Review the inlet-screen passage, approve its locator as 14 and keep the decision with the revised index export. Every locator needs human approval; word overlap does not establish semantic correctness. The guide shows repeated and removed material too, and lists the text-PDF limits before you consider the $0.99 tool.

View the illustrated card
The Page Moved. Check the Passage. — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card

Before you start

  • Python 3 and desktop Google Chrome. Independently checked on Linux x86_64, Python 3.10.12 and Chrome 152.0.7977.82.
  • Extract FolioMend-1.0.1.zip completely. In its FolioMend-1.0.1 folder run python3 serve.py, then open http://127.0.0.1:8765/app/ in desktop Chrome. Choose Load practice case. Python 3 is required; all runtime assets are included. No npm installation or internet connection is needed. Opening app/index.html directly will not work.
  • Two unencrypted text PDFs and an index with unique nonblank column headers. Map a heading, locator and optional cross-reference column. Additional columns remain in the canonical output.
  • Use UTF-8 CSV with standard quoted fields, or simple TSV without tabs/newlines inside fields. Your index and approved destinations must use labels present in the confirmed proofs.

Your first result

  1. Open the practice case

    Start the supplied local server, open its loopback address and choose Load practice case. The old proof has printed labels i;12;13; the new proof has i;13;14;15;16;17. Inspect the page renders and choose Confirm numbering & begin review.

  2. Review foreword, screens and storage

    Approve foreword → i even though it is unchanged. Select the inlet-screen sentence in the old proof and choose Use selected passage, then Find possible destinations. Read the candidate excerpts: pages 14 and 17 repeat the words, but 17 is a summary. Inspect proof opens a page without selecting it. Add page selects the main discussion on 14; Remove page reverses that selection. Check the printed destination field and approve with a reason. For winter storage, inspect the “Drain and disconnect…” passage and approve 15.

  3. Resolve split and deleted material

    Approve overflow → 16. Maintenance has two separate old locators: approve old 12 → 14 using the screen passage and old 13 → 16 using the overflow passage. For brass taps, select the old passage, record that it was removed from the new proof and choose Remove this locator.

  4. Clear the cross-reference

    After all seven locator decisions, clear the brass taps target in the tap care cross-reference, explain the removal and approve it. Any later locator decision resets cross-reference approval.

  5. Download and inspect the handoff

    Download Corrected CSV, Spreadsheet-safe CSV, Readable HTML, Plain text and Review ledger as separate files. Compare the canonical CSV with the expected answers. The maintenance locator is 14;16, not a continuous range. Use the safe copy when viewing in a spreadsheet; it deliberately prefixes formula-like cells.

  6. Save before closing

    Choose Save project and verify the JSON download. It contains original proofs and is private working material. Reopen it through Reopen project, confirm numbering and reapprove the draft decisions. Stop the server with Ctrl+C when finished. Nothing is automatically saved or overwritten.

A worked example

Measuring a Rain Barrel — original fictional practice case

Input: Old page 12 contains screen and winter-storage passages; old 13 contains overflow and a brass-tap passage. The new proof splits, repeats and removes material.

  1. Approve foreword i, inlet screens 14, winter storage 15 and overflow 16 after inspecting their passages.
  2. Approve the two maintenance atoms separately as 14 and 16; remove the brass-tap locator with a reason.
  3. Clear and approve the tap care cross-reference, then compare the downloaded CSV with expected.json.

Expected result: foreword i; inlet screens 14; winter storage 15; overflow 16; maintenance 14;16; brass taps has an empty locator; tap care has a cleared cross-reference. Source row order and other fields remain. Seven locator decisions and one cross-reference decision are recorded.

Troubleshooting

Opening the HTML file fails

Run python3 serve.py from the extracted FolioMend folder and open http://127.0.0.1:8765/app/. The Python local server is required.

The local port is already in use

Stop your previous FolioMend server with Ctrl+C. Do not stop unrelated processes; this version has no custom-port setting.

A proof is rejected or extracts poorly

Use an unencrypted text PDF with text on every page. There is no OCR. Compare extracted text with the rendered page and enter destinations manually when reading order is poor.

Numbering cannot be confirmed

Enter exactly one unique supported printed label per physical page. Do not confuse a PDF position with its printed page number.

Export is still disabled

Approve every atomic locator, including unchanged ones, then review every cross-reference. Changing numbering or mapping invalidates approvals; changing a locator resets cross-reference review.

Reopened decisions are no longer approved

This is expected. Confirm numbering and reapprove the restored drafts before delivery. Save a project before loading another job.

Changing work while files open

Using a different selected passage clears that locator approval and the cross-reference approvals. Review and approve again before exporting. Only the latest started project, proof import or practice load can replace the workspace; an older delayed read cannot overwrite it. An unreadable replacement preserves the current project.

Suggestions disappear after changing the supporting passage

This prevents choices based on the old passage. Choose Find possible destinations again and inspect the new excerpts. Every destination still needs your approval; word overlap is not proof of the right meaning.

Compatibility & limits

  • 100 physical pages, 10 MiB and one million extracted characters per proof. Every page must contain extractable text; scans, blank pages and encrypted PDFs are rejected.
  • 500 index rows, 1,500 expanded locators, 30 columns and 1 MiB of UTF-8 CSV or TSV. Saved projects have a 64 MiB cap.
  • Arabic labels 1–9999 and lowercase Roman i–xxx. Use full ranges and semicolon lists. Abbreviated ranges, page suffixes, volume prefixes and duplicate printed labels are unsupported.
  • Every locator needs human approval. Word overlap helps navigate; it does not establish semantic correctness. No OCR, native Cindex/SKY import or publisher-specific typesetting.
  • No autosave or undo history. Save before changing jobs. Reopened decisions are drafts and require reapproval. Private project files embed the original proofs.
  • Verified on Linux x86_64 with Python 3.10.12 and Chrome 152. Other operating systems and browsers, customer proofs, physical phones and physical printing are unverified. Desktop is recommended; browser layouts at 390px and 320px were checked.
  • Canonical CSV preserves field strings and row/column order, except explicit locator and cross-reference edits; byte-level quoting is regenerated. Use the separate safe CSV for spreadsheet viewing.
  • CSV supports commas, doubled quotes and quoted newlines; TSV is simple tab-separated text. HTML/TXT are readable outputs, not a publisher-specific hierarchy or layout.
  • The launcher binds only to 127.0.0.1; input files are processed in the browser. Source proofs are included in saved private projects, not in exported index files. No accounts, cloud sync or external runtime requests.

Need a hand?

Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.