From owner-freebsd-hackers  Tue Sep 19 07:18:01 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id HAA06152
          for hackers-outgoing; Tue, 19 Sep 1995 07:18:01 -0700
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA06128
          for <hackers@freebsd.org>; Tue, 19 Sep 1995 07:17:56 -0700
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA16020
  (5.67a/IDA-1.5 for hackers@freebsd.org); Tue, 19 Sep 1995 08:50:20 -0500
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id IAA27985; Tue, 19 Sep 1995 08:27:13 -0500
Date: Tue, 19 Sep 1995 08:27:13 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199509191327.IAA27985@bonkers.taronga.com>
To: hackers@freebsd.org
Subject: Re: Policy on printf format specifiers? 
Newsgroups: taronga.freebsd.hackers
In-Reply-To: <6760.811430864@critter.tfs.com>
References: <199509181236.WAA23935@godzilla.zeta.org.au>
Organization: Taronga Park BBS
Sender: owner-hackers@freebsd.org
Precedence: bulk

In article <6760.811430864@critter.tfs.com>,
Poul-Henning Kamp  <phk@critter.tfs.com> wrote:
>> >I'd like to add a format specifier '%S' to the list of format specifiers
>> >accepted by printf.  Well, kernel printf, anyway.
>> I don't want wchar_t's in the kernel.
>I also fail to see the need for this, and even if I did see the need, I
>still think we shouldn't have them in the kernel...

Does namei() handle UTF filenames correctly?