This page documents how GCC development interacts with the Translation Project.
template files containing all the messages translators need to translate)
are currently regenerated manually.
--enable-generated-files-in-srcdir(this option is only needed for 4.3);
Similarly, to regenerate
This is done at the following times on mainline and active release branches:
gcc.potsubmission to Translation Project
An i18n maintainer submits the
.pot files from
releases to the Translation Project.
In preparation for the first release from a new release branch, a
.pot file for a snapshot should be manually
submitted. Send a message to firstname.lastname@example.org,
whose subject is "gcc-version-bdate.pot" (the "b" format
gets it ordered correctly before the release proper) and whose body
contains the URL of the snapshot
.tar.bz2 file. You need
to regenerate the
pot files on the branch, then wait for a new
snapshot to be run containing it (or run one manually, using the command in the
crontab, if you have access to the
before submitting the snapshot.
.po files (translated messages) from the translators
need to be added to GCC (mainline and active release branch). They
are automatically sent (gzipped) to gcc-patches, and should be
committed by the i18n maintainer as and when they appear on
gcc-patches. But sometimes the i18n maintainer may be busy or
otherwise engaged, or a
.po file may be missed, so,
before each release, a check should be made for updated
.po files that haven't been committed already and the
.po file for each language should be
committed to mainline and branch. The current
for GCC may be found at
the Translation Project site. cpplib
may also be found there.
.po files are maintained by the translators. Patches
to them must not go directly into GCC; they need to be sent to the
respective language team, indicated by the Language-Team entry in the
.po file or the
list of language teams. Bug reports about a translation should be
forwarded to the translation team.
Copyright (C) Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
These pages are maintained by the GCC team. Last modified 2022-10-26.