other/2857: i18n, translations does not work
Dennis Bjorklund
db@zigo.dhs.org
Wed May 23 10:26:00 GMT 2001
On Wed, 23 May 2001, Mark Mitchell wrote:
> I would very much prefer that *no* generated files be in CVS, but I
> don't understand internationalization at all. :-) If the pot file can
> be generated, I agree that we shouldn't have it in CVS.
I have now looked more into this. I hade trouble compiling before and that
was because I built inside the source directory, and that does not work.
(I knew that, but had forgot since the last time)
Another misstake I did was to use the HEAD branch instead of the
gcc-3_0-branch.
Now some information about the problem in gcc/po/ (gcc-3_0-branch):
1. POTFILE.in
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
POTFILE.in
Now I had to remove the entries:
frame-dwarf2.c
frame.c
There is probably some files missing meaning that there will
be strings in gcc not marked for translation. But we can't know
which until we have a full translation and gets output that is
not translated, or if someone goes through all gcc source files
searching for it. But I want volenter for that.
2. Makefile.in.in
The --defines flag to xgettext must be deleted since it does
not exist.
3. gcc.pot
Can be deleted from the cvs since it can be recreated with
a "make update-po" in the po directory.
Now when I do it the size of this file is comparabel with
the size of the cvs version so I guess they are almost
the same. The cvs version is 9 months old so you
can't really expect them to be exactly the same. Some
strings surely have changed during this time :-)
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.
The patch seems to work and now that I can compile, and when I have
checked out the right branch I can restart the work with the translation.
I've been waiting 9 months for this :-)
--
/Dennis
More information about the Gcc-patches
mailing list