Script modifies certain utility files which it shouldn't

[osanstrong]

At the time of writing this issue, the script interprets all .tex files in the input directory equally. This was simple to implement, but flawed in a number of ways.

For example, a project may use the package acro, which allows writers to define acronyms with commands in a file acros.tex. However, the script treats acros.tex as if it were just part of the body of the document, and thus adds a plethora of notes and concerns about what it thinks are acronyms and contractions galore inserted into ordinary writing. This is unnecessary, and for utility .tex files, can even cause compilation issues for viewing the final diff file.

Before:

\newacronym{FHR}{FHR}{Fluoride-Salt-Cooled High-Temperature Reactor}
\newacronym{FLiBe}{FLiBe}{Fluoride-Lithium-Beryllium}

\newacronym{FHR}{FHR}{\colorbox{teal}{Fluoride-Salt}\footnote{5g: Two words joined by a hyphen in title case should both be capitalized.}-Cooled \colorbox{teal}{High-Temperature}\footnote{5g: Two words joined by a hyphen in title case should both be capitalized.} Reactor}
\newacronym{FLiBe}{FLiBe}{\colorbox{teal}{Fluoride-Lithium}\footnote{5g: Two words joined by a hyphen in title case should both be capitalized.}-Beryllium}

Some approach that allows for easy but meaningful distinction between the different parts of a repository is necessary. This issue can be closed when the script is modified to discriminate between .tex files, such as by checking for common utility names, carefully ensuring the package xcolor is used, and/or clearly allowing the user to easily define how the script should treat project files using some kind of configuration file.