0 votes

I think the proper way to mark words as belonging to the wordlist/glossary is \w␣…\w*␣, where the second space that I’ve marked there is optional. For example, if you wanted punctuation immediately after word, you’d put that immediately after the * and not have a space included.

Also, I’m pretty sure you’re not supposed to add a space after the word and before the end marker \w*. If you do it fails reference checking and tells you there’s a space there.

Is all the above true?

If so, I think there’s a bug either in the USFM standard or in PrintDraft. In TeX, usually you add an optional space before a marker depending on whether you need it in the output, and an obligatory space must come after the marker to signal the end of the marker. USFM seems to treat closing markers with * differently than the TeX rule, and doesn’t require a space after them.

So, what’s happening is if I format my text according to the rules above, I’m getting no spacing between the \w marked word and the next word.

If someone can confirm this is a legitimate problem and not just a mistake on my part, I can write it up as a bug. Should I send it to Paratext or to the ptx2pdf mail list, or someone else?

Paratext by (1.6k points)

3 Answers

+1 vote
Best answer

It’s not a bug. The standard
rule is that “\w " including the space is the complete opening
marker. “*” is the complete closing marker. To have a space
in the text after the \w word/phrase”, you would have to type
a space after the closing marker.

      You are correct that the

word/phrase within the phrase should not end in punctuation or
a space. Ending in punc/space means it would have to be
included as a part of the key in the glossary.

by (571 points)

Arrgh. I’ve known about how the optional space after a closing marker determines the spacing in the output for years, and it didn’t even occur to me today that maybe the rest of the team didn’t. In fact, that was so far from my mind that I started inventing other ideas of what was going on. Now that I re-read my first post here it makes a lot less sense, and I should have known something was wrong.

I went back and looked more carefully (spacing is extremely difficult to see in our font) and realized there wasn’t a space after the \w* marker. In fact, over an hour later and I’ve found and corrected about 500 places where there wasn’t a space but should have been.

Now I probably need to start search for when there is a space but shouldn’t be…

0 votes

The built-in “Export Project to USX” tool in PT also deletes the space after the \w* closing marker, meaning that the <char style=“w”>…</char> result doesn’t have a space after it. To me this suggests a bug in USFM, not PrintDraft.

by (1.6k points)
0 votes

Here is a regex I run on all projects to move a space from before a character style closing marker to after it. It ignores \f* \x* and \fe* because you do not want to move a final space out of a footnote, cross reference or endnote into the text:

by (1.8k points)

I inserted crossed references and they were underlined. What do I do to resolve it?
Then I just ran basic check and found invalid books. What do I do to resolve this?

Related questions

0 votes
3 answers
0 votes
1 answer
0 votes
1 answer
PTXprint Dec 19, 2023 asked by mlucas53 (138 points)
0 votes
3 answers
PTXprint Aug 22, 2023 asked by sajid.imdad (140 points)
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Very truly I tell you, whoever accepts anyone I send accepts me; and whoever accepts me accepts the one who sent me.
John 13:20
2,450 questions
5,139 answers
1,241 users