UltraEdit is a full Unicode
aware application since UltraEdit for Windows v24.00. UEStudio is a full Unicode aware application since v17.00.
The change from an application supporting editing Unicode files to a full Unicode aware application made it necessary to store the settings in INI file UTF-16 Little Endian (two bytes per character) instead of ANSI encoded (one byte per character) to support not only Unicode find/replace history entries (saved UTF-8 encoded up to UE v23.20 and UES v16.20), but also Unicode file/folder names.
For that reason is used by default:
- uedit32u.ini instead of uedit32.ini by uedit32.exe;
- uedit64u.ini instead of uedit64.ini (or uedit32.ini on upgrade from 32-bit to 64-bit) by uedit64.exe;
- uestudiou.ini instead of uestudio.ini by uestudio.exe. There is no difference in file names between 32-bit and 64-bit UEStudio.
Full Unicode aware 32-bit and 64-bit UltraEdit and UEStudio still search first for the INI files without u
in file name in the application's program files directory, in Windows directory and last in application data directory if started without command line option /I=
and with no environment variable UEINIDIR
set. If an INI file with that name is indeed found and the directory of found INI file contains also already the Unicode version with u
in file name before file extension, the Unicode version of the INI file is loaded and the ANSI version in same directory is completely ignored. A found ANSI encoded INI file with no Unicode encoded INI file in same directory is loaded, upgraded and saved as Unicode encoded INI file finally.
The ANSI encoded configuration files are not automatically deleted by UltraEdit/UEStudio after first start and exit after upgrading UE/UES in case of a user decides later to uninstall the newer (not licensed) version and reinstall the older (licensed) version supporting only ANSI encoded configuration.
The ANSI encoded uedit32.*
files are in real no longer needed after an upgrade to UE v24.00 or UES v17.00 or any later version and the decision has been taken by the user finally for working in future with full Unicode aware version of UE/UES. Therefore a user can delete them to save some storage space and speed up start time of UE/UES a little bit although not really noticeable.
The Windows directory should not be used anymore as storage location for the UE/UES configuration files with full Unicode aware UE/UES versions not running anymore on Windows versions prior Windows 7.
But it can still make sense to use a not write-protected UltraEdit/UEStudio program files directory as storage location for the configuration files, for example on often using multiple user accounts on same machine or on often switching between various versions of UE/UES like I do often to answer forum questions not related to currently latest version of UE/UES.
One fact must be taken into account on having the configuration files located in folder containing also uedit32.exe
(x64 or x86 version): executable file nameu.ini is not recognized
in directory of the executable if there is additionally no executable file name.ini
It is best to define environment variable UEINIDIR
with path of UltraEdit/UEStudio program files folder as value either as user or as system environment variable to still have (most) configuration files in program files folder of UE/UES after deletion of ANSI encoded uedit32.*