https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665
--- Comment #3 from Roland Illig <roland.illig at gmx dot de> --- (In reply to Jonathan Wakely from comment #2) > It might be better to report multiple bugs, one per target backend, so that > the relevant target maintainers are informed. Oh, I tried that last year. Of the 113 bugs I reported, 41 are still open. Therefore I thought I'd try a different approach this time. Since it's only about the wording of the diagnostics, it should be possible to handle them all in a few commits, rather than splitting the work onto 12 people. > To avoid similar problems in future, I wonder if a weekly email detailing > any new or modified diagnostics could be produced automatically. The > diagnostics maintainers (and anybody else interested) could look over it and > ensure that we use correct grammar, punctuation, and style. Does this mean you already have diagnostics maintainers? That would be bad because then they should have caught many of these typos already. There were only 53 new strings to translate, and 12 of them contain mistakes. Instead of pushing this task to humans, I still think an automatic process is much more efficient since it doesn't overlook the most commonly occurring patterns. Having human proof readers in addition is nice, too. But having the existing rules codified in a linter program is more important.