Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!yetti!geac!daveb
From: daveb@geac.UUCP (Brown)
Newsgroups: comp.protocols.appletalk
Subject: Re: mac File Representation
Message-ID: <1259@geac.UUCP>
Date: Thu, 27-Aug-87 09:33:40 EDT
Article-I.D.: geac.1259
Posted: Thu Aug 27 09:33:40 1987
Date-Received: Sat, 29-Aug-87 07:39:22 EDT
References: <8708261841.AA19610@ucbvax.Berkeley.EDU>
Reply-To: daveb@geac.UUCP (Dave Collier-Brown)
Organization: The little blue rock next to that twinkly star.
Lines: 27

In article <8708261841.AA19610@ucbvax.Berkeley.EDU> tom@CITI.UMICH.EDU writes:
>I don't like having different naming conventions for different
>servers.  This is another server dependency that MacNFS will have to
>keep track of.  Yet, I am not sure it is possible to devise a single
>scheme that works for all server types.  I don't know the answer to
>this one.

You may consider a canonicalization procedure for names like the
following (used in a C compiler for a brain-damaged linker):

  if name exceeds the maximum length and the its-ok flag is not set
	1) from the end to the beginning delete _ characters until
	   the length is short enough or the first character is reached
	   (ie, don't delete leading single _'s)
	2) do the same with spaces, NOT retaining leading spaces (heuristic!)
	2) do the same with vowels, retaining leading vowels
	3) truncate.

This produces names for the linker which usually work, and are still
recognizable by mere humans when using the debugger.

  And thats what I'm after when I want to munge a Mac filename!
-- 
 David Collier-Brown.                 {mnetor|yetti|utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind)
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.