From owner-freebsd-i18n Sat Mar 8 17:23: 7 2003 Delivered-To: freebsd-i18n@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE58737B407 for ; Sat, 8 Mar 2003 17:23:04 -0800 (PST) Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD0C543FAF for ; Sat, 8 Mar 2003 17:23:03 -0800 (PST) (envelope-from jkh@apple.com) Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.12.7/8.12.7) with ESMTP id h291N3Yv028487 for ; Sat, 8 Mar 2003 17:23:03 -0800 (PST) Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Sat, 8 Mar 2003 17:23:03 -0800 Received: from apple.com (vpn-scv-x2-161.apple.com [17.219.193.161]) by scv2.apple.com (8.11.3/8.11.3) with ESMTP id h291N2Q26350; Sat, 8 Mar 2003 17:23:02 -0800 (PST) Date: Sat, 8 Mar 2003 17:23:15 -0800 Subject: Status of Citrus project merge work? Content-Type: multipart/alternative; boundary=Apple-Mail-20-146318854 Mime-Version: 1.0 (Apple Message framework v551) Cc: Landon Fuller To: freebsd-i18n@freebsd.org From: Jordan Hubbard Message-Id: X-Mailer: Apple Mail (2.551) 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 --Apple-Mail-20-146318854 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi guys, I'm currently looking at the NetBSD libc support for wchar_t and noticing that the support seems to be considerably more fully-fleshed out there. There is a citrus/ subdirectory in src/lib/libc which FreeBSD does not have and it also appears that there are quite a few more of the standard ISO/IEC 9899:1999 functions defined there. Is there work ongoing to sync up FreeBSD's libc with NetBSD's libc in this respect (or from the original Citrus sources, for that matter)? I've looked at http://citrus.bsdclub.org/ and it certainly appears like there's some sort of effort underway to do this work for all the BSDs, but I haven't been following the matter closely enough to know how active the FreeBSD branch of this work has been. I have a reason for asking, of course, and that's because Apple is currently reviewing what it would take to bring this work into our own libc for Mac OS X, a libc which is substantially based on FreeBSD's at this point and something I would rather not have gratuitous divergence from. If there's no work currently underway to bring this support in from NetBSD, it's conceivable that I could have some Apple engineers work on the merge and bring FreeBSD's up to date before bringing that, in turn, into Mac OS X but I don't want to step on any toes, either. Comments appreciated. Thanks. - Jordan -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer --Apple-Mail-20-146318854 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII Hi guys, I'm currently looking at the NetBSD libc support for wchar_t and noticing that the support seems to be considerably more fully-fleshed out there. There is a citrus/ subdirectory in src/lib/libc which FreeBSD does not have and it also appears that there are quite a few more of the standard ArialISO/IEC 9899:1999 functions defined there. Is there work ongoing to sync up FreeBSD's libc with NetBSD's libc in this respect (or from the original Citrus sources, for that matter)? I've looked at http://citrus.bsdclub.org/ and it certainly appears like there's some sort of effort underway to do this work for all the BSDs, but I haven't been following the matter closely enough to know how active the FreeBSD branch of this work has been. I have a reason for asking, of course, and that's because Apple is currently reviewing what it would take to bring this work into our own libc for Mac OS X, a libc which is substantially based on FreeBSD's at this point and something I would rather not have gratuitous divergence from. If there's no work currently underway to bring this support in from NetBSD, it's conceivable that I could have some Apple engineers work on the merge and bring FreeBSD's up to date before bringing that, in turn, into Mac OS X but I don't want to step on any toes, either. Comments appreciated. Thanks. - Jordan -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer --Apple-Mail-20-146318854-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message