> Date: Sun, 23 Oct 2022 18:52:58 +0200 > From: [email protected] > Cc: [email protected], [email protected] > > On Sun, Oct 23, 2022 at 06:18:09PM +0300, Eli Zaretskii wrote: > > > It depends whether a file with latin1 name was copied or not. If the > > > file was copied, it is normal to have OK. So, could you please check > > > that there is a file included_latîn1.texi in tp/tests, with the î > > > encoded in latin1? On my Debian GNU/Linux it shows as: > > > > > > 'included_lat'$'\356''n1.texi' > > > > The file exists, but its name is included_latמn1.texi. That's how > > Windows interpreted that non-ASCII character in my locale. > > I am pretty sure that this file is correctly generated, I guess that > מ corresponds to the same octet than î in latin1, which is 0xEE unless I > missed something, and your codepage would be Windows-1255, maybe?
Yes, it is. > So, there seems to be no trouble creating a correctly encoded file name > which, if interpreted as ISO-8859-1 gives the correct binary string. Yes. I think the problem is not in generating the file name, it is in using that file later.
