0 votes
359 views

The translators I work with often combine verses–sometimes two, sometimes three. We use a comma as a separator, and include the number of every verse that has been combined, e.g., Gn. 31:17,18,19 (mostly so that new readers won’t be left wondering what happened to verse 18 if it was written Gn. 31:17-19).
Anyway, when I produce a Print Draft and combined verses are at the top of a page, the header reads: 31:17,18,19-32. Is there any way to have it read: 31:17-32?

Paratext by (642 points) | 359 views

1 Answer

0 votes
Best answer

I think this will do it, or at least get the conversation started.

Here’s what to do:
Open or create "My Paratext Projects\YOURPROJECT\custom.sty"
Add

\Marker v
\TextProperties verse nonpublishable

Open or create "My Paratext Projects\YOURPROJECT\PrintDraftChanges.txt"
Add

"\\v\ ((\d*)(.*?)(\d*)?)\ " > "\\v \2-\4 \\vp \1 \\vp* "
"-\ " > " "

Why it (hopefully) works:
As you send your text to draft, you’re changing verse numbers so that \v marks what PT expects to see, i.e. hyphens in ranges. You’re also adding \vp which says which text should actually be printed. In your PrintDraft, the header references are read from \v and hence will display correctly.

I’m not very good at using Regular Expressions, so I’m not confident mine will work perfectly but I know I have the general idea down. The second line "-\ " > " " is necessary because I couldn’t find a way to not create a hyphen when the verse only had a single reference in it, so I just created it and then deleted it when necessary.

Sidenote: In my opinion the edits to custom.sty should be unnecessary, as should my forcing every verse to have both \v and \vp markers. This is because ptx2pdf, the TeX macros behind PrintDraft, fail to follow what I think should be a simple rule: If \vp exists then print \vp and not \v. Else print \v.

[Edited to fix Regular Expression]

by (1.9k points)
reshown

Sorry to say, it doesn’t work… With the lines added to PrintDraftChanges.txt, I get ‘marker errors’ that prevent a Print Draft from being created. With the lines commented out (with #), Print Draft works again. So there’s something up with the regular expression.
I appreciate you taking a crack at it, but don’t waste too much time on it–it’s not a big deal!

Strange, I found that mistake yesterday and corrected, but obviously copied and pasted the wrong regex line onto the webpage. There was simply an extra \ in my line.

"\\v\ ((\d*)(.*?)(\d*)?)\ " > "\\v \2-\4 \\vp \1 \\vp* "

This one works. Thanks!

Related questions

0 votes
4 answers 504 views
Tildes (used in USFMs as non-breaking spaces) disappear when the view is changed in Preview view, as expected. ... . Am I missing some step that would make these disappear?
Alex W. 191 asked Jul 13, 2018
+1 vote
1 answer 252 views
I want to export a Japanese project that has ruby text to RTF (Print Draft will be okay if necessary). So far, I have ... the project is set to USFM 3. Thank you for your help.
anon180868 195 asked Dec 28, 2020
0 votes
2 answers 313 views
One user wants to use print draft but is encountering an error which says marker errors detected , when certain ... user be concerned about the message seen in print draft?
anon310851 135 asked May 8, 2018
0 votes
0 answers 164 views
While I have submitted a problem report, it does not include one of the screen shots, so I thought someone ... Roman (but trying different fonts changed nothing.) Iver+Larsen
Iver Larsen 869 asked Apr 9, 2018
0 votes
4 answers 571 views
We have a user who is experiencing a problem where a certain character combination does not present correctly using the Print ... when the user should get Any ideas? Thank you.
MSEAIT_LT 478 asked Mar 21, 2018
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
There is neither Jew nor Gentile, neither slave nor free, nor is there male and female, for you are all one in Christ Jesus.
Galatians 3:28
3,041 questions
5,999 answers
5,665 comments
2,023 users