From owner-freebsd-i18n Tue Feb 19 19:44:20 2002 Delivered-To: freebsd-i18n@freebsd.org Received: from omega.lovett.com (omega.lovett.com [209.249.90.123]) by hub.freebsd.org (Postfix) with ESMTP id 0C49437B416; Tue, 19 Feb 2002 19:44:05 -0800 (PST) Received: from [209.228.7.72] (helo=[209.228.7.72]) by omega.lovett.com with esmtp (Exim 3.34 #1) id 16dNfi-000FsL-00; Tue, 19 Feb 2002 19:43:59 -0800 User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Tue, 19 Feb 2002 21:45:13 -0600 Subject: Re: iconv conversion: the plan [Was: iconv port: plea for take-over] From: Ade Lovett To: Maxim Sobolev Cc: Pete Fritchman , "Andrey A. Chernov" , Konstantin Chuguev , , , , Message-ID: In-Reply-To: <3C721ADF.7968582D@FreeBSD.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-i18n@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02/19/02 03:29, "Maxim Sobolev" wrote: > Does this sound reasonably? If yes, then we need a volunteer to do the > step (1) above. Ade told that he currently works on libiconv, perhaps > he will take this task as well to avoid the need to merge someone > else's work. Ade? All of the above sounds entirely reasonable (cunningly enough, with the exception of the giconv.h - use iconv.h - hack, it was pretty similar to the way I'd envisaged it). I'm happy to deal with this, but it's going to be at least until next week before I can start hacking - I'm currently in SFO doing RealJob[tm]. Give me until the end of next week, so I can get back home in front of my devel box, update my tree, nuke GNOME, and then start working on the necessary patches. In the meantime, I'm quite happy for others to start work on this, with the provisor that the patches are sent to me first rather than direct committing to the tree, so we can do this as painlessly as possible. Regards, -aDe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message