Re: Free Translation Project

[Philipp Thomas <pthomas at suse dot de>]

* Tom Tromey (tromey@cygnus.com) [20000507 19:20]:

> Maybe adding gcc would result in translations being done.

I tried to start that process once but failed. I'm all for getting gcc
listed in the translation matrix, but IMO there are a few topics that need
to be decided on first before we can try to attract translators. Topics that
come to my mind are:

  - how do we support i18n when building gcc from core+additional language?

    Currently there is no way to do that, as POTFILES.in lists all sources
    that contain translatable messages. And even if this would be changed,
    on what part of the message catalog should translations be based?
    The easiest solution would be to have seperate catalogs for each
    language, but AFAIK, you can't use multiple catalogs simultaneously
    (sp?).
    
  - how do we support i18n when cross-compiling?
  
  - what version of gcc.pot should translators start from?
  
  - how do we provide a way for the translation robot (or Francois Pinard)
    to fetch the most recent version of gcc.pot?
    
I volunteer to act as maintainer for the i18n specific stuff and in the end
get gcc listed, but we have to do our part first, which includes the points
mentioned above.

Philipp

-- 
Philipp Thomas <pthomas@suse.de>
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany

#define NINODE  50              /* number of in core inodes */
#define NPROC   30              /* max number of processes */
 	-- Version 7 UNIX fuer PDP 11, /usr/include/sys/param.h