From owner-freebsd-hackers  Tue Sep 19 07:18:10 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id HAA06189
          for hackers-outgoing; Tue, 19 Sep 1995 07:18:10 -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 HAA06167
          for <hackers@freebsd.org>; Tue, 19 Sep 1995 07:18:05 -0700
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA16023
  (5.67a/IDA-1.5 for hackers@freebsd.org); Tue, 19 Sep 1995 08:50:27 -0500
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id IAA28290; Tue, 19 Sep 1995 08:31:59 -0500
Date: Tue, 19 Sep 1995 08:31:59 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199509191331.IAA28290@bonkers.taronga.com>
To: hackers@freebsd.org
Subject: Re: Policy on printf format specifiers?
Newsgroups: taronga.freebsd.hackers
In-Reply-To: <199509182019.NAA08435@phaeton.artisoft.com>
References: <6760.811430864@critter.tfs.com>
Organization: Taronga Park BBS
Sender: owner-hackers@freebsd.org
Precedence: bulk

In article <199509182019.NAA08435@phaeton.artisoft.com>,
Terry Lambert  <terry@lambert.org> wrote:
>If your storage encoding, like Plan9, is UTF-8, then the answer is you
>can allow them no more than 51 characters for file names, unless you
>provide a prohibitively expensive (in terms of interactive response
>time) "check" callback for character entry.

Why would it be prohibitively expensive? UTF is a simple scheme. I'm sure
I could implement a version of UTF file name checking for an entry dialog
that was fast enough nobody would notice it in TK, even on a 386, and TCL
is no number cruncher.