0 votes
298 views

I have a question about \nd ‘name of Deity’. In USFM 2.4 (p. 53) the syntax is:

\nd_…\nd*

If for some reason there is no space following the opening \nd, and I type the closing marker, like:

\ndManeka\nd*

ParaTExt rightly flags it red. If I then add a space preceding the name, ParaTExt automatically adds a space following the name, like:

\nd_…_\nd*

My inclination is to add a space after the closing marker \nd*, but if I do so there are now two spaces following the ‘name of Deity’–one automatically added inside the markup boundaries and one added by me.

Is this behaviour (i.e., automatically adding a space following a word within marker boundaries) expected?

Paratext by (642 points) | 298 views

2 Answers

0 votes
Best answer

Because \ndManeka is not a valid marker it gets flagged. There should automatically be a space added in front of the \nd* because it is a valid marker and gets separated from the bad marker.

In order to pull the \nd* back I would suggest searching for space \nd* and replacing with no-space \nd* (rather than the entire phrase).

I would be careful adding a space after the \nd* because there could be punctuation so you end up with \nd* . (or some other punctuation). However, if there is no space then you end up with the word being concatenated to the following word.

Here you could use a regular expression in the find and do something like the following:
Find=regex:\s\nd*(?=\p{L})
Replace=\nd*

(Add a space after the \nd* in the replace) This looks for a space followed by \nd* and no-space and a letter. It then replaces it with no-space \nd* and a space.

Paratext adds spaces in some what seem like strange ways. If you have double clicked on a word then generally the space is included and so if you add the \nd…\nd* markers then the space gets included before the \nd*. To avoid this you should select only the word to be marked.

As to the expression not being found in the search, I’m guessing that it could have to do with extra spaces around the expression or another setting in the search window - I tried a similar search and it worked fine.

by (9.8k points)

Thanks anon848905. That’s some very helpful information.

0 votes

Just to add a bit more info:

  • if I try to Find/Replace \nd Maneka \nd* (in order to replace it with \nd Maneka\nd*) there are “No matches found” (even though I select \nd Maneka \nd* in the text and press CTRL + H, and the string \nd Maneka \nd* appears in the Find What box)
  • I’m using View > Standard
by (642 points)

Related questions

0 votes
0 answers 46 views
Do there already exist any syntax highlighters for USFM? These could be in the forms of pattern matchers parsers ... d be to provide this functionality in other USFM editors.
Mercado 203 asked Oct 24, 2024
0 votes
2 answers 442 views
I am trying to create a link to a chapter span like this: \xt 1:16-2:12|MRK 1:16-2:12\xt* But this generates ... -2\xt* But no, it too generated.an Invalid extra material error☐☐
Kent Spielmann 1.8k asked Jul 7, 2022
0 votes
1 answer 30 views
This is mentioned in English, but it seems it would be true in other languages, too. Lord refers to Adonay in Hebrew; LORD ... instead of "Lord" or "\nd Lord\nd* instead of Lord?
Peggy Connett 214 asked Feb 3
0 votes
2 answers 401 views
The /ip marker is used in book introductions in the Good News Version. In Deuteronomy, the /ip marker is registering an error ... to keep that marker in the text. What can be done?
anon142050 118 asked Apr 17, 2019
+1 vote
0 answers 155 views
Hi, in Romani, assuming we're using Rai for the name of the LORD (doesn't always work), then \nd Rai\nd*esko ... tell Paratext's spell checker that \nd* doesn't terminate the word?
anon542642 294 asked Feb 4, 2019
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
May the God who gives endurance and encouragement give you the same attitude of mind toward each other that Christ Jesus had.
Romans 15:5
3,042 questions
6,001 answers
5,666 comments
2,024 users