Error: "Footnote caller is not the expected value (*)"

Question

I have a team who is getting lots of errors in the marker check: “Footnote caller is not the expected value (*)”.

I think I have solved the problem as I was writing this message, but I think it is worth still sending this in case others come across the problem.

The errors show only verses which have valid footnotes. That is, of the format
\f + \fr 2.23 \ft …\f*.

I confirmed with RegEx that the + was the only character used in valid footnotes. I used RegExPal to give me a count of the unique matches (\f . \fr). This confirmed that + was the only character used in valid footnotes.
The settings.xml has the +
+

Then just before sending this message I did another search in RegExPal (\f . .) and discovered that there were several hundred invalid footnotes in the New Testament that was done over a decade ago. These had manually defined callers (a b c …) but with no verse reference.

I still don’t know why Paratext was expecting * as the footnote caller, nor why only the valid footnotes were being reported as errors but at least I have a better understanding of the problem and assume the solution will be to correct the invalid ones so that it will accept the valid ones.

I think their second error “Most notes of this type do not have an origin reference.” is related. Once again it only lists what looks like valid footnotes. However, with 213 valid out of 700+ total footnotes, Paratext is correct - most of the footnotes don’t have an origin references, but they should! The valid ones are not the errors. In this case the majority are the errors with only a minority of correct ones.

较早的帖子 - 以原始语言显示

Answer 1

A team I work with is having the same (almost) problem. They have just finished the Gospel of Mark and have inserted cross-references using \x + and defined digits (1-15) in the Langauge Settings as the caller to be used. It works fine but when the run Basic Checks they get 54 (the number of cross-refs) messages saying “Note caller is not the expected value (-)”. Why would PT be expecting the caller (-) when the team have defined a different set of callers in the Language Settings? What is more bizarre about this problem is that when I import the book into an empty “Test” project I set up with the same Language Settings, running Basic Cheks doesn’t produce any errors!

Comments

This error occurs when other places in the text have used \x - . What you can do is search for \x - and change it to \x + so that all references have the same format of \x +.

---

Thanks. In just the one book or all books in the project. I’ve already done so for Mark?

---

Paratext 正在考虑所有的书。

机器翻译自 English 显示原文

Answer 2

I encountered this same situation. We had no \f * anywhere in the text, only \f + (normal footnotes) and \f % (a special kind of footnote, to be omitted from the printed book but retained in the digital version). There were more \f % in the text than \f + so Paratext decided that \f % was the expected form and flagged all the normal \f + footnotes. Since there were so many, it seemed like every footnote was being flagged, but later we realized that the \f % ones were not being flagged.

What sent us down a rabbit trail was the actual content of the error message. It said:
Note caller is not the expected value (*)
which led us to believe it was expecting an asterisk. If it had said
Note caller is not the expected value (%)
we would have realized right away what was happening. It seems that no matter what custom caller you’re using, if Paratext considers that caller to be the expected one, it shows (*) in the error message instead of the actual character. Showing the actual expected character in the error message would clarify things.

较早的帖子 - 以原始语言显示

Answer 3

I believe that in this case Paratext is using the * as a wildcard and not to represent the character *. This may be unfortunate since some people do mark their footnotes with an *. In the first case mentioned, Paratext is actually using a variety of characters that are not the standard +. Therefore Paratext designates this with the *. Even in the case where all of the notes used %, Paratext sees this as something other than the standard + and designates it with the wildcard.

较早的帖子 - 以原始语言显示

Answer 4

Hi anon703820

Have you fixed all the
footnotes missing the origin reference, either the \fr marker
or the actual ch/vs reference?

If so, I have created a
regular expression find and replace that

• inserts the missing \fr

  Find:(\\f \S+ )((\\f[^r])|(\d\S+))
Repl:\1\\fr \2

• insert the missing ch.vs reference.
  Find:(?s)(?<=\\c (\d+).*?\\v(\S+).*?\\f \S \\fr )(?!\d)(?=.*\\v)
Repl:\1.\2 for period cv separator
  Repl:\1:\2 for colon cv spearator

I have a third expression to make a reference end with ": " as in
be “ch:vs :”
Find:(\\fr \d+[:.][^ :]+) ?(\\f)
Repl:\1: \2

I have user menu options to do these three functions. To use,
edit usermenu.txt in your \My Paratext Projects root directory. If
that does not exist you can add the attached usermenu.txt to that
directory. It gives you many common tasks to perform related to
cleaning up a project.

FO-05 find fnote missing \fr origin ref marker#csd#(\\f \S+)((\\f[^r])|(\d\S+))
FO-05a add missing \fr to footnote#r#(\\f \S+)((\\f[^r])|(\d\S+))#\1\\fr \2

Admin Edit: Attempted to fix formatting from e-mail.

较早的帖子 - 以原始语言显示

Answer 5

我遇到了这个问题，但无法从上面的回复中弄清楚该怎么做。我不懂正则表达式，目前在约翰福音中添加了两个脚注（如果脚注一直报错，我可不想再添加更多了！），这两个脚注都显示以下消息：
“Note caller is not the expected value (*)”
以及
"Most notes of this type do not have an origin reference.

这些脚注是在 Paratext 中使用 Insert Footnote 添加的。

我尝试对路得记运行 Marker check，其中有一个脚注，但没有出现这些错误消息，但我看不出它和约翰福音中被标记为错误的两个脚注有什么不同。

我的 Paratext 可能有一些奇怪的历史遗留问题，因为这个项目已经进行很长时间了，曾在 Shoebox、Toolbox 甚至 Word 中处理过。后来它经历了几次 Paratext 升级，所以里面潜伏着各种各样的东西！

机器翻译自 English 显示原文

Comments

你好 Ro，很高兴在这里见到你。
你收到这些消息可能是因为约翰福音中旧脚注的形式没有使用自动调用者 \f + 和标准来源引用 \fr C:V。通常人们希望保持一致性，因此 Paratext 正在警告你，旧脚注的格式与使用标准方法添加的脚注不同。路得记中可能很少有或没有旧脚注，所以它没有警告你。你可以打开这些书的脚注窗格（F7）来检查脚注并验证这一点。

如果你想为约翰福音添加 \fr 引用以消除 PT 错误消息警告，可以使用一种特殊方法来添加它们：

1. 从项目菜单中的 Project 选择 Advanced>Insert missing origin references
   提示： 如果你看不到 Advanced 菜单项，请点击菜单底部的向下箭头以查看更多选项。
2. 在 Insert missing origin references 窗口中选择 Insert Missing \fr in footnote。
   
3. 点击 Choose Books，然后选择约翰福音
4. 点击 OK，然后点击 OK。
5. \fr 引用将很快被添加。查看约翰福音中的脚注，看看它们是如何更改的。
6. 运行基本检查，“Most notes of this type do not have an origin reference” 错误现在应该已被消除。

如果你运行此操作并希望消除 “Note caller is not the expected value (*)” 错误。这可以通过让所有脚注使用自动调用者来“修复”。你可以使用以下使用正则表达式的 Find/Replace (CTRL-H) 来完成：
查找：
regex:\\f\s+\S+\s*
替换：
\f +
（确保 + 后面有一个空格）

希望这有帮助。

机器翻译自 English 显示原文

---

CrazyRocky:

\f +

Hi, CrazyRocky, Long time no see!

Thanks for the response. I did both of the things you suggested and now no more error messages about footnotes. Thanks!

Answer 6

I’m not sure if the steps CrazyRocky mentioned automatically insert a Project History point. I would recommend doing that first: go to the Project menu > Mark point in history.

After CrazyRocky’s steps, running Basic Checks will help you see if there are remaining errors.

Also, if you want to quickly see a list of all of the footnotes in John, you can use Paratext RegEx Pal. With the list, you could quickly compare and find footnotes that don’t look like the others.

Click the Paratext menu > Advanced > RegEx Pal

In RegEx Pal:

1. Choose your project from the Project drop-down
2. In Find, put \\f .+?\\f\*
3. Go to the Tools menu > Choose Books
4. Choose the book(s) you want to find footnotes for
5. Click OK
6. Go to Tools > Count/Extract
7. Choose Extract
8. Select Include References
9. Click OK

This should give you a list of all of the footnotes in John (and/or whatever book(s) you choose).

I would suggest trying the other steps that CrazyRocky mentioned first, then try this if you’re still having issues.

Answer 7

As you have found, it can be very confusing to get errors when the syntax is correct. In Paratext 9, the checks are not just checking that you have the correct syntax but also if you have been consistent throughout your text.

Answer 8

谢谢。已解决。

机器翻译自 English 显示原文