Re: l10n/i18n issue in gvfs

[Alexander Larsson <alexl redhat com>]

On Mon, 2008-01-07 at 22:56 +0100, Luca Ferretti wrote:
> Il giorno dom, 23/12/2007 alle 09.53 +0100, Alexander Larsson ha
> scritto:
> > On Sat, 2007-12-22 at 22:12 +0100, Luca Ferretti wrote:
> > > Il giorno sab, 22/12/2007 alle 21.06 +0100, Alexander Larsson ha
> > > scritto:
> > > > On Sat, 2007-12-22 at 12:34 +0100, Luca Ferretti wrote:
> > > > > Il giorno sab, 22/12/2007 alle 12.08 +0100, Luca Ferretti ha scritto:
> > > > > > Il giorno mer, 19/12/2007 alle 09.58 +0100, Alexander Larsson ha
> > > > > > scritto:
> > > > > > > On Tue, 2007-12-18 at 16:53 +0100, Luca Ferretti wrote:
> > > > > 
> > > > > > Note that the second one is missing a \ (xc2 instead \xc2)
> > > > > > 
> > > > > > I'm going to implement solution B
> > > > > 
> > > > > Here is the patch to use intltool framework. po/Makefile.in.in should be
> > > > > removed from svn.
> > > > 
> > > > Is this needed now? I made some changes in HEAD that should put
> > > > --from-code=UTF-8 in the gettext call
> > > > 
> > > 
> > > Ehmm... did you forgot to commit?  ;-)
> > 
> > No, but the change was in po/Makefile.in.in which changed from
> > autogenerated by autogen.sh to being checked in to svn. Maybe you didn't
> > get the latest version of it checked out?
> > 
> 
> Huston, we have a problem....
> 
> Alex, we have to make `intltool-update <LANG>` work too; it should be
> needed by l10n.gnome.org to update statistics and downloadable PO files
> and it's the standard and suggested way to manually update PO files from
> sources.
> 
> But we need to put the infamous "[encoding: UTF-8]" string in
> POTFILES.in in order to run it. This string should be removed by the
> "POTFILES" rule in Makefile.in.in, but this seems to not work. 
> 
> Try this on current svn:
>      1. `cd po`
>      2. `intltool-update it`
>      3. error message: needed "[encoding: UTF-8]"
>      4. add this string in POTFILES.in
>      5. `make POTFILES`
>      6. `less POTFILES`
> 
> Rows starting with [ should be removed (as well as comments starting
> with #) generating POTFILES from POTFILES.in
> 
> Meybe there are some errors in sed rules. Could you check it?

I tried to understand it before, but i just couldn't. There is this sed
call in the Makefile:
	    && (sed -e '/^#/d' 						\
		    -e "s/^\[.*\] +//" 					\
		    -e '/^[ 	]*$$/d' 				\
		    -e "s  *@	$$posrcprefix& \\\\@" < $(srcdir)/$  in	\
		| sed -e '$$s/\\$$//') > $ -t \

The way I read it that should strip out the [] part. But it just doesn't
seem to work, and I was unable to figure out why.

Help? Anyone?