From owner-freebsd-i18n Mon Nov 27 21: 2:53 2000 Delivered-To: freebsd-i18n@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id D4F3E37B479 for ; Mon, 27 Nov 2000 21:02:50 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id OAA14604; Tue, 28 Nov 2000 14:02:26 +0900 (JST) To: "Michael C . Wu" Cc: freebsd-i18n@freebsd.org In-reply-to: keichii's message of Mon, 27 Nov 2000 22:59:42 CST. <20001127225942.B558@peorth.iteration.net> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: NetBSD libintl, import of CITRUS * From: itojun@iijlab.net Date: Tue, 28 Nov 2000 14:02:26 +0900 Message-ID: <14602.975387746@coconut.itojun.org> Sender: owner-freebsd-i18n@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I would like to produce a patchset for the latest NetBSD libintl >changes ( BSDL gettext, etc.) and the CITRUS FreeBSD source tree >this weekend. Do you have any objections or any suggestions? >Are there any bugs or problems in the CITRUS code or the NetBSD >libintl? i think it a bit early to integrate full citrus code, it may break exisitng applications if you do - you need to be really careful about endianness and some other stuffs. libintl (which is actually a part of citrus code) should be okay, but pls expect some updates, it's not finalized! to enjoy build-in libintl better, you need to update ports/devel/gettext and some interdependencies between ports too. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message