Printing from a module spec omits first few pages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
When I print a Bible Module directly in PTXPrint the first few pages are skipped. When I load the same Module spec. into XXA and print that book in PTXPrint it prints correctly. (Ignore too-big titles and other bits, I need to get this working before fine-tuning it).
I've included the current PTXPrint "Scope" setting above each PDF in the pics to identify them. The first pic is correct. The second pic shows "page 1" starting with the third reading (Epistle) under "1st Sunday of Advent."
- I upgraded PTXPrint to the latest version today; the same thing happened with the previous version last week.
- The same Module file is called for both printings. Same thing happens with all of my 10+ Catholic Sunday Readings modules.
- I upgraded PTXPrint to the latest version today; the same thing happened with the previous version last week.
- It is much more convenient to print directly from the Module specs, as I'm sure you know. I hope this isn't hard to fix.
- Another odd thing I just noticed: The PDF with the first 3-4 pages missing has 62 total pages. The file that includes the entire module text has 61 pages! I haven't examined this yet but it looks as if styles might be applied differently, because they are both printed with the same PTXPrint Layout.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the attached kyxPublx-LiturgyReadingsPTXprintArchive.zip, comparing a module spec printed directly in PTXPrint with the same module loaded into XXA. Compare the generated PDFs and Scope settings, then trace the direct-module printing path; done means the initial pages and total output match the working route.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100