- Posted by
- Okay. I just downloaded Version 17.20.0.1014 to my Windows 7 Pro, and it seems to have fixed the BOM default problem. The default encoding is now set to UTF8-no BOM, unlike the prior version, which stubbornly stuck at UTF-8 WITH BOM. It baffles me, however, as to why IDM, which is otherwise so cleve...Posted in Configuration/INI Settings
-   Topics
-   Views
- arofer
Sep 08, 2011
- I believe I have found an (additional) problem. If "Default UTF8=1", I cannot get the "Save As" default setting to move off of "UTF-8 with BOM". It looks like this is a bug in UltraEdit, so I am bailing out and going to support with this. I sent in my settings and example to IDMCOMP support. They ve...Posted in Configuration/INI Settings
-   Topics
-   Views
- arofer
Aug 09, 2011
- Okay I fixed it. First, I changed the Uedit32.ini as you recommended. No change in behavior. Second, I renamed the Uedit32.ini and with save as, I got the Default encoding. I changed this to "utf8 no bom" and that became the new defaulted "save as" encoding. I diffed the old Uedit32.ini and the new ...Posted in Configuration/INI Settings
-   Topics
-   Views
- arofer
Aug 09, 2011
- I am on version 17.10.0.1015 of UltraEdit on Windows 7 Professional. The UTF-8 settings are: New File Creation: UTF-8 File Handling/Save: all options are deselected I never see "Default" on the save as. I always see "UTF-8", which puts a BOM on the file. UTF-8 with BOM is incompatible with most prog...Posted in Configuration/INI Settings
-   Topics
-   Views
- arofer
Aug 08, 2011
- The "Save As" action always chooses UTF-8 (with BOM), and I have to mouse around and reset it in every case. Since the UTF-8 with BOM is a brain-dead format, which is also incompatible with many applications, I NEVER want a BOM on UTF-8. There are no 16-bit entities in the UTF-8 encoding, so it is c...Posted in Configuration/INI Settings
-   Topics
-   Views
- arofer
Aug 05, 2011