# BridgeConn test cases expected to fail.
# One test path per line (relative to tests/fixtures/usfm-grammar/).
# Lines starting with # are comments.

# --- bugfixes ---
# thc: BridgeConn fixture expects "start" align for thr3/tcr3, but the USFM
# spec says right-aligned columns use "end". Our output is correct.
bugfixes/thc
# empty-table-cell: BridgeConn drops verse content from table cells that
# contain sub-verse markers. Our parser preserves the content.
bugfixes/empty-table-cell

# --- special-cases ---
# empty-attributes: BridgeConn rejects empty-quoted attribute values (e.g.
# lemma="") and falls back to treating the entire |... string as text content.
# The USFM spec does not explicitly forbid empty values; lemma="" is
# syntactically well-formed. Our parser accepts it and lets validation flag
# the empty value separately.
special-cases/empty-attributes

# --- usfmjsTests ---
# usfmBodyTestD: BridgeConn unnests \fv from \fqa, but the USFM spec says
# "\fv will typically be nested within another footnote content element, like
# \ft, \fq or \fqa" (see docs.usfm.bible and ubsicap.github.io/usfm). Our
# parser nests \fv inside \fqa per spec. BridgeConn is also inconsistent —
# it nests \fv correctly in specExamples/footnote but not here.
usfmjsTests/usfmBodyTestD
