[1050] in BarnOwl Developers

home help back first fref pref prev next nref lref last post

Merging the Unicode branch

daemon@ATHENA.MIT.EDU (Nelson Elhage)
Thu Oct 29 18:12:30 2009

Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
X-Original-To: nelhage@nelhage.com
Date: Mon, 5 May 2008 13:59:09 -0400
From: Nelson Elhage <nelhage@MIT.EDU>
To: barnowl-dev@mit.edu

I want to merge the unicode branch to trunk real soon now. It's stable
and has been in heavy use by most of the devs and some users for a
while now. The three main things we may want to think about are:

1) GLib dependency
   The Unicode branch requires GLib 2.12 or newer. Etch or newer
   Debian or Edgy or newer Ubuntu have this; Older systems will
   not. Athena Linux or Solaris have too old a GLib, but we've
   successfully built it into the barnowl locker and so the locker
   build should not be a problem.

   I don't think this is a big concern unless someone tells me that
   everyone at CMU is using barnowl on ancient machines without a
   modern GLib, or something.

2) Non-UTF-8 locales
   The unicode branch won't work with non-ASCII if you're running in a
   non-UTF-8 locale. I suspect we don't care, but I'd be curious to
   hear if anyone thinks we do.

3) Sending encoding information
   If we want to modify barnowl to create a convention of e.g. sending
   a Content-Type header in zephyr field three, we might want to do so
   now, before we push this into even more widespread use.

Does anyone have any thoughts about these or other concerns before we
merge?

- Nelson

home help back first fref pref prev next nref lref last post