Bug#190964: gcc-3.2: No .mo files included in the package?
Matthias Klose <doko@cs.tu-berlin.de> writes:
> > Some people have spent quite a lot of time translating GCC messages
> > into other languages (yeah, I happen to be one of them). But these
> > translation .mo files don't seem to be included in any of the Debian
> > packages.
>
> they are, but now for gcc-3.3, because the files clash with
> gcc-3.2. I'm happy to include a patch to look for gcc-X.Y.mo instead
> of gcc.mo.
Ah, see. Didn't understand the issue, either, since I recall them
being distributed before. But I had seen weirder things with other
packages.
Well, I've downloaded the GCC tarball and looked at it. AFAICS,
renaming the package specified in gcc/configure.in to include the
version number should do the trick (GNOME programs do the same to
handle the GNOME 1.x -> GNOME 2.x transition). The attached patch does
that.
--- gcc/configure.in 2003-02-04 01:17:41.000000000 +0100
+++ gcc/new-configure.in 2003-04-30 00:31:18.000000000 +0200
@@ -942,7 +942,7 @@
changequote([,])dnl
# Internationalization
-PACKAGE=gcc
+PACKAGE=gcc-3.2
VERSION="$gcc_version"
AC_SUBST(PACKAGE)
AC_SUBST(VERSION)
> > I don't know if that is a problem with upstream not including them,
> > but anyway the latest files are available here:
> >
> > http://www2.iro.umontreal.ca/~pinard/po/registry.cgi?domain=gcc
>
> maybe you want to help upstream applying these patches? They are
> currently sent to the gcc-patches list and have to be checked in by
> hand.
Applying patches? Do you mean the .po files? How can I help with them?
It is just a question of replacing the old ones. If I could help, I
would love to. Apparently, the gcc-3.2.3 tarball contains the
translation for 2.95, which is completely outdated. Sigh.
--
Ole Laursen
http://www.cs.auc.dk/~olau/
Reply to: