This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Free Translation Project
> This will currently only work if we include an up-to-date gcc.pot with the
> core package and make sure it is more recent than any of the source files it
> is generated from. Otherwise the build process will try to build gcc.pot and
> will fail because files are missing. Hmm, won't make fail anyway *because*
> of the missing files, i.e. with a 'no rule to make cp/foo.c' ? This issue
> *is* tricky IMO.
Is it really necessary that gcc.pot is always up-to-date? There is IMO
no point in regenerating it every time somebody changes some of the
source files. Instead, building gcc.pot should be invoked manually, by
the i18n maintainer, before releasing a catalog to the translators.
That would solve this problem, wouldn't it? It would also allow to
store gcc.pot in the CVS, together with the translations.
Could it be arranged that the relevant dependencies are available only
under --enable-maintainer-mode? Otherwise, I'd propose that the rule
in po/Makefile.in.in
$(srcdir)/$(PACKAGE).pot: $(POTFILES)
is disabled, and manually enabled only when gcc.pot is to be
rebuild. As I indicated earlier, this must not happen often, for the
sake of the translators.
> That's what I suggested and also posted a patch for.
Hmm. I'd prefer that such patches carry a more prominent subject than
"GCC 3.0 Release Criteria"... I have extreme difficulties of
determining whether that patch has been approved or not, or what the
commentary was.
> > I'm not sure there are much points left,
>
> Well, see above :-/
Try to see this from the user's perspective. A number of users would
consider it an achievement if gcc would produce error messages they
could understand even sometimes. It is quite unlikely that all
translation teams finish their translations by the time gcc 3.0 is
released. Instead, some catalogs will be complete, others nearly
complete, and some will be completely missing. Because the catalog is
large, there will be mistranslations.
So it is very important that this starts very soon, or it won't have
any effect on the release of gcc 3.
Regards,
Martin