From owner-freebsd-hackers  Tue Sep 19 12:05:38 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA24630
          for hackers-outgoing; Tue, 19 Sep 1995 12:05:38 -0700
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA24602
          for <hackers@FreeBSD.ORG>; Tue, 19 Sep 1995 12:05:27 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA10393; Tue, 19 Sep 1995 12:02:39 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199509191902.MAA10393@phaeton.artisoft.com>
Subject: Re: Policy on printf format specifiers?
To: peter@taronga.com (Peter da Silva)
Date: Tue, 19 Sep 1995 12:02:39 -0700 (MST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <199509191327.IAA27985@bonkers.taronga.com> from "Peter da Silva" at Sep 19, 95 08:27:13 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 693       
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?

If you consider reducing the MAXPATHNAME by one for every expansion,
then yes, I suppose it does.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.