0 votes
279 views

In the Body Tab, under “Include Scripture Text” there is a selector for “Glossary Words Markup Style”. Even though I have set this to “None”, PTX print seems to think it’s stuck on “star *before word”, as shown in the picture below. I’ve tried to change it to other settings, but only the “star *before word” behavior is observed.

Thank you for your help!

PTXprint by (120 points) | 279 views

2 Answers

0 votes

Thanks @ChristopherF for alerting us to this bug. We weren’t able to reproduce this, but have just made a change to the code which we hope has fixed the issue. We hope to release 2.0.4 with this and a few other minor fixes in the next few hours. Could you report back to us if the fix worked; and if not, we’ll keep digging.

by (3.2k points)
reshown

Hello @mjpenny! Unfortunately, the problem persists. What more information would be helpful for me to provide for you? Here’s what I’ve noticed since:

In the unformatted Paratext file, the glossary markup looks good:

In “formatted” view in Paratext, no asterisks appear:

But I noticed that, in PTXprint in the “View+Edit” pane, in the “Final SFM” tab there are asterisks in the text here.

I don’t know whether this is the expected behavior when Body → Include Scripture Text → “Glossary Words Markup Style” is set to “star *before word” but it is currently set to “None”.

Thank you so much for helping me through this :slight_smile:

Hi again @ChristopherF - thanks for the screenshots which help us understand what you’re seeing. At this point, the easiest way for us to replicate the issue is for you to send us an archive using the instructions in this post. We’ll then be able to figure out why it isn’t doing what we expect. Thanks.

0 votes

@ChristopherF Thanks for sending the archive. After a bit of scratching our heads, we realized that this isn’t a bug at all. The behavior is due to an unwanted rule in your PrintDraftChanges.txt file, which can be reached through the Edit link on the Advanced page (which brings up the file on the View+Edit page):


Comment out line 33 with a # as shown above and everything should work as advertised. (This line was needed when using Paratext’s PrintDraft feature, but gets in the way for PTXprint.)
by (3.2k points)
reshown

Related questions

0 votes
1 answer 204 views
I have three auxiliary projects in Paratext, that contain the text of a booklet that is being produced in the three different ... , and if so, which files and from where to where?
muckles 116 asked Jan 13, 2021
0 votes
2 answers 451 views
We are using Paratext 8.0.100.63 but I recall seeing this for several versions of Paratext I'm finding that if I ... switch to unformatted view. Is there something I'm doing wrong?
MSEAIT_LT 478 asked Jul 5, 2018
0 votes
0 answers 155 views
Is there an easy way to remove Glossary Markup automatically (in bulk)? I will add this as a feature request. It can be done at ... \w* Then use Edit > Replace to get rid of "\w "
anonymous asked May 12, 2015
0 votes
1 answer 392 views
I'm working on basic checks for a project, and it keeps coming up with Citation form (x) is missing from glossary every ... difference. (P.S. I am using Paratext 8.0.100.84)
Rɔnelh 199 asked Nov 16, 2019
0 votes
1 answer 377 views
Despite having the default Arial font selected in my Language Settings, that is not the font being used in ... currently does not differentiate between lowercase L and uppercase i
anon715303 111 asked Mar 30, 2023
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Give proper recognition to those widows who are really in need.
1 Timothy 5:3
3,037 questions
5,994 answers
5,661 comments
2,022 users