X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date: Wed, 9 May 2001 13:12:16 -0500
From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
To: djgpp-workers AT delorie DOT com
Subject: Re: DJGPP 2.04 release date
Message-ID: <20010509131216.L27959@kendall.sfbr.org>
Mail-Followup-To: djgpp-workers AT delorie DOT com
References: <20010509093658 DOT C27959 AT kendall DOT sfbr DOT org> <200105091638 DOT SAA19410 AT mother DOT ludd DOT luth DOT se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200105091638.SAA19410@mother.ludd.luth.se>; from ams@ludd.luth.se on Wed, May 09, 2001 at 06:38:29PM +0200
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

-: Does that mean the file names are gibberish?

Yes, that's correct.  The SFN is `spelled' using a subset of the
characters from the upper 128 of the active PC character set.

I.e., take the LFN, boil it down to a 48-bit CRC, and interpret those 48
bits as _eight_ (6-bit) ASCII character codes from the upper half of the
codepage.  That becomes the SFN entry, and the original LFN is stored
conventionally in unused directory entries.

-: Can you show us some
-: examples how the SFN looks?

Yes, but I'll have to do that from home, perhaps this
weekend.  (And they may lose some of their appeal in
the journey DOS/DJGPP -> Solaris -> mutt -> you).