v5.38.1

v5.38.1 -- 2026-08-19

Summary

• acronyms-suggest proposed FMI = "Interface" for a chapter whose prose
  correctly said "Functional Mock-up Interface (FMI)". The inline
  definition pattern could not carry the hyphenated "Mock-up", so the capture
  restarted at the hyphen and kept only the last word.
• That is worth a release on its own because the next step is
  --apply, which writes the suggestion into the author's own
  [style].acronyms vocabulary -- where a wrong expansion would then make
  src.draft style report correct prose as drifted from it.

What's Changed

• Keep a hyphenated word in a suggested acronym expansion by @prasadtalasila in #255

Full Changelog: v5.38.0...v5.38.1

In Detail

before:  FMI = "Interface"
after:   FMI = "Functional Mock-up Interface"

One group: a name word may now carry (?:-[a-z]+)*. Lowercase after the
hyphen only, so "Digital Twin-Based" keeps its existing reading as two words.
The other ten acronyms the same 15-chapter book suggests -- DT, DM, DS,
DTA, DTI, DTP, DES, ROM, RTF, UQ -- are unchanged, and no draft
or glossary needed editing: the book was right and the detector was not.

Upgrading

Nothing to do. If you have already run acronyms-suggest --apply on prose
containing a hyphenated definition, check that entry in your own
[style].acronyms file -- this release does not rewrite what an earlier run
recorded.