\fr # in Markers followed by lowercase letter inventory

Question

In “Markers followed by lowercase letter inventory” Paratext has flagged:
\fr 4:10…

1. are digits considered lowercase letters by Paratext? It would seem odd to say it’s ‘valid’ to have lowercase letters following \fr if it’s only to permit numbers…; real errors would also be permitted.
2. a search for \fr in my project returns 196 hits, but only this one appears in the “Markers… inventory”; does anyone have an idea why?
   [I’m trying to set up a project plan that isn’t allowing me to check off things that have been done because some of these issues exist. I’ve never known how to solve them, so there may be a number of such questions to come!]

Answer 1

What you’ve presented should not flag. Too outside the problem it would be good to see the whole text of the problem line and also to see the inventory line that is causing the flag.
Blessings Shegnada

Comments

The whole text of the problem line is:
\f + \fr 4:10b \ft Verse 10b has been moved to after verse 5 because it seems to answer the question asked here. [Cf. T4T1, and also GNT (which moves 10b-14 to after v. 5); Iver Larsen (Danish?) has 4,5,10b,6,7,(8),9,10a,1,2,3,11-14]\f*
I’m not sure what you mean by “the inventory line that is causing the flag”…

---

I think you’ve found the inventories now. For the below problem, your fuller text shows that your reference has 4:10b. It is that lowercase b which is causing the error flag. That is a verse segment. You should make sure that you have listed the verse segment characters for your publication in the Language Settings. (Project Menu/Project Settings/Language Settings/Other Characters). That may solve the problem. If it does not, I suggest that you deny the flags individually when they are appropriate for that situation until you finish text editing so that the check continues to catch wrong editing. After that, you can change the inventory to make that situation valid.

Of course, if you have many of that type of reference, you may prefer to change the inventory right away, but then make a note to yourself to review them in case an error has crept in. This check is good at catching missing \ft, for example. You should also consider your audience. Our teams can blindly follow a resource which uses segments and not know why they are doing it nor consider that their audience will not understand its usage. If it is to be used, they will have to be taught what it means. I would consider a single instance of this in a NT to be an error (which is also a good usage for this check).

Blessings,

---

Thanks for the tip to check “Other Characters” in “Language Settings”. Verse segment characters were already set, so I don’t think that’s the problem…

---

The check is flagging the lowercase b in your reference. You can change the inventory to allow lowercase letters to follow \fr or you can deny the individual flag. Which you do is your choice based on the factors I mentioned earlier.

Blessings,

---

How do you go about denying an individual flag? The Project Plan shows this as the only marker issue for the book.

---

1. Run Basic Checks (Project Menu/Tools/Run Basic Checks) get the list
   of errors.
   2. Single-click on the error in the List menu that you wish to deny
   3. Ctrl-D (Or go to the List menu/Edit/Deny)

That should clear it for the project plan.

Blessings,

Shegnada J.

Language Technology and Publishing Coordinator, SIL Nigeria

Complex Script Layout Specialist, GPS

[Email Removed]

Skype: Shegnada.james.

+[Phone Removed]Signal, LINE and What’sApp)