Date: Tue, 16 Oct 2001 11:09:10 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp-workers AT delorie DOT com
Subject: Re: W2K/XP fncase [code]
In-Reply-To: <10110160409.AA14685@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1011016110527.1994N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Mon, 15 Oct 2001, Charles Sandmann wrote:

> Comments?

Some minor ones:

> + The function will return 0 (failure) if there are more than 8 
> + characters before a period, more than 3 characters after a period, 
> + more than one period, starts with a period, any lower case characters, 
> + or any of the special characters @kbd{+,;=[]} or a space.  The 

The @kbd here should be @samp, and please give each character a
separate markup, like this:

  @samp{+}, @samp{,}, @samp{;}, ...

> + special names . and .. are exceptions and will return sucess.

The . and .. should be @file{.} and @file{..} (since these are file
names).

> + system.  The library internally calls this function to determine
> + if a file should have it's name lower cased when fncase=n.

Suggest a cross-reference to _preserve_fncase after the "fncase=n"
part.

Finally, I think the documentation should say it very clearly that the 
argument must _not_ contain lower-case letters, otherwise it will be
considered invalid 8+3 file name.  This is very non-obvious, so we
should say it in a prominent way.