Date: Fri, 21 Dec 2001 21:13:54 +0200 From: Alexey Zelkin <phantom@FreeBSD.org> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/msgdef Makefile src/etc Makefile src/etc/mtree BSD.usr.dist src/lib/libc/locale lmessages.c Message-ID: <20011221211354.A8081@ark.cris.net> In-Reply-To: <20011221184818.GA1468@nagual.pp.ru>; from ache@nagual.pp.ru on Fri, Dec 21, 2001 at 09:48:18PM %2B0300 References: <200112211314.fBLDE2b42673@freefall.freebsd.org> <20011221151756.GC98626@nagual.pp.ru> <20011221184745.A91245@ark.cris.net> <20011221184818.GA1468@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, On Fri, Dec 21, 2001 at 09:48:18PM +0300, Andrey A. Chernov wrote: > > > It breaks static binary compatibility at least. I don't think that > > > touching system locale hierarchy is the right solution - libintl is not > > Hmm... I not sure how it will break compatibility. Anyway, since this > > functionality is not merged to RELENG_4 (whole LC_MESSAGES support) > > I don't think that preserving compatibility is important issue. > > Yes, just to note that. I mean -current binaries. It also troubles 'make Hmm... Is preserving compatibility for -current big issue ? > hierarchy' when mtree tries to make directory over existen file. Please take a look on patches committed. It deals with 'make distrib-dirs' case. > > > locale. It will be better to make separate hierarchy for libintl (f.e. > > > 'intl') as done for nls. > > Such behavior is not applicable to any existent gettext() implementation. > > Why create additional incompatility between even BSD's (not to mention > > Linux even) ? > > There are far more incompatibilities than that. F.e. gettext-oriented > programs use short language names. We need either to keep short names too > under locale/ or patch each program to teach our long names. Second To get short language names work we need to bring iconv first. Isn't it ? Only binaries which use some locale specific features will always use "POSIX" locale settings. There's no functional breakage. > solution will be much easy if whole libintl hierarchy moved into separate > dir because short names not needed to be touched. I don't see a reason to do it in this way. > Security issues may arise too (evil-made .po files). What about NLSPATH .po files should be generated as part of buildworld process. > analog in libintl? Is there a way to work f.e. with both /usr/share/locale > and /usr/local/share/locale? Let's back to this issue when libintl import time come. 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?20011221211354.A8081>