https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119684
--- Comment #25 from Bruno Haible <bruno at clisp dot org> --- Jakub, Joseph, (In reply to Jakub Jelinek from comment #18) > I'm afraid implementing format specifier extensions months or years before > they are actually used in the compiler is not possible, they are added when > we need them for something. Ok, that means you are asking for agility, i.e. frequent updates when needed. Gettext 0.26 is now released, with support for the 'gcc-internal-format' strings as of GCC 15. I ignored the problem mentioned in https://gcc.gnu.org/pipermail/gcc/2025-June/246173.html because I got no feedback. > Usually that is during gcc development stage > (so May-mid Nov), so if during patch review the submitter is reminded to > post a patch against gettext, there could be a few months before it is > actually needed (Feb-Apr). Please notify bug-gettext if there are changes in the format specifier extensions in this development cycle. (In reply to Joseph S. Myers from comment #21) > If we want such checking, it should be done in CI (similar to the CI that > verifies generated files that are checked in have been correctly > regenerated), not at .pot regeneration time or .po commit time. OK. Who are the people who manage this CI, and could - add an "msgmt -c" check on the *.po files, - make sure that shortly before a GCC release, the newest GNU gettext release binaries are installed on the CI machine, so as to get the newest GCC/GFC-format string checkers?
