From owner-freebsd-i18n@FreeBSD.ORG Mon Mar 9 22:17:49 2009 Return-Path: Delivered-To: freebsd-i18n@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9C3B10656FD; Mon, 9 Mar 2009 22:17:49 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-ew0-f166.google.com (mail-ew0-f166.google.com [209.85.219.166]) by mx1.freebsd.org (Postfix) with ESMTP id C29198FC0A; Mon, 9 Mar 2009 22:17:48 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by ewy10 with SMTP id 10so1004120ewy.43 for ; Mon, 09 Mar 2009 15:17:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=RtlVDg7gHyiNaK+oV1JUW9LswDwnyVFVeDNI5jo1AQU=; b=VrRmFWZ/2AtLzJVY2TXP+YPCj7fv1VuLH1yLPyn+OPrzVzUWM3wnn5wMOTmeYFx3kz 1HTcr9wufPhSvevTepFWHJGUVktYVlu+8sjKYFtvQmE0xCauLmz5Ken9gxZIQ9J2aPHM h6KWFVqfEVMFgoXjHw1lsG8HKQYdYD4ktxy/E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=iaPAOOEqPn+I/z2rB8jlqinMIE5pW2VsapdYniz4GnGW14i8qRWUAy5UtPIBhU+sxI H4RcuW/Bki5MyQtZMx12lvUSte5e561k0LsaAKFKrkoRYCnWSmycRITRo+6FeNXXv8k9 jbLD8+9/ovfZ3EPO1WCEhq0z6pw2Nb9VrpVpg= Received: by 10.216.53.83 with SMTP id f61mr2377784wec.33.1236637067781; Mon, 09 Mar 2009 15:17:47 -0700 (PDT) Received: from self.rene-ladan.nl ([77.163.174.49]) by mx.google.com with ESMTPS id 35sm8337736nfu.47.2009.03.09.15.17.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 09 Mar 2009 15:17:47 -0700 (PDT) Sender: Rene Ladan Message-ID: <49B5958A.8040403@freebsd.org> Date: Mon, 09 Mar 2009 23:17:46 +0100 From: Rene Ladan Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090111) MIME-Version: 1.0 To: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= References: <49A85B8A.2080503@FreeBSD.org> <49B3F585.7030304@freebsd.org> <49B3F63F.3080405@FreeBSD.org> In-Reply-To: <49B3F63F.3080405@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org, freebsd-i18n@FreeBSD.org Subject: Re: RFC: localized libc messages X-BeenThere: freebsd-i18n@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Internationalization Effort List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 22:17:51 -0000 Gábor Kövesdán schreef: > Rene Ladan escribió: >> Gábor Kövesdán schreef: >>> Hello all, >>> >>> There has been NLS support in our libc implementation for a long >>> time, but it has been disabled because of some initial problems with >>> NLS. (I don't know the exact explanation, I've just looked up the >>> mail archives.) Now, I've made a patch to re-enable it and I've >>> tested this stuff. It seems to be working without any problems on >>> 7.X. I haven't had any opportunity to try it out on -CURRENT, but >>> I've made available the patch for 8-CURRENT. It turns NLS on and adds >>> some new catalog files. >> >> I've put a slightly different patch (some improvements to the Dutch >> translation) at http://people.freebsd.org/~rene/patches/nls-r189223.diff >> >> It works fine on CURRENT after adding the appropriate stuff to >> ~/.login_conf. >> >> The only problem is that during buildworld, the temporary directories for >> storing the translations are not created. I had to create them manually, >> and continue the build with the NO_CLEAN flag (to prevent them getting >> deleted again). > Yes, I was going to commit the patch yesterday but I realized this > problem and haven't yet found the fix. If there's someone skilled at > bsd.*.mk, some help would be appreciatied. :) > I had a quick look at src/share/mk/bsd.nls.mk and lib/libc/nls/Makefile.inc The latter seems ok to me, can the problem be in bsd.nls.mk (e.g. that it has to create the directories somewhere in the installation rules)? bsd.nls.mk first does some name mangling in the installation step and then adds the mangled NLS stuff to the SYMLINKS variable, i.e. create the appropriate symbolic links. But it indeed doesn't seem to create directories. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net)