Re: jhbuild status for 2.23.x

2008-05-19 Thread Claudio Saavedra
El mar, 20-05-2008 a las 00:15 +0200, Kjartan Maraas escribió:
> 
> I tried building everything with jhbuild today and noticed a few
> things that need attention:

Add to that gnome-python having problems to be detected by modules
depending on it due to waf 1.3.2 being used. I already fixed that by
upgrading waf to 1.4.2 in bootstrap.modules.

Claudio

-- 
Claudio Saavedra <[EMAIL PROTECTED]>

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

jhbuild status for 2.23.x

2008-05-19 Thread Kjartan Maraas
Hi.

I tried building everything with jhbuild today and noticed a few things
that need attention:

- glib trunk has changed the _() macro to take a const char * now and
some modules break because of this. Most notably nautilus, ekiga, dasher
and probably a few more. Other modules will have a bunch of new warnings
that need fixing.

- gnome-session doesn't seem to work. When logging in it just hangs and
I see a zombie gnome-login-sound(?) process. Tried running gconf-editor
to turn off the sound server but that didn't help.

- epiphany and yelp don't build on fedora rawhide because of xulrunner
issues and haven't built for me for quite a while (2.22.x even). A
roadmap for html rendering engines and porting to them for various
modules in 2.23.x would be nice

- ekiga should be tracking trunk (3.0 to be) for 2.23.x according to
damien

Granted, this is building from scratch with a very raw fedora hide so
some of my issues could stem from that.

I have patches for nautilus and dasher to make them build and will file
them in bugzilla

Cheers
Kjartan


___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Quotation marks: Using “” instead of ""

2008-05-19 Thread Alan Cox
On Wed, 14 May 2008 04:17:09 -0400
"Havoc Pennington" <[EMAIL PROTECTED]> wrote:

> As James says on Simos's blog post, all strings inside GTK apps are
> defined to be UTF-8 regardless of locale. GLib and GTK will convert on
> the fly to locale encoding if they print to a terminal.

gtk may do, but what will glibc do with them  ?
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Quotation marks: Using “” instead of ""

2008-05-19 Thread Havoc Pennington
As James says on Simos's blog post, all strings inside GTK apps are
defined to be UTF-8 regardless of locale. GLib and GTK will convert on
the fly to locale encoding if they print to a terminal. So there
should be no issue with "C" locale other than possibly some odd
escaping. (Which could in theory be cured by modifying the charset
converter.)

(Though of course the C locale is completely broken and always wrong
to use for messages, but ignoring that for a moment.)

Additionally, there's no rule that a given translation can only
contain strings in the language in question. For example, in the
English translation, I could spell a French or Japanese word correctly
in its native character set, if I wanted to refer to that word. That's
one of the reasons Unicode is used rather than the old
language-specific encodings.

Havoc
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list