Delivered-To: garrigue at math.nagoya-u.ac.jp
Delivered-To: lablgtk at yquem.inria.fr
Message-Id: <EF36B2D3-203D-4961-BED9-1A1F44D25F5C at cea.fr>
From: Pascal Cuoq <Pascal.Cuoq at cea.fr>
To: Aaron Bohannon <bohannon at cis.upenn.edu>
In-Reply-To: <c413fcb70909240710s628e514bh5dd4da8eb12cdc42 at mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: [Lablgtk] Lablgtk2 and gtk-osx
Date: Thu, 24 Sep 2009 16:35:21 +0200
References: <c413fcb70909191145r4b1b831cu5e5a8fb4de38eea4 at mail.gmail.com>
	<20090921.202824.28799666.garrigue@math.nagoya-u.ac.jp>
	<c413fcb70909210930u25ab4649scbafcc9686c7c5c6@mail.gmail.com>
	<20090922.110331.102563324.garrigue@math.nagoya-u.ac.jp>
	<1DC952C2-2C8A-4FF0-A845-C9C299798CAD@cea.fr>
	<c413fcb70909240710s628e514bh5dd4da8eb12cdc42@mail.gmail.com>
Cc: lablgtk at yquem.inria.fr


> Well, this is nice to know, but unfortunately the character display is
> too buggy to make lablgtk2 usable with gtk-quartz on 10.6.  (See
> attached images.)  I gather that this has something to do with pango,
> and we have to wait until they update their code.

Interesting image. I have never had this particular flavor of
character misdisplay, and I am not transitioning to 10.6 until
everyone else has ironed out the bugs.

Some ideas, for what they are worth:

* I worked around display problems in Frama-C by installing
the DejaVu Sans fonts and making sure the application
was using them. Before I did that, the non-ascii characters
were displayed wrong, so there was at least a little bit of
similarity with your problem.

* Binary compatibility in Snow Leopard for Leopard-compiled
applications is probably better than source-level compatibility
(Leopard-compiled Frama-C binaries work on Snow Leopard).
So if your intention is to make binaries that work on Snow
Leopard, a shortcut would be to compile them on Leopard.
In order not to irritate users (including yourself) who already use
MacPorts for other packages, I would recommend that you
compile the MacPorts software from sources and configure it
to install in another directory, such as /opt/32bit/

If you are willing to do that, the instructions are on the wiki
http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX
at the section:
"Installing a second Macports tree (recommended approach)"

Your mileage may, as they say, vary.

Pascal

_______________________________________________
Lablgtk mailing list
Lablgtk@yquem.inria.fr
http://yquem.inria.fr/cgi-bin/mailman/listinfo/lablgtk