Support.Bible is a public forum that connects users of Bible translation software, so that they can help one another find solutions and discover new ways of working together. We welcome users of all Bible translation software systems to discover how they can help one another take God's Word to the world.
Search existing questions first — if you don't find what you need, create a free account to ask your own.
Basic checks is reporting a problem "Character style not closed" on the following cross-reference in 1 Peter:
\x + \xo 5.13 \xt Zk: Bbh 12.12, 25; 13.13; 15.37-39; Kls 4.10; 2 Tim 4.11; Flm 24 \x*
I can't see what is causing this, especially as there are already dozens of cross-references in the project with the same markers and which aren't generating errors, such as:
\x + \xo 5.6 \xt Zk: Mty 23.12; Luk 14.11; 18.14 \x*
How do I resolve this please?
在沒有看到更多 USFM 內容，也無法確切知道檢查工具在何處標記錯誤的情況下，我最好的猜測是：交叉引用位於另一個樣式內部，而該樣式在交叉引用之前沒有關閉。如果我没記錯的話，類似以下內容是無效的：\em this is text\x + \xo 5.13 \xt Zk: Bbh 12.12,25\x* that is styled.\em*
修正方法是先關閉樣式，然後在交叉引用之後重新開啟：
\em this is text\em*\x + \xo 5.13 \xt Zk: Bbh 12.12,25\x*\em that is styled.\em*
Without seeing more of the USFM and without seeing exactly where the check is flagging, my best guess is that the cross reference is inside another style that is not closed before the cross reference. If I recall, something like the following is invalid:\em this is text\x + \xo 5.13 \xt Zk: Bbh 12.12,25\x* that is styled.\em*
The fix is to close the style before the cross reference and then reopen it afterwards:
它不是巢狀的。這是一個簡單的交叉引用。也許截圖比我的解釋更有助於理解：......除非它指的是前面的腳註？
It isn't nested. It's a simple cross-reference. Perhaps a screenshot helps more than my explanation:......Unless it's referring to the preceding footnote?
這個錯誤確實是由於前面的腳註中缺少 \xt* 造成的，但這種錯誤提示方式似乎極其令人困惑。我自然而然地在實際的交叉引用中尋找問題，因為當我雙擊錯誤訊息時，該交叉引用被高亮顯示了。不過，問題已經解決了。
The error was indeed caused by the missing \xt* in preceding footnote but it seems an exceedingly confusing way to signal an error. I naturally looked for a problem in the actual cross-reference which was highlighted when I double-clicked the error message. Still, problem solved.
