0
322 次瀏覽

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 (642 點) 提出 | 322 次瀏覽

2 個回答

0
最佳回答

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.

舊文章 - 以原文顯示
(9.9k 點) 提出

Thanks anon848905. That’s some very helpful information.

舊文章 - 以原文顯示
0

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
舊文章 - 以原文顯示
(642 點) 提出

相關問題

0
0 個回答 59 次瀏覽
目前是否已經存在任何 USFM 的語法高亮工具? 這些工具的形式可能包括 模式匹配器 解析器 語義高亮 我想知道在其他 USFM 編輯器中提供此功能有多困難。
Mercado 203 提出 已提問 10月 24, 2024
0
2 個回答 528 次瀏覽
我試著建立一個指向章節範圍的連結,如下所示: \xt 1:16-2:12|MRK 1:16-2:12\xt* 但這會產生「Invalid extra material」錯誤 有趣的是,章節列表(chapter list)是有 ... 1:16-2:12|MRK 1-2\xt* 但沒有,它同樣產生了「Invalid extra material」錯誤☐☐
Kent Spielmann 1.8k 提出 已提問 7月 7, 2022
0
1 個回答 146 次瀏覽
雖然這是用英文提到的,但似乎在其他語言中也同樣適用 「主」在希伯來文中指 Adonay;在 NIV 譯本中,「LORD」指希伯來文的 Yahweh Yahweh 在文本中呈現為 \nd 主\nd* 它會在文本中顯示這些標記,或使用區分它 ... 使用 NIV 作為對照文本,並視覺上看到「LORD」而不是「主」,或是看到「\nd 主\nd*」而不是「主」?
Peggy Connett 214 提出 已提問 2月 3
0
2 個回答 435 次瀏覽
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 提出 已提問 4月 17, 2019
+1
0 個回答 167 次瀏覽
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 提出 已提問 2月 4, 2019
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Accept the one whose faith is weak, without quarreling over disputable matters.
Romans 14:1
3,051 個問題
6,010 個回答
5,675 則評論
2,030 位使用者