X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date: Tue, 31 Jul 2001 12:15:17 -0500
From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
To: djgpp-workers AT delorie DOT com
Subject: Re: gettext port
Message-ID: <20010731121517.B871@kendall.sfbr.org>
Mail-Followup-To: djgpp-workers AT delorie DOT com
References: <2E0980B03A1 AT HRZ1 DOT hrz DOT tu-darmstadt DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <2E0980B03A1@HRZ1.hrz.tu-darmstadt.de>; from ST001906@HRZ1.HRZ.TU-Darmstadt.De on Tue, Jul 31, 2001 at 11:05:35AM +0200
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

-: 1) Binaries compiled with NLS are large. Should the binary package
-:    contain binaries compiled _without_ NLS too? This means two binaries
-:    for every program.  This would be intended for people who need the
-:    binaries but are not interested in NLS for some particular reason.

I suppose I am one of those people ;-) 

Surely NLS support is a good thing, but I really was shocked at the
resulting increase in size of the NLS-capable executable.  E.g.,
sed 3.02.80 with NLS support---even stripped and UPX-compressed---is
seven times larger than the corresponding 3.02 executable!  I naively
expected NLS support to involve a few hooks in the application itself,
with the real nuts and bolts---and code overhead---of the support to
reside elswhere (e.g., an optional app).