This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: other/2857: i18n, translations does not work

* Dennis Bjorklund ( [20010523 19:26]:

>    Contains files that does not exist any more. Every
>    time a file gets deleted or when a file that contains
>    strings to be translated is added, one must update

The problem is, that you can't do the check unconditionally.

As it is, lists all files that contain messages, excluding only
those files, that should not be translated because they either belong to
tools used to create gcc (like the gen* tools) or belong to debugging
facilities. The check as to whether is current can only be made
if you have a complete source tree. But GCC is also available in split-up
packages, and there the check would fail.

What would be needed for doing the check unconditionally is a mechanism to
create from language specific fragments. I've tried to come up
with a solution but so far haven't succeeded.
> 3. gcc.pot
>    Can be deleted from the cvs since it can be recreated with
>    a "make update-po" in the po directory.

Yes, it can, but again *only* if you have the complete source tree.

> 4. When one builds the files outside the source directory
>    one expects that the source directory should not be
>    altered. In the case of gcc.pot it's not true and this
>    file is created in the source directory.

I'm ATM testing patches that upgrades the i18n machinery to the current
0.10.37 level. The will build gcc.pot in objdir.


Philipp Thomas <>
Development, SuSE GmbH, Deutscherrnstr. 15-19, D-90429 Nuremberg, Germany

Penguins shall save the dinosaurs
                          -- Handelsblatt about Linux on S/390

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]