Re: 3.0 branch: POTFILES.in broken

["Zack Weinberg" <zackw at Stanford dot EDU>]

On Mon, Jun 11, 2001 at 11:32:42PM +0100, Joseph S. Myers wrote:
> On Mon, 11 Jun 2001, Zack Weinberg wrote:
> 
> > Appended please find a patch which corrects the Makefile and
> > POTFILES.in for the mainline.  I've applied this as obvious.  In
> > addition, I have regenerated gcc.pot on the mainline and checked that
> > in too.  The diff is very long and boring so I have not included it
> > here.
> > 
> > Mark, OK to apply an equivalent patch (details of the contents of
> > POTFILES.in will be different) to the 3.0 branch?
> 
> Is the plan now that a gcc.pot for the 3.0 release will go to the GNU 
> translation project, for translations to be added in 3.0.1, rather than 
> adding any translations before 3.0?

Given that there are, what, five days left till release, I think we
have no choice.  The .po files we have right now are worse than
useless.  If we don't do a msgmerge we get maybe 5% of the strings
translated.  If we do, then we get actively misleading "fuzzy"
translations of maybe 10% of strings.  I say we zap them, freeze
diagnostics on the branch, and maybe 3.0.1 can have sensible
translations.

> > -c-parse.c
> > +c-parse.y
> 
> The source file here is c-parse.in.

I'm aware of this, but including c-parse.y and objc/objc-parse.y
instead works just as well and is easier to automate.  gettext has no
problem with strings which are duplicated in more than one of the
files it scans.

I'd still be using the yacc output files, if it weren't that the
labelling of what strings came from where was completely wrong.
Somewhere between gettext, bison, and the confusion of source and
build directory for yacc-generated files, we wound up with nonsense.

> > +config/float-c4x.h
> >  config/float-i128.h
> >  config/float-i32.h
> > +config/float-i386.h
> >  config/float-i64.h
> > +config/float-m68k.h
> >  config/float-sh.h
> > +config/float-sparc.h
> >  config/float-vax.h
> 
> None of the float.h files should contain any strings, translatable or
> otherwise.  These are ISO C target headers.

Okay, I'll add these to my script's exclusion list and comment them
all out.

-- 
zw     I was putting away groceries in our kitchen when I got to the
       cabbages and thought "this needs to be tossed into air, preferably
       without looking up first."
       	-- James Nicoll