I have not yet received a reply by IDM. I can tell you only what I see with UltraEdit v220.127.116.115 on Windows XP SP3 x86.
- If I select Create new files as UTF-8 at Configuration - Editor - New File Creation,
- and Write UTF-8 BOM header to all UTF-8 files when saved
and Write UTF-8 BOM on new files created within this program
are both not enabled at Configuration - File Handling - Save,
- and I press Ctrl+N to open a new file which is encoded in UTF-8 with DOS line terminators as indicated in the status bar at bottom with U8-DOS,
- and enter some text with characters with decimal value greater than 127,
- and press key F12 to open Save As dialog for saving the new file,
- the Format option is set to Default and the file is saved as UTF-8 file without BOM.
I agree that usually UTF-8 encoded files are used without BOM and that using a BOM makes problems in many applications not supporting Unicode files. The UTF-8 encoding without BOM is often used because
- many applications like compilers and interpreters still do not really support Unicode files. UTF-8 encoding makes it possible to use those applications nevertheless because UTF-8 encoded files can be interpreted when only single byte, null terminated strings can be processed.
- UTF-8 encoding saves storage space and reduces data transfer volume for many text files in comparison to UTF-16 because often most text files contain mainly characters from ASCII table and just a few characters are from Unicode table.
However, UTF-8 with BOM should be nevertheless supported by a text editor.
I just tested UltraEdit with the default settings by renaming uedit32.ini
(usually located in directory %appdata%\IDMComp\UltraEdit
) and starting UltraEdit which created the INI file completely new. The 2 Write UTF-8 BOM
... settings are by default not checked. The default encoding type for new files is ANSI and therefore this setting must be changed by the user when new files should be encoded with UTF-8. After making this change, opening a new file, entering a text, opening Save As dialog, entering a file name and saving the file, the new file was saved on my hard disk as UTF-8 encoded file with DOS line terminators and without BOM.
So UltraEdit is configured by default for saving UTF-8 files without BOM, at least on Windows 2000 / XP. Just when a UTF-8 file with BOM is opened, modified and saved, it still contains the BOM after save.
Perhaps the Save As dialog for Windows 7 and Vista is working currently different to Save As for Windows XP and 2000.
Is there any other user using UE v18.104.22.1685 on Windows 7 / Vista who can confirm this behavior?
In the meantime while waiting for a reply from IDM support, I suggest that you check your uedit32.ini. Open it with Notepad while UltraEdit is not running. Search for File Format=
and set the value to 0
(zero). Make sure there is no second File Format=
in uedit32.ini. Save uedit32.ini, close Notepad and check if UltraEdit now has always Default
set in the Save As dialog.
If that does not work and in Save As dialog still UTF-8
is preselected, close UE, rename uedit32.ini for example to uedit32_bak.ini, start UE which creates uedit32.ini new, select encoding type UTF-8 for new files in the configuration, open a new file (the one already open is an ANSI file), enter some text and save it. Is the file now saved as UTF-8 file without BOM?