Not recognizing hyphenated line-wrapped words

[shmup]

And maybe it shouldn't, but I wanted to bring it up in case it hasn't been before:

Here's an example:

       [......]  they  provide a standard way to include non-standard informa-
       tion in the archive).  If neither  exists,  the  character  will  be  a
       hyphen  (`-'); if there is an extended local header but no extra field,
       `l'; if the reverse, `x'; and if both exist, `X'.   Thus  the  file  in
       this  example is (probably) a text file, is not encrypted, and has nei-
       ther an extra field nor an extended local header  associated  with  it.

What I'm wondering is, would it even be worth it to have an argument that says "respect wrapped hyphenated words"?

In this case that's information and neither.

Example for posterity:

error: `indicat` should be `indicate`
  --> ./third_party/unzip/zipinfo.txt:153:71
    |
153 |        several values.  The first character may be either `t' or `b', indicat-
    |                                                                       ^^^^^^^

[epage]

This would require also distinguishing between a dash being used for line wrapping and subtaction/kebab-case. Granted, there are different kinds of dashes but people are sloppy about that.

I suspect this will not be resolved but will leave open for now.

[cgzones]

Another example (where ignoring systemd-localed is void):

error: `localed` should be `located`
  --> policy/modules/systemd/systemd_locale.te:24:11
   |
24 | # systemd-localed policy
   |           ^^^^^^^

[jgillard]

Another: add-ons, where ons is flagged as a typo