Date: Sat, 3 Jun 2000 09:15:37 -0600 (MDT) From: Nate Williams <nate@yogotech.com> To: "Andrey A. Chernov" <ache@FreeBSD.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/locale big5.c euc.c mskanji.c runetype.c setlocale.c setrunelocale.c table.c tolower.c toupper.c utf2.c Message-ID: <200006031515.JAA16138@nomad.yogotech.com> In-Reply-To: <20000603055251.A25576@freebsd.org> References: <20000603054355.A24274@freebsd.org> <6327.960036335@critter.freebsd.dk> <20000603055251.A25576@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> Megre XPG4 code into libc > > > > > >This is not full XPG4 standard of course, but our libxpg4 subset. > > > > I thought we had an age old core decision to leave this out of > > libc ? Has that decision been re-evaluated without me noticing ? > > This was not core decision but my decision after some talks with Nate in one > of the freebsd lists as I remember. Really? I don't remember it, and I don't know enough to be happy/sad with it. :) I do know that the JDK must link in -lxpg4 to get support for Asian locales (wide-char support), so it saves me having to link in a library. But, that's a pretty trivial step to do. > The reasons are obsolete. Now any > i18n-enabled application requires libxpg4 so simple way is always enable it > to not differs from other systems much. This will not cause performance > degradation and only little code grows for static binaries. Sounds good to me, but I have no strong opinion one way or the other. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006031515.JAA16138>