This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Use gcc-internal-format instead of c-format or nothingin gcc.pot where needed
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Bruno Haible <bruno at clisp dot org>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Zack Weinberg <zack at codesourcery dot com>, gcc-patches at gcc dot gnu dot org
- Date: Wed, 1 Jun 2005 14:06:24 +0000 (UTC)
- Subject: Re: [PATCH] Use gcc-internal-format instead of c-format or nothingin gcc.pot where needed
- References: <20050517113757.GD4930@devserv.devel.redhat.com><firstname.lastname@example.org> <20050601121652.GQ22349@devserv.devel.redhat.com><email@example.com>
On Wed, 1 Jun 2005, Bruno Haible wrote:
> > The patch assumes gettext 0.14.5 or later, not sure how we should
> > enforce it (and not sure for which operations is that version really
> > necessary, only for make gcc.pot and msgmerge or also for msgfmt?).
> This version is necessary also for msgmerge and msgfmt. msgmerge needs
> the precise knowledge about what is a valid gcc-internal-format string,
> so that it can add fuzzy markers, for the translator. And msgfmt needs
> it, so it can report an error if a gcc-internal-format string is not
> validly translated and nevertheless not marked fuzzy.
We need to avoid two possible causes of build breakage:
(a) People building from CVS with an old version of msgfmt must not have
their builds fail because of new features in the .pot and .po files. If
builds with old msgfmt would fail then we need configure checks to disable
msgfmt in such cases.
(b) People building from CVS with current msgfmt must not have their
builds fail because of inconsistencies between the .po and .pot files.
The normal procedure for updating .po files is that we only ever take new
.po files from the TP site; we update the .pot file in CVS, submit a
release or snapshot to the TP, then download the automerged files from
there. Do I understand this would cause build failures between when the
new gcc.pot goes in CVS and when the new .po files do, and if so we need
to get the .po files fixed in CVS first (i.e. get all the relevant
translation teams to submit to the TP files with the problem translations
fixed or marked as fuzzy)?
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
firstname.lastname@example.org (personal mail)
email@example.com (CodeSourcery mail)
firstname.lastname@example.org (Bugzilla assignments and CCs)