Follow-up Comment #16, bug #63354 (project groff): The explanation for the first half of comment #8 appears to be this.
https://git.savannah.gnu.org/cgit/groff.git/tree/src/libs/libgroff/uniglyph.cpp?id=59efbfc364daee11af9207a3fc79675b6f5bfc25#n334 Normally, I get this: $ printf '.fchar \\[u2010] BOGOSITY\nfoo\\[u2010]bar\n.pl \\n[nl]u\n' | ./build/test-groff -Tps -a <beginning of page> foo<hy>bar But if I change it to something obviously wrong, I get this: $ printf '.fchar \\[u2010] BOGOSITY\nfoo\\[u2010]bar\n.pl \\n[nl]u\n' | ./build/test-groff -Tps -a <beginning of page> foo<sl>bar And if I comment it out, I get this: $ printf '.fchar \\[u2010] BOGOSITY\nfoo\\[u2010]bar\n.pl \\n[nl]u\n' | ./build/test-groff -Tps -a <beginning of page> foo<u2010>bar N.B., groff -a output does not "chase" fallback character definitions of the sort we use in "fallback.tmac". _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?63354> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
