Total Commander

ghisler(Author) wrote: ↑2020-03-12, 10:20 UTC Indeed INI files cannot have Unicode names because the functions to read from ANSI INI files expects an ANSI name for the ini file too.

It seems that GetPrivateProfileStringW with UNICODE parameters properly reads ANSI files.
That is another relic, but at least it could not be turned off.

If TC dir, or the ini files have 8.3 short aliases, could the ANSI functions access TC dir and ini files by their 8.3 names? Or such functions need the rewriting for adding this Unicode name->8.3 name fallback?

In principle, yes - I but I would have to adjust a lot of functions to make it work. It's not really needed when you can choose an install directory with ANSI name from your codepage.

It seems that GetPrivateProfileStringW with UNICODE parameters properly reads ANSI files.
That is another relic, but at least it could not be turned off.

Reading in general should work fine, but writing will cause problems when trying to save Unicode names, which TC stores as UTF-8 with BOM in ANSI files.