Follow-up Comment #4, bug #68515 (group groff): [comment #2 comment #2:] > But it does not match the "expected output" in the comments of the script.
This "expected output" comes from examples in bug #66054. But in comment 19
there, Branden explains why the formerly expected output is no longer
expected:
"In _groff_ 1.23.0, é had a hyphenation code of 0. In _groff_ 1.24.0, it has
a hyphenation code of 233 (because these are set up in 'latin1.tmac' now)."
So as of 1.24.0, the latin1.tmac setup file is invalidating the test that
hcode-request-copies-spec-char-code.sh tries to run.
While this doesn't entirely explain the July-10-build behavior, we do now know
the script isn't testing .hcode per se.
But it _is_ still testing actual hyphenation behavior, which is the aspect of
hyphenation codes that users care about, and something hcode-request-works.sh
does not do. But there might be other tests that already cover that (I
haven't looked).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68515>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
