tlug: Li18nux Draft Spec?!?

[Austin Kurahone <austin@example.com>]

Hi,

I've been giving the new Li18nux spec a quick glance through and was wondering
what everyone else here thought about it.  To be specific, I'm currious why
it chooses GNU gettext (well it currently has all this SunOS stuff in it, 
but they say they're going to be moving to gnu gettext) as their mandetory(?)
mechanism for message catalogues.  Am I the only one who sees a problem with
this[1]?

If anyone knows of a Free (preferably BSD licensed) alternative to gettext
would they please e-mail me.

Thanks,

-- 
Austin K. Kurahone
Tokyo Linux Users Group / Green Frog Linux Maintainer / BUILD Linux Project
printk("Just another Kernel Hacker\n");

[1]:Before anyone asks "What's the problem?", GNU gettext is GPL'd and AFAIK
must be linked into the program that's making use of the calls. (As I
understand, this is the purpose of the intl directory in many a GNU programs)
The problem arises when someone wants to include programs that are for 
various reasons, Non-GPL'd.  Since you can't just say "aw hell GPL it" (Apache
comes to mind), and the GPL and hance gettext have the wonderful "VIRAL" clause
with these programs remain noncompliant?
--------------------------------------------------------------------
Next Nomikai Meeting: June 16 (Fri), 19:00   Tengu TokyoEkiMae
Next Technical Meeting: July 8 (Sat) 13:30   Topic: TBA
--------------------------------------------------------------------
more info: http://www.tlug.gr.jp        Sponsor: Global Online Japan