Date: Wed, 25 Aug 1999 13:47:13 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michel de Ruiter <Michel AT smr DOT nl>
cc: "'DJGPP workers'" <djgpp-workers AT delorie DOT com>
Subject: Re: ASCII 128+ in filenames
In-Reply-To: <B0FEA00E82A7D1118BFB00A0CC990278213397@ARGON>
Message-ID: <Pine.SUN.3.91.990825134401.2834V-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 24 Aug 1999, Michel de Ruiter wrote:

> Is this documented behaviour?

I have never seen it documented, although I know about it.

> Can it be turned off?

I don't think so.  But I'm not sure.

What happens if you install another codepage--do the codes of the 
converted characters, and what they are converted into, change?

> I think it has something to do with DOS
> converting every filename to capitals.

Definitely.

> Should we check for these things in (for
> instance) djtarx, unzip, tar, Emacs, etc.?
> I encountered this when unzipping files
> containing 128+ characters, actually.

What are the problems that this conversion causes?

Emacs 20 supports encoding of file names (with the same MULE machinery 
that is used to encode and decode non-ASCII characters).  Perhaps if we 
understand the problems, we could use this feature to help.