Caution: depending on the length of the hyphenated term and the surrounding text—especially if you refer to the statement intext with the identifier (i.e., @statement-id)—this might mess up the horizontal spacing of lines since the term will not be split up at the hyphen. To avoid this, you can refer to the statement with an internal link, i.e., [L-a](#statement-id).
Caution: depending on the length of the hyphenated term and the surrounding text—especially if you refer to the statement intext with the identifier (i.e., @statement-id)—this might mess up the horizontal spacing of lines since the term will not be split up at the hyphen. To avoid this, you can refer to the statement with an internal link, i.e., [[L-a]{.smallcaps}](#statement-id).
Fix 2 (If Fix 1 Fails). Surround the dash with spaces
:::{.statement #statement-id}
__L - a__. This will not generate an error.
diff --git a/search.json b/search.json
index 9bd01e2..40d9565 100644
--- a/search.json
+++ b/search.json
@@ -1576,7 +1576,7 @@
"href": "chapters/copyediting/27-cop-troubleshooting.html#attempt-to-compare-nil-with-number",
"title": "28 Trouble and troubleshooting",
"section": "28.9 attempt to compare nil with number",
- "text": "28.9 attempt to compare nil with number\nError:\nwarning (node filter): error: ...e/2022/texmf-dist/tex/generic/babel/babel-bid\ni-basic.lua:155: attempt to compare nil with number\n\nThis bug can be produced by a statement with a custom label containing an uppercase letter followed by a dash, such as:\n:::{.statement #statement-id}\n__L-a__. This statement might generate an error!\n:::\n\nFix 1. Use the HTML entity for non-breaking hyphen (‑)\n:::{.statement #statement-id}\n__L‑a__. This will not generate an error.\n:::\n\nCaution: depending on the length of the hyphenated term and the surrounding text—especially if you refer to the statement intext with the identifier (i.e., @statement-id)—this might mess up the horizontal spacing of lines since the term will not be split up at the hyphen. To avoid this, you can refer to the statement with an internal link, i.e., [L-a](#statement-id).\nFix 2 (If Fix 1 Fails). Surround the dash with spaces\n:::{.statement #statement-id}\n__L - a__. This will not generate an error.\n:::\n\nA longer dash probably looks better:\n:::{.statement #statement-id}\n__L -- a__. This will not generate an error.\n:::",
+ "text": "28.9 attempt to compare nil with number\nError:\nwarning (node filter): error: ...e/2022/texmf-dist/tex/generic/babel/babel-bid\ni-basic.lua:155: attempt to compare nil with number\n\nThis bug can be produced by a statement with a custom label containing an uppercase letter followed by a dash, such as:\n:::{.statement #statement-id}\n__L-a__. This statement might generate an error!\n:::\n\nFix 1. Use the HTML entity for non-breaking hyphen (‑)\n:::{.statement #statement-id}\n__L‑a__. This will not generate an error.\n:::\n\nCaution: depending on the length of the hyphenated term and the surrounding text—especially if you refer to the statement intext with the identifier (i.e., @statement-id)—this might mess up the horizontal spacing of lines since the term will not be split up at the hyphen. To avoid this, you can refer to the statement with an internal link, i.e., [[L-a]{.smallcaps}](#statement-id).\nFix 2 (If Fix 1 Fails). Surround the dash with spaces\n:::{.statement #statement-id}\n__L - a__. This will not generate an error.\n:::\n\nA longer dash probably looks better:\n:::{.statement #statement-id}\n__L -- a__. This will not generate an error.\n:::",
"crumbs": [
"Copyediting",
"28 Trouble and troubleshooting"