https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119684
--- Comment #15 from Roland Illig <roland.illig at gmx dot de> --- (In reply to Jakub Jelinek from comment #6) > (In reply to Roland Illig from comment #1) > > I wrote a little program to check these, and while doing this, I noticed the > > ambiguity that %td could mean a target-sized integer and "%t must be reg + > > const_int". So the "t" is used both as a modifier as well as a conversion > > specification. This needs to be fixed as well. > > Could you share it, so that we can also check with it other translations? > I thought it is the gettext utilities which are supposed to verify this kind > of stuff, but maybe it hasn't been taught about some GCC format strings yet. Sure, here it is: https://github.com/rillig/translation-team-de, proofread.lua It should be easy to adopt the checks from this program to contrib/check-internal-format-escaping.py, which alread has a working .po parser.
