Follow-up Comment #5, bug #57594 (project groff):
[comment #3 comment #3:] > We should also write script(s) to verify the groff-cleanliness of the hyphenation files. This can easily take the form of one or more regression tests like the 48 others we have. The most obvious thing I can think of to do is to have one test file for each supported groff locale which then calls .hla (or uses my in-development internationalization patch, bug #59814). If my understanding is correct, an otherwise empty groff document will suffice to provoke diagnostics from .hla if the hyphenation or exception files contain unsupported constructs. See src/roff/troff/env.cpp:hyphen_trie::hpf_getc and src/roff/troff/env.cpp:hyphen_trie::read_patterns_file. The foregoing is done. commit 3e9250fea4ab3e698cf7c2f903eaa4ed0fabf5c0 Author: G. Branden Robinson <[email protected]> Date: Fri Jul 9 03:40:04 2021 +1000 [tests]: Test localization with `-m` option. * src/roff/groff/tests/initialization_is_quiet.sh: * src/roff/groff/tests/localization_works.sh: Rewrite test to use explicit macro file loading localization mechanism. I haven't updated FOR-RELEASE yet because we're blocked on UTF-8 input handling as noted in my previous comment, and the process is not streamlined enough to become robotic. I had to manually do some tomfoolery to deal with our English hyphenation exceptions file (on the bright side, it's much shorter now). _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57594> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
