We did consider that, however that would be painful for some users when working with filesets etc.
I will have build uploaded shortly that will behave a lot better - the trick was to try opening with the fallback (for no bom scenarios) as utf-8 - if that fails then try again with the fallback being Encoding.Default - that did work for all my test files. I’m not sure this will be the end of this issue for some users though, as Encoding.Default can be different on different machines.
Much appreciated. I am off tomorrow, but I will work on getting this in next week. My workarounds will hold for the weekend, I think. I am glad I stayed up to converse with you.
Looks like it worked. Some of the batch processes will not be run until later in the week, but there were no issues that I can see with existing nightly processes. Thank you for working with me to turn this around.