0 votos
400 visualizações

I’m having trouble using \w … \w* markers when the word in the text is a different form of the word than is in the glossary.

I found in the online USFM documentation that I should be using a pipe (by the way, is there a pdf version of the USFM 3.0 documentation?).

When I type something like \w ہِرودِ|ہِرود\w* (note the small vowel point under the last letter) it solves my “Citation Form (“ہِرودِ”) is missing from the glossary: \w” errors, but both words are still showing in the text. No matter which of the views I go to (Preview, Basic, Formatted, Unformatted, or Standard) both words show.

In Preview view, which would typically remove the \w markers and replace them with a * before the word, the markers are gone but the * is not present.

Basic view is the only place where the glossary version (the second of the two words) is grayed out.

Publicação antiga - exibida no idioma original
Paratext por (1,9k pontos)
reexibida | 400 visualizações

2 Respostas

0 votos
Melhor resposta

Which version of Paratext are you using? What stylesheet is the project using?

I tried it in version 8.0.100.63 and it seems to work fine in a test project (Standard view):
image

Publicação antiga - exibida no idioma original
por [Expert]
(16,7k pontos)

I’m using 8.0.100.62.

In looking at stylesheets, I noticed my usfm.sty is version 2.503. Has usfm.sty version 3.0 not been incorporated into PT yet?

There was a fairly innocuous line in custom.sty pertaining to \w, but I removed it to no effect.

I’m not seeing that grayed out look in Standard view.

Publicação antiga - exibida no idioma original

No, the USFM 3.0 specification was only finalized a couple months ago so it has not been incorporated into any released version of Paratext, yet. Support for USFM 3.0 will be in 8.1 when it releases later this year.

However, having a pipe separating the parts of \w was in before USFM 3.0 so the version of the stylesheet you have should be fine. Could you tell me the name of the project with the problem (if it’s not sensitive)?

Publicação antiga - exibida no idioma original

I’ve sent an email.

Publicação antiga - exibida no idioma original
+1 voto

In case someone else has a similar issue, it turns out it was caused by the spell checking. If the word following the pipe (’|’) was marked as incorrectly spelled (or unknown), that caused the word to not show up in its typical gray color.

Publicação antiga - exibida no idioma original
por [Expert]
(16,7k pontos)

Perguntas relacionadas

0 votos
0 respostas 182 visualizações
O Paratext só pode ordenar automaticamente as entradas do glossário que estão corretamente vinculadas na ferramenta de ... alteradas e não estão mais sendo ordenadas corretamente.
[Expert]
Jeff_Shrum
2,9k
perguntada Mar 23, 2021
0 votos
1 resposta 421 visualizações
I'm working on basic checks for a project, and it keeps coming up with Citation form (x) is missing from glossary every ... difference. (P.S. I am using Paratext 8.0.100.84)
Rɔnelh 199 perguntada Nov 16, 2019
0 votos
1 resposta 35 visualizações
Estamos usando /xt nas referências cruzadas de notas de rodapé, configurado para usar o 'nome curto' do livro. Mas ... Existe um código USFM diferente que eu possa usar para isso?
Lenice 180 perguntada Out 7, 2025
+1 voto
1 resposta 358 visualizações
Quando você insere entradas no glossário por meio da ferramenta de Termos Bíblicos ou da janela de Renderizações de ... a seguir também descreve esse procedimento em mais detalhes:
[Expert]
Jeff_Shrum
2,9k
perguntada Mar 23, 2021
0 votos
1 resposta 371 visualizações
Sou administrador neste projeto. Outro administrador fez alterações no GLO e em outros livros e executou Send/Receive. As ... do Projeto, mas não foram atualizadas no livro GLO.
anon399461 123 perguntada Mar 13, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
How good and pleasant it is when God’s people live together in unity!
Psalm 133:1
3,048 perguntas
6,007 respostas
5,672 comentários
2,027 usuários