Roland Illig [CCed] recently filed numerous issues within our Bugzilla instance relating to i18n.
In general, the issues look valid to me, so I've attempted to fix some of them in the following patch kit. However, we're deep in stage 4 of the development cycle. Looking at our development plan https://gcc.gnu.org/develop.html it's not clear to me how such changes fit into our schedule: the plan seems to make no mention of how i18n and translation fit in to the stages (it talks about bugs and documentation, but not about translatable strings). Do we have a "string freeze" in our schedule? i.e. is there a point at which we avoid changing strings to avoid disrupting things for translators? For example, patch 6 in the kit fixes a bug in a rarely-seen message and would add new entries to the gcc.pot. Other patches in the kit fix grammar/style nits in diagnostic messages, and these would mean changes to entries in the gcc.pot. Some of these nits are clearly worth fixing (e.g. patch 1); others (e.g. patch 7) may be more of a judgement call. Given that we're deep in stage 4 of the cycle, how should deferred issues be marked in BZ? (do we have a fix-queued-for-next-release tag?) FWIW the combined patch kit was successfully bootstrapped®rtested on x86_64-pc-linux-gnu. OK for trunk for next stage 1? (or for stage 4, if any of these look high-priority or sufficiently low-risk?). Also, from a developer POV, when should we regenerate and check-in the .pot files? The rules for submitting patches: https://gcc.gnu.org/contribute.html and for committing them: https://gcc.gnu.org/svnwrite.html seem to make no mention of gettext and .pot files. Looking in libcpp/po/ChangeLog and gcc/po/ChangeLog I see that Joseph [CCed] seems to regularly commit regenerated copies of the .pot files; do we have a policy about this? Thanks; sorry if I'm missing something obvious here. Dave David Malcolm (7): Add missing punctuation to message (PR driver/79875) aarch64.c: tweaks to quoting in error messages (PR target/79925) Remove trailing period from various diagnostic messages (PR translation/79923) c-indentation.c: workaround xgettext limitation (PR c/79921) fortran: remove trailing exclamation mark from various diagnostics (PR fortran/79852) i386.c: make "sorry" message more amenable to translation (PR target/79926) Simplify uses of "%<%s%>" to "%qs" (PR translation/79848) gcc/auto-profile.c | 14 ++++++------- gcc/c-family/c-format.c | 6 +++--- gcc/c-family/c-indentation.c | 4 ++-- gcc/c/c-decl.c | 16 +++++++-------- gcc/c/c-parser.c | 2 +- gcc/config/aarch64/aarch64.c | 10 ++++----- gcc/config/arm/arm-builtins.c | 48 +++++++++++++++++++++---------------------- gcc/config/arm/arm.c | 2 +- gcc/config/i386/i386.c | 12 ++++++++--- gcc/config/msp430/msp430.c | 4 ++-- gcc/cp/decl.c | 6 +++--- gcc/fortran/bbt.c | 2 +- gcc/fortran/decl.c | 2 +- gcc/fortran/dump-parse-tree.c | 2 +- gcc/fortran/module.c | 2 +- gcc/fortran/primary.c | 12 +++++------ gcc/ipa-devirt.c | 2 +- gcc/ipa-pure-const.c | 4 ++-- gcc/opts.c | 2 +- 19 files changed, 79 insertions(+), 73 deletions(-) -- 1.8.5.3
