I'm still trying to find out why.

Even though I have:
LC_ALL=pt_BR.UTF-8
LOCALE=pt_BR.UTF-8
LANG=pt_BR.UTF-8
LANGUAGE=pt_BR.UTF-8

And even though most of the programs understand that localization, some doesn't get it and keeps in english, three of them are GDM, Gimp, Nautilus. There are others.

I don't know why they are missing the localization. I already checked the specs and didn't find anything wrong.
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez

It's a bug in an old version of intltool, which some developers are still using. I hope this to be fixed by GNOME 2.30.

Thanks for the fast reply

Out of curiosity I see that paldo's initltool is the latest, so wouldn't downgrading it fix it?
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez

Juergbi,

Intltool and Gnome are fine.

I got curious how mandriva, gentoo, ubuntu, opensuse and many others use the same intltool and does not have the localization problem.

So I found out that intltool reads the files through XML-Parser which uses expat library to do the job. So looking at the packages, I found out that there is a bug on expat 2.0.1 that makes it stop reading some files in some cases. this was reported and then fixed by a patch on novell bug report.

And looking at all the distributions that didn't had the problem I saw that they all use these 2 patches (one for a Python bug and another for xmlparser it self), but looking at paldo's spec I saw that our expat is not patched.

So adding these patches to expat may fix the localization problem.

Here are the patches:

>> PATCH: expat-2.0.1-CVE-2009-3560.diff

Code	[In neuem Fenster öffnen]
https://bugzilla.novell.com/show_bug.cgi?id=566434 http://expat.cvs.sourceforge.net/viewvc/expat/expat/lib/xmlparse.c?r1=1.164&r2=1.166 --- lib/xmlparse.c 2007-05-08 04:25:35.000000000 +0200 +++ lib/xmlparse.c.oden 2010-01-08 15:53:46.992897073 +0100 @@ -3703,6 +3703,9 @@ doProlog(XML_Parser parser, return XML_ERROR_UNCLOSED_TOKEN; case XML_TOK_PARTIAL_CHAR: return XML_ERROR_PARTIAL_CHAR; + case -XML_TOK_PROLOG_S: + tok = -tok; + break; case XML_TOK_NONE: #ifdef XML_DTD /* for internal PE NOT referenced between declarations */

>> PATCH: expat-2.0.1-CVE-2009-3720.diff

Code	[In neuem Fenster öffnen]
http://expat.cvs.sourceforge.net/viewvc/expat/expat/lib/xmltok_impl.c?view=log (1.13 -> 1.15) http://svn.python.org/view?view=rev&revision=74429 --- lib/xmltok_impl.c 2006-11-26 18:34:46.000000000 +0100 +++ lib/xmltok_impl.c.oden 2009-08-21 23:01:22.000000000 +0200 @@ -1744,7 +1744,7 @@ PREFIX(updatePosition)(const ENCODING *e const char *end, POSITION *pos) { - while (ptr != end) { + while (ptr < end) { switch (BYTE_TYPE(enc, ptr)) { #define LEAD_CASE(n) \ case BT_LEAD ## n: \

Probably after recompiling expat the recompilation of intltool and the programs that are not correctly localized such as nautilus, gnome-search, gimp should be recompiled as well
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez

These two patches are now in paldo, however, I doubt that they are related to the localization problem. As I mentioned, intltool 0.41 fixes the issue but not all developers are using it yet.

Even though it didn't fixed the problem of gnome programs with lack of intertionalization, it did fixed the lack of localization of gnu utilities (gettext).

Now I'm still intriged by the fact of why on paldo it is happening but not on mandriva or ubuntu that have intltool 0.41 as well?
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez

It seems that the latest gnome 2.30 have fixed almost everything, but still gnome-panel and gimp are both half translated.

I'll try to investigate these two.
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez