0 votos
357 vistas

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?

Publicación antigua - se muestra en su idioma original
Paratext por (1,4k puntos) | 357 vistas

3 Respuestas

0 votos
Mejor respuesta

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…
Publicación antigua - se muestra en su idioma original
por (1,4k puntos)

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:-)

Publicación antigua - se muestra en su idioma original
0 votos

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

Publicación antigua - se muestra en su idioma original
por (9,9k puntos)
0 votos

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?

Publicación antigua - se muestra en su idioma original
por (1,4k puntos)

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

Publicación antigua - se muestra en su idioma original

Preguntas relacionadas

+2 votos
0 respuestas 172 vistas
Tengo un problema relacionado con el tema Caracteres no formadores de palabras inesperados en el glosario , pero estoy ... opción es denegar todos los mensajes para este error?
BruceBeatham 129 preguntada nov 9, 2020
0 votos
1 respuesta 153 vistas
Estoy enfrentando este error en mi página de Glosario al ejecutar la verificación "Nejat-dooya" contains unexpected non- ... para resolver este error. Necesito su ayuda. Gracias.
TSNgaihte 220 preguntada sep 24, 2024
0 votos
0 respuestas 189 vistas
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
preguntada ago 16, 2019
+1 voto
0 respuestas 160 vistas
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
preguntada mar 18, 2019
0 votos
0 respuestas 46 vistas
Me parece que la opción de espacios en blanco y caracteres ocultos (WHC) tendrá un impacto significativo en nuestros ... y, quizás, recibir una respuesta de los desarrolladores.
Kent Spielmann 1,8k preguntada nov 19, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And let us consider how we may spur one another on toward love and good deeds, not giving up meeting together, as some are in the habit of doing, but encouraging one another—and all the more as you see the Day approaching.
Hebrews 10:24-25
3,045 preguntas
6,005 respuestas
5,671 comentarios
2,026 usuarios