From: scott <scott@chronis.rightbox.com>
To: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] labltk vs lablgtk
Date: Thu, 10 Apr 2003 13:41:19 -0400 [thread overview]
Message-ID: <20030410134119.A95310@chronis.pobox.com> (raw)
In-Reply-To: <20030410171825.GA10613@swordfish>; from mgushee@havenrock.com on Thu, Apr 10, 2003 at 11:18:26AM -0600
On Thu, Apr 10, 2003 at 11:18:26AM -0600, Matt Gushee wrote:
> On Thu, Apr 10, 2003 at 04:00:58PM +0200, Henri Dubois-Ferriere wrote:
> >
> > But since I'm going to live with this choice for quite a while, i'm
> > wondering what are the broad pros/cons between labltk and lablgtk?
> > does anything stick out as being specific to one or the other?
>
> Let's see ...
>
[...]
> * (My impression is that) GTK has good Unicode support. Tk has had issues
> with i18n for some time. The latest versions may be up to par, but I'm
> not sure. Probably either would be fine for Western European
> languages; the problems I have heard of were mostly related to
CJKV.
The new gtk (2) has good unicode support. I'm not sure how that's
addressed in lablgtk (2). Tk works with unicode, but labltk does
not. It is possible to hack labltk to do this, but it's _very_ ugly
(trust me I've done it)
scott
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-04-10 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 14:00 Henri Dubois-Ferriere
2003-04-10 16:51 ` Eric C. Cooper
2003-04-10 17:18 ` Matt Gushee
2003-04-10 17:41 ` scott [this message]
2003-04-10 19:26 ` Henri Dubois-Ferriere
2003-04-10 19:57 ` Henri Dubois-Ferriere
2003-04-11 8:41 ` Sven Luther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030410134119.A95310@chronis.pobox.com \
--to=scott@chronis.rightbox.com \
--cc=caml-list@pauillac.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).