Date:	Wed, 25 Aug 1999 15:17:06 +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:	<B0FEA00E82A7D1118BFB00A0CC99027821339A@ARGON>
Message-ID:	<Pine.SUN.3.91.990825151324.2834m-100000@is>
MIME-Version:	1.0
X-MIME-Autoconverted:	from QUOTED-PRINTABLE to 8bit by delorie.com id IAA04993
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

On Wed, 25 Aug 1999, Michel de Ruiter wrote:

> > What are the problems that this conversion causes?
> 
> Well, the automatic filename conversion in djtarx, unzip
> and tar does not know that "filename" and "fîlenámé" will
> result in the same file. So if a zipfile contains both,
> the user has to rename it himself.

That's right, but where is the problem?  Even if DJTAR knew these all map 
to the same file name, it would still ask the user to rename.

> How does Emacs determine whether two buffers are actually the
> same file? For instance:
> 
> c:/path/filename	k:/filename	(SUBSTed)
> filename		FILENAME
> filename		filename.
> filename		fîlenámé
> filename		../path/filename

The answer is, of course, stat(): like any other Unix program, Emacs 
calls stat() and looks at st_dev and st_ino of the two files.

It would be interesting to do the same with the file name which includes 
8-bit characters and see if stat() handles them correctly.  I'd expect it 
to Do The Right Thing, but there's always one more bug...

- Raw text -