0 votes
391 vues

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.

Ancienne publication - affichée dans sa langue d'origine
Paratext par (1,9k points)
réaffiché | 391 vues

2 Réponses

0 votes
Meilleure réponse

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

Ancienne publication - affichée dans sa langue d'origine
par [Expert]
(16,7k points)

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.

Ancienne publication - affichée dans sa langue d'origine

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

Ancienne publication - affichée dans sa langue d'origine

I’ve sent an email.

Ancienne publication - affichée dans sa langue d'origine
+1 vote

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.

Ancienne publication - affichée dans sa langue d'origine
par [Expert]
(16,7k points)

Questions connexes

0 votes
0 réponses 175 vues
Paratext can only automatically sort glossary entries that are properly linked in the Biblical terms tool. Changing the ... have changed and are no longer being sorted correctly.
[Expert]
Jeff_Shrum
2,9k
posée mars 23, 2021
0 votes
1 réponse 416 vues
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 posée nov. 16, 2019
0 votes
1 réponse 34 vues
We're using /xt in footnote cross-references, set to use 'short name' of book. But in the glossary I'd like to use ... name, is there a different USFM code I could use for that?.
Lenice 180 posée oct. 7, 2025
+1 vote
1 réponse 337 vues
When you enter a glossary entries through either the Biblical terms tool or the Biblical terms renderings window, ... following video also describes this procedure in more detail:
[Expert]
Jeff_Shrum
2,9k
posée mars 23, 2021
0 votes
1 réponse 354 vues
I am an administrator in this project. Another administrator has made changes in GLO and other books and done send/ ... Project History but have not updated in the GLO book.
anon399461 123 posée mars 13, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Give proper recognition to those widows who are really in need.
1 Timothy 5:3
3,044 questions
6,003 réponses
5,671 commentaires
2,026 utilisateurs