sillsdev / sillsdev/ptx2pdf

Psalm Book Section Formatting

Open
#1,235 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
33
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Not sure if this is a Paratext issue, PTXPrint issue or something I've done.
This is what is in Paratext:

Image

So, each Psalm starts with \c

In this case, there is the book section text marked with the \ms marker and comes after the \c .

However, PTXPrint prduces this:
(The rectangle was not produced by PTXPrint).

Image

so the order of the \c and the \ms have been reversed.
Is this meant to happen?

THAMI-PsalmsPTXprintArchive.zip

What is wanted is to have the book section appear before the Psalm number. It is possible to do this by editing the Paratext source file by placing the book section text at the end of the previous Psalm as Paratext seems to insist on a chapter beginning with \c and nothing preceding it. Normally a typesetter can't change the Paratext file, so this isn't really an option.

I have been able to do this in the changes.txt file:

at PSA 42:0 '\s1' > '\s1 x'
at PSA '\c 42' > ''
at PSA '\s1 x' > '\c 42\r\n\s1'

which produces:

Image

Archive attached.

Thanks

Alastair

THAMI-PsalmsPTXprintArchive.zip

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached THAMI-PsalmsPTXprintArchive.zip and inspect the supplied changes.txt, comparing the Paratext source order with PTXPrint's output. Reproduce the Psalm 42 case and trace the handling of \c and \ms markers. Done means the book section appears before the Psalm number without requiring manual edits to the source or changes.txt.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, tex
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.