0
362 次瀏覽

A project I’m working on wants to have both singular and plural forms of the word for some glossary entries, separated by a slash. So the keyword will look something like this:
\k araba/arabaat\k*
But the markers check comes up with this error:


Yes, it is a non-wordforming character, and I’m OK with that, so how can I make the error go away? A couple of keywords contain commas, and it doesn’t complain about those, so why isn’t it accepting this other punctuation? I’ve verified that it has been validated as a character, validated in the punctuation inventory. I even tried adding it to the “Word break characters” list in the Language Settings.

What small thing am I missing?

舊文章 - 以原文顯示
Paratext (1.4k 點) 提出 | 362 次瀏覽

3 個回答

0
最佳回答

So now I have a configuration problem. Before I made this change the only character in the “Other Characters” tab of the Language Settings was a “-” in the Word-medial punctuation field. In spite of this character being there, in the word list, words that had a hyphen were broken, e.g. “hukum”, “al” and “l” were in the word list, but not their combined forms. As soon as I added the “/” to the word-medial punctuation, I guess Paratext recalculated the word list, and it seems to have discovered that there are a lot more words in this language, including “al-hukum” and “l-hukum”, all of which are marked as unknown spelling state, a big problem for this project nearing complete Bible publication! To fix this problem, I had to move the “-” to the Word break characters field. But once I did that, the “-” is now marked as an error in the glossary keywords:


So is the underlying problem that the keyword SFM expects only wordforming characters? But it’s fine with spaces and commas, so that it can have phrases? Sounds kind of contradictory to me…
舊文章 - 以原文顯示
(1.4k 點) 提出

Do not move - to the Word break characters When you so that - will disappear when you view it in Print preview mode. Keep it where it is supposed to be, in Word medial punctuation. (Word break characters is intended for Thai and some other South-East Asian scripts that do not have spaces between words.)

Now that Wordlist recognizes - as a word forming character, you really should complete the Wordlist checks again. In particular you should use the Incorrectly joined or split words check to find inconsistencies in the use of the hyphen to join words.

However if you want to quickly approve all hyphenated words you can do that easily by filtering using hyphen and approving all of the words that appear. (If putting just a hyphen in the Filter box does not give you what you need to see, use regex:-)

舊文章 - 以原文顯示
0

Have you tried adding the / as a “Word-medial” punctuation in the Language Settings?

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

That does seem to solve the problem. What I don’t understand is why it doesn’t complain about the comma as part of the keyword, since it’s not in the Word-medial punctuation list. Is it a different kind of character somehow?

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

I didn’t look into the history as to why, but the check currently skips commas in the keyword of the glossary entries.

From the best I can tell, the checks were added for DBL.

John+Wickberg

舊文章 - 以原文顯示

相關問題

+2
0 個回答 172 次瀏覽
我遇到一個與「詞彙表意外的非構詞字元」問題相關的問題,但我將原本的問題移至這個新討論串,因為在我的情況下,我看到的「意外的非構詞字元」錯誤發生在詞彙表標記內的文字;也就是位於 \w \w* 或 +w +w* 標記之間 連結到詞彙表條目 ... w \w* 標記內的關鍵詞呈現方式中視為有效,而無需將它們定義為字中標點?或者我們唯一的選擇是否認此錯誤的所有訊息?
BruceBeatham 129 提出 已提問 11月 9, 2020
0
1 個回答 153 次瀏覽
我在執行檢查時,於詞彙表(Glossary)頁面遇到此錯誤 "Nejat-dooya" 包含非預期之非構詞字元 ['-']: \k (frtbak.sty) 我需要在該詞中間加入連字號。我不確定應如何在 frtbak.sty 檔案中加入程式碼以解決此錯誤。請您協助。 謝謝。
TSNgaihte 220 提出 已提問 9月 24, 2024
0
0 個回答 189 次瀏覽
This week I discovered that Alt-X does work for Unicode characters where the code is longer than 4 hex digits. The ... desired character when typing two periods: ..-->\ud804\udf
[Expert]
sewhite
3.3k 提出
已提問 8月 16, 2019
+1
0 個回答 160 次瀏覽
Some Unicode characters have a code longer than 4 hex digits. For instance David Rowe was trying to help someone ... on that character gives the UTF16 coding equivalent for it.
[Expert]
sewhite
3.3k 提出
已提問 3月 18, 2019
0
0 個回答 46 次瀏覽
我認為空白與隱藏字元(WHC)選項將對我們的專案產生重大影響 它帶來了一些實際的好處,但如果用於格式設定目的,也有被濫用的風險 我們需要仔細思考,以確保能妥善使用此功能 [已編輯] 請參閱 John Wickberg 在相關貼文中提供的 ... 時,自動將它們轉換為 u00A0 可能也是個好主意 我期待聽到其他人的評論和觀察,也許還能收到開發人員的回覆
Kent Spielmann 1.8k 提出 已提問 11月 19, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Every day they continued to meet together in the temple courts. They broke bread in their homes and ate together with glad and sincere hearts, praising God and enjoying the favor of all the people. And the Lord added to their number daily those who were being saved.
Acts 2:46-47
3,045 個問題
6,005 個回答
5,671 則評論
2,026 位使用者