0
360 次浏览

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 分) 发布 | 360 次浏览

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 发布 提问于 十一月 9, 2020
0
1 个回答 153 次浏览
我在运行检查时,在词汇表页面遇到了这个错误 “Nejat-dooya” 包含意外的非构词字符 ['-']:\k (frtbak.sty) 需要在单词中间使用连字符。我不确定如何在 frtbak.sty 文件中编写代码来解决此错误。需要您的帮助。 谢谢。
TSNgaihte 220 发布 提问于 九月 24, 2024
Paratext
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 发布
提问于 八月 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 发布
提问于 三月 18, 2019
0
0 个回答 46 次浏览
在我看来, 空白和隐藏字符 (WHC)选项将对我们的项目产生重大影响 它带来了一些切实的好处,但如果用于格式设置目的,也有被滥用的风险 我们需要仔细思考,以确保正确使用它 [已编辑] 参见 John Wickberg 在相关帖子中的回答 ... 时,自动将它们转换为 u00A0 可能是一个好主意 我期待听到其他人的评论和观察,也许还能得到开发人员的回复
Kent Spielmann 1.8k 发布 提问于 十一月 19, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And I tell you that you are Peter, and on this rock I will build my church, and the gates of Hades will not overcome it.
Matthew 16:18
3,045 个问题
6,005 个回答
5,671 条评论
2,026 位用户