Re: l10n/i18n issue in gvfs

Thadeu Lima de Souza Cascardo <[email protected]>
Newsgroups gmane.comp.gnome.vfs.general
Organization Minas Livre
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 08 Jan 2008 09:12:16 +0100
Alexander Larsson <[email protected]> wrote:

> 
> On Mon, 2008-01-07 at 22:56 +0100, Luca Ferretti wrote:
> > 
> > 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)/[email protected]	\ | 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?
> 
> _______________________________________________
> gnome-vfs-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/gnome-vfs-list

The code "s/^\[.*\] +//" should remove those lines like "[encoding:
UTF-8] ". Notice the space after the closing bracket. Otherwise, the
script should only be "s/^\[.*\]//" or perhaps "s/^\[.*\]$//".

Regards,
Thadeu Cascardo.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHg34vyTpryRcqtS0RAtpbAKCa6J6XlC+MFPu3q2Ke9ijsvbApeACghh4c
Klr/pXd1MEl40eazOZxY88U=
=sxkv
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.