Date:	Tue, 26 Nov 2002 08:09:19 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: [PATCH] Updates for readme.1st
In-Reply-To:	<E18GPJ9-0000hA-00@phekda.freeserve.co.uk>
Message-ID:	<Pine.SUN.3.91.1021126080532.23833C-100000@is>
MIME-Version:	1.0
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

On Mon, 25 Nov 2002, Richard Dawe wrote:

> Following up from the review of readme.1st, here is a patch that:

Thanks.

> Charles didn't think that the symlink information was necessary,
> but I think we should tell users about it in advance. Forewarned
> is forearmed, I think the saying goes.

I agree.

> OK to commit?

Fine with me, but I have a couple of minor comments:

> +A 'long file name' or 'long directory name' has path components that
> +are longer than 8 characters in the portion before the extension
> +and longer than 3 characters in the extension.  A long file name may
> +also have multiple extensions and contain some characters that are
> +illegal in short file names (e.g.: spaces).

In compliance with the GNU project's policy, please don't say "illegal", 
unless some real legal problem is involved.  Using such characters in 
DOS names will not get anyone arrested or something.  In this case, 
"invalid" is a better word.

> -Compatibility with V2.00
> -------------------------
> +Compatibility with V2.x
> +-----------------------

I suggest "Compatibility with previous V2.x versions" instead.

> -(and long filenames under Win95), mixing V2.00 programs with those
> +(and long file names under Win95), mixing V2.00 programs with those

I think we should replace "Win95" with "Windows 9x, Windows ME, Windows 
2000 and Windows XP".

- Raw text -