From owner-freebsd-questions@FreeBSD.ORG Thu Apr 8 20:13:02 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55445106566B for ; Thu, 8 Apr 2010 20:13:02 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout026.mac.com (asmtpout026.mac.com [17.148.16.101]) by mx1.freebsd.org (Postfix) with ESMTP id 400B78FC1B for ; Thu, 8 Apr 2010 20:13:01 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp026.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0L0K001AKQTOL480@asmtp026.mac.com> for freebsd-questions@freebsd.org; Thu, 08 Apr 2010 13:13:01 -0700 (PDT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-1004080178 From: Chuck Swiger In-reply-to: Date: Thu, 08 Apr 2010 13:13:00 -0700 Message-id: <85A565CC-DB7F-421B-831B-9E1B48967173@mac.com> References: To: "Kotecha, Grishma" X-Mailer: Apple Mail (2.1078) Cc: "freebsd-questions@freebsd.org" Subject: Re: Unicode support in Free bsd. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2010 20:13:02 -0000 On Apr 8, 2010, at 12:11 PM, Kotecha, Grishma wrote: > Can we name files in freebsd with unicode characters? UFS/UFS2 supports 8-bit chars (except NULL), so UTF8 representation for Unicode filenames ought to work OK. > Also are unicode characters supported in file i/o system calls like open, dllopen, fopen? i.e. can we open a file with unicode pathname? Yes. > for e.g in windows CreatefileW is used for opening files with unicode pathnames (wide characters). You can't use USC-2 / UTF-16 widechars. Regards, -- -Chuck