What problem does this solve?
Useful printable content is often tacked onto the end of a larger book — a blank character sheet, a map, a spell reference, a handout. To use just those pages today you'd have to open the whole book and page to them every time, or crack out an external PDF tool to split them off.
What would you like to see?
An option to export a range of pages from an existing PDF into a new standalone document:
- Pick a start/end page (or a set of pages).
- Produce a new PDF (or added library item) containing just that range — e.g. a character sheet, map, or spell sheet extracted from the back of a book.
- Give it a name so it lands as its own browsable item.
Have you found any workarounds?
Splitting the PDF externally with a separate tool and re-importing the result, which is clunky and defeats the point of an in-app library.
Anything else?
Backend already uses PyMuPDF for rendering, which supports page extraction/subsetting — so producing a new PDF from a page range should be feasible without new dependencies.
What problem does this solve?
Useful printable content is often tacked onto the end of a larger book — a blank character sheet, a map, a spell reference, a handout. To use just those pages today you'd have to open the whole book and page to them every time, or crack out an external PDF tool to split them off.
What would you like to see?
An option to export a range of pages from an existing PDF into a new standalone document:
Have you found any workarounds?
Splitting the PDF externally with a separate tool and re-importing the result, which is clunky and defeats the point of an in-app library.
Anything else?
Backend already uses PyMuPDF for rendering, which supports page extraction/subsetting — so producing a new PDF from a page range should be feasible without new dependencies.