> Date: Wed, 26 Oct 2022 17:47:54 +0200 > From: [email protected] > Cc: [email protected], [email protected] > > On Wed, Oct 26, 2022 at 03:14:26PM +0300, Eli Zaretskii wrote: > > For this to work, the non-ASCII character we use should be encodable > > both by Latin1 and by the Windows codepages. This is a tough > > requirement, but if you look at the tables of these encodings, you > > will see that some codepoints between 0xA1 and 0xAF are identical > > between many Windows codepages and Latin1. For example, 0xAB is > > identical in many codepages. So maybe we could try such a character, > > for these tests? > > I set the character to the Yen and Yuan sign which is in the range.
That will work in many codepages, but not in 1250, for example. But maybe it's good enough, thanks.
